On Mon, 29 Jul 2002, Oskar Sandberg wrote:
Masquerading NATs do allow transient nodes to work normally, though.
NO! Don't tell me how it works - I wrote the code in question and the
protcol specification. A Freenet node, transient or not, needs to be
able to accept new TCP connections
On Sunday 28 July 2002 21:11, Matthew wrote:
CVS now is at version 489, and this includes code to always route to a
random key on the first hop, at oskar's suggestion. This hopefully will
have the following benefits:
a) prevents the network from splitting, sows it back together when/if it
On Mon, Jul 29, 2002 at 09:29:07AM -0400, Gianni Johansson wrote:
On Sunday 28 July 2002 21:11, Matthew wrote:
CVS now is at version 489, and this includes code to always route to a
random key on the first hop, at oskar's suggestion. This hopefully will
have the following benefits:
a)
I have seen a claim (on FMB) that one person can see more with build 489
than he could before. I've also seen claims that the noderefs that are
available to a transient node behind a NAT firewall are different from
the noderefs that are available to a non-transient node tunneling
through a
On Mon, Jul 29, 2002 at 12:19:37PM -0400, [EMAIL PROTECTED] wrote:
I have seen a claim (on FMB) that one person can see more with build 489
than he could before. I've also seen claims that the noderefs that are
available to a transient node behind a NAT firewall are different from
the
On Mon, 29 Jul 2002, Oskar Sandberg wrote:
On Mon, Jul 29, 2002 at 12:19:37PM -0400, [EMAIL PROTECTED] wrote:
I have seen a claim (on FMB) that one person can see more with build 489
than he could before. I've also seen claims that the noderefs that are
available to a transient node
On Mon, Jul 29, 2002 at 11:50:54PM +0300, Mika Hirvonen wrote:
On Mon, 29 Jul 2002, Oskar Sandberg wrote:
Freenet DOES NOT WORK behind a NAT firewall if you do not tunnel (by
port forwarding.) It does not work, period, transient or not.
Masquerading NATs do allow transient nodes to work
CVS now is at version 489, and this includes code to always route to a
random key on the first hop, at oskar's suggestion. This hopefully will
have the following benefits:
a) prevents the network from splitting, sows it back together when/if it
does
b) if you can't find a piece of data, then
On Mon, Jul 29, 2002 at 02:11:19AM +0100, Matthew Toseland wrote:
CVS now is at version 489, and this includes code to always route to a
random key on the first hop, at oskar's suggestion. This hopefully will
have the following benefits:
a) prevents the network from splitting, sows it back
