Several alternative modes have been added to the node recently for
talking to peers while minimizing bandwidth usage. These need to be
documented.

We have normal mode, listen only mode and burst mode.

"Open" = direct connection to the internet, or behind a full cone NAT.

A normal, B normal:
  If neither node is open, works unless A's or B's IP changes.
  If A or B is open, works unless both A and B change IP.
A normal, B listen-only: 
  Works if B is open, unless B's IP changes.
A normal, B burst:
  Works if B is open, unless B's IP changes.
  Works if A is open, unless A's IP changes.
A burst, B burst:
  Does not work at all if neither node is open, because the bursts will
  not coincide.
  Works if B is open, unless B's IP changes.
  Works if A is open, unless A's IP changes.
A burst, B listen-only:
  Works if B is open, unless B's IP changes.
A listen-only, B listen-only:
  Never works!

Unless you know what you are doing, stick to normal mode. It costs
around one packet per peer per 20-30 seconds, and this is not a big deal
IMHO unless you have far more peers than you should have. We need to
change the warning message to explain our real reasons for discouraging
having too many peers... Which essentially are that we don't like
ubernodes, and that when you add a node it is essential that they add
your peer as well as you adding theirs. Should we warn about listen only
/ burst mode? Or should we just leave them - they only show up in
advanced-darknet mode ...

If B is open and has a reasonably static IP (or if ARKs can be relied
upon, which is not always the case for e.g. nodes with few peers), then
it is okay for B to be burst-only.
-- 
Matthew J Toseland - toad at amphibian.dyndns.org
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20060722/83fc84f6/attachment.pgp>

Reply via email to