on master help sign in
daemon worker king serf confusion
commit2920d9796b53e9a38f45a001d2692bc2deefb01d authorsyzygyzer <jon@tlon.io> dateWed 18 Nov 2020, 17:19 (6 years ago) parent3f72569
1 file changed+6−3
tutorials/arvo/ames.md+6−3
tutorials/arvo/ames.md+6−3
@@ -374,9 +374,12 @@ intended recipient of the packet, and so gets ready to forward it to
374374checksum with the new, and then sends the packet along to `~worwel-sipnum`.
375375
376376Once `~worwel-sipnum` processes the packet, it will know the IP and port of
377−`~bacbel-tagfeb` since `~zod` included it when it forwarded the packet and so
378−will send an ack packet directly to `~bacbel-tagfeb`. Communication between the
379−two ships will now be direct until one of them changes their IP address, port, or networking keys.
377+`~bacbel-tagfeb` since `~zod` included it when it forwarded the packet. Thus
378+`~worwel-sipnum` will send an ack packet directly to `~bacbel-tagfeb`, unless a
379+NAT and/or firewall prevents a direct peer-to-peer connection, in which case
380+`~zod` will contineu to relay packets. Absent these factors preventing a
381+peer-to-peer connection, communication between the two ships will now be direct
382+until one of them changes their IP address, port, or networking keys.
380383
381384
382385## The Serf and the King