aboutsummaryrefslogtreecommitdiffstats
path: root/cli/edit-module.c
diff options
context:
space:
mode:
authoreunhhu <[email protected]>2026-09-29 15:02:46 +0100
committereunhhu <[email protected]>2026-09-29 15:02:46 +0100
commita48c38d2a80efd146ba0f81cb46bac00c22297b6 (patch)
tree348cae210dde44dcbe0f4c2d8eb9bfd2b8c29c44 /cli/edit-module.c
parent0f074f2b1e26e0cdc4e17b785eda2e06ef13e5a8 (diff)
downloadpure-a48c38d2a80efd146ba0f81cb46bac00c22297b6.tar.gz
pure-a48c38d2a80efd146ba0f81cb46bac00c22297b6.zip
Look for a link's receiver again when its probes go unanswered
A link resolved its receiver's name once, at its start: a receiver whose store moved to another machine (another address under the same name) was never found, and a sender whose own network changed kept a socket that no longer went anywhere. Now, when three probes in a row go unanswered, and at each probe after (a second apart at most), the link looks the name up again and sends from a new socket connected there. It looks before the probe goes, so the probe's answer comes to the new socket (looking after it lost every answer, one socket after another). A sender at rest does not look: only probes unanswered count. make check moves a receiver (H3 of docs/design/011-pure-transport.md): in namespaces of its own, the sender links to pure://receiver.test at 127.0.0.2; the receiver is killed, its store, key and memo copied, the old address made unreachable, the name pointed at 127.0.0.3 and the copy started there. Every order is applied once, and the moved receiver makes no X25519.
Diffstat (limited to 'cli/edit-module.c')
0 files changed, 0 insertions, 0 deletions