On Tue, Feb 27, 2001 at 12:33:29AM +0000, Matthew Toseland wrote: > Ahhh... you are comparing the network interfaces and resetting on an interface > change? So what is this caused by? Many people on LANs send their internet > traffic across the LAN, on the same interface as the inet is on, yes? Any way > to avoid this behaviour, as freenet seems to assume global connectivity?
What's currently done is the best way to avoid this behaviour. The only way such invalid address can leak out is on insertion of data from a Freenet node without transient set behind NAT (note that IP-Masqurading qualifies as a form of NAT) or if a node is behind a NAT box that's doing port forwarding. (unlikely as how would the node get contacted anyway?) Both cases aren't really all that common and I think we don't have to worry much. Any invalid addresses will be removed pretty quickly through timeouts and the nodes creating them obviously won't be contacted anyway. If Freenet can't handle a few invalid addresses we don't have a hope in hell. :) -- retep at penguinpowered.com http://retep.tripod.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20010226/e8b77084/attachment.pgp>
