aboutsummaryrefslogtreecommitdiffstats
path: root/docs/glossary.md
Commit message (Collapse)AuthorAgeFilesLines
* docs: how long a broken path takes to see, with PINGs taking turnstv47 hours1-1/+5
| | | | | | | Review 4, 1258's note: the glossary says that a path whose way out broke while the peer's PINGs still come is found by this node's own unanswered PINGs, which with the turns come every one to two intervals, up to twice as long as before, and what still finds it at once.
* paths: PINGs of a path take turns with the peer'stv2 days1-1/+3
| | | | | | | | | | | | | | | | | | The node's keepalives take turns between the two sides (`PeerState::keepalive_due_at`), but the paths layer pinged every path in use every `probe_every` (the keepalive interval, 30 s at least) whatever the peer did: a PING from the peer over the path didn't count. So both sides pinged each path every interval, often within a second of each other (seen on the dashboard: a PING answered, and our own PING right after it). Now a PING from the peer over a path is noted (`PathState::peer_probe`), and a path is pinged again (`rested`) an interval after the peer's PING, if that came last; after ours, an interval and a half while the peer pings too (its PING within two intervals before ours), so its turn comes first; else an interval. One exchange per interval goes over a path, as the measurements' "two keepalives per neighbour per interval" says, and each side measures every other interval; a shorter `--keepalive` measures more often. A path whose way out broke while the peer's PINGs still come in is found by our own PINGs half as often; a failed send or unanswered traffic (`suspect`) still pings at once.
* signatures: kept in the document filetv4 days1-1/+2
| | | | | | | A node's signatures are saved with its document (--document-file) and loaded with it. Auth plan M5.
* replace eager links by treestv8 days1-5/+4
|
* introduce eager linkstv9 days1-0/+6
|
* add documentationtv9 days1-0/+154