Ephrim Khong ([EMAIL PROTECTED]) wrote: > Are you sure that it's technically required to be able to accept > incoming connections?
For full details, you should review the list archives for the
development list ([EMAIL PROTECTED]).
What it comes down to (as far as I understand it) is this:
1) Your node wants to find a key.
2) Your node looks through its list of other nodes and chooses one to
ask for this key. It makes a TCP connection.
3) If the other node has the key, great. You get it. You win.
4) But if the other node doesn't have it, it will have to go looking
for it, which could take a long time. It will disconnect from you
if it doesn't find it within some time frame.
5) If the other node finds the key, it will try to connect to you and
give it to you.
6) If the other node doesn't find the key, it will try to connect to
you and give you the disappointing news.
If any developers are reading this, and I screwed up, please correct
me. Preferably using simple English and small words, because we're
a bit dumb over here on the support@ list. ;-)
> I had some some 15 connections after browsing through some sites, when
> suddenly one connection after the other closed down until none was left.
> My traffic monitor didn't indicate any traffic, and I (think I) know that
> the SOCKS proxy closes connections that were idle for some time.
Then your proxy might be exacerbating the problems that NAT are
causing. In any case, it looks like using Freenet will be a pretty
miserable experience for you with the current codebase.
But I still don't understand how you are actually *using* SOCKS5 in the
context of Freenet. Are you sure you aren't simply using NAT? (E.g.,
if you turn off the NAT and leave only the SOCKS5 proxy, does Freenet
work at all for keys that aren't already in your data store?)
--
Greg Wooledge | "Truth belongs to everybody."
[EMAIL PROTECTED] | - The Red Hot Chili Peppers
http://wooledge.org/~greg/ |
msg01237/pgp00000.pgp
Description: PGP signature
