We discovered what the problem with my connection to sbc was. It was a corporate NAT that rewrites the source port, but doesn't then reroute packets to the new port to the original port. I have introduced a new peer parameter, ignoreSourcePort, which can be set on a specific peer from the dropdown box at the bottom of the darknet page. When this is set, a workaround is instigated, which allows us to connect to such nodes. Each of sbc's peers must set this flag on sbc. At present this is purely manual; some time in the distant future auto-detection code may be introduced. (bug #945).
Should we allow users to set this, and allowLocalAddresses, from the non-advanced darknet page? -------------- 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/20061130/0f45009d/attachment.pgp>
