Thanks your reply!
Jeroen Asselman writes:
Op ma 24-11-2003, om 00:24 schreef Rafael R. Reilova:I'm in one of those "degraded" network locations (Puerto Rico to be exact ;) , it appears that some of my ISP's upstream connections are filtered for ports 6346:6348, so I end up with a lot of timeout connections as most other clients still default to those ports. Grr! I can be sure that not all uplinks are filtered since I sometimes do get a connection to a host using that port.
Perhaps we can add an option in gtk-gnutella to not connect to certain ports.
Don't bother, I think the problem is not as critical or might lie elsewhere. Also if we keep some state on unreachable hosts this option is not needed.
However, I wonder, then you must have a hard time downloading too. As that happens over the same port.
I've been looking more into my ISP filtering theory and perhaps it is no more that 15% or so of upstream, either that or a bad router somewhere. I jumped to the first conclusion after the eight hour episode during which I couldn't get a single stable ultra. This happened after I cleared the cache in frustration after waiting about 20 min. to get a stable ultra and seeing the same hosts been attempted for connections.
It seems that the larger amount of failed connections to ports 6346-8 is just mostly due to those ports being the most popular. I can download fine most of the time, so I believe that the large delay to connect to Gnuetella is the suboptimal strategy in selecting the hosts to connect to, combined with some amount of bad luck and ISP filtering: a web cache returning mostly dead / unreachable hosts, and gtk-gnutella reconnecting to those bad / unstable hosts again and again. (about my ISP: you'll be amazed the kind of NAT'ing these people do, even though I have a fully routable public IP, a traceroute reveals no less than three 10.x.x.x and one 192.168.x.x routers between me and the Internet, yet they are the only one's offering DSL in my area.)
Try clearing the host cache. If I clear the host cache, it will take me a loong time again to get into Gnutella (~ hours), as gtk-gnutella cycles over and over the same small set of hosts. I'm now keeping an electrified fence between me and the clear cache button ;)
I'll see if I can do some intrumentation of gtk-gnutella to get more precise connection statistics (# hosts attempted, # repeated hosts, etc) and do an experiment with the cache cleared.
Cheers,
-Rafael
---
Rafael R. Reilova
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
