While the symptoms seem concerning, I don't think your analysis is correct. The DNS lookup doesn't occur while connecting, but when the address object is constructed from the reference, and that time is not included in the connect timeout.
You could try setting up the connect timeout anyways, if a domain name lookup takes you 5 seconds you must be a on a very shabby connections (it took me about 2, and I'm on a modem... in Indonesia). If that doesn't help I want to see logs (logging=debugging , verbosity=5) of what happens on your node when you make a request with HTL > 1. On Sat, Aug 26, 2000 at 02:05:40PM +0100, degs wrote: > Hi, > > I think that the default connection timeouts (2000ms) in .freenetrc are too > short for dynamic DNS. It takes a good 5 seconds to lookup > ceequdee.no-ip.com. I think that this is affecting other nodes' ability to > connect to me. > > The symptoms are: > > * my node is definitely running and visible from the net: I can telnet from > work in to ceequdee.no-ip.com:19114 and get what looks like FP out > * netstat shows connections to other nodes in various TCP states (I can send > this output if it is useful) but practically no traffic goes over the line. > * I can insert data locally and only that data which I have inserted locally > ends up in my datastore. > > The upshot is I don't think any other node is able to contact my node. > > Degs > > PS: apologies if this message is an (approximate) duplicate, Real JukeBox > turned my machine inside-out mid send in the previous attempt... > > _______________________________________________ > Freenet-dev mailing list > Freenet-dev at lists.sourceforge.net > http://lists.sourceforge.net/mailman/listinfo/freenet-dev > -- \oskar _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
