Markus 'guruz' Goetz writes:

can we have another DEFAULT tcp port in 0.92 ?
This would help people that have it blocked or slowed down.

I have also thought about this. I've seen many ISP blocking or limiting the bandwith to the default ports. In my case, I cannot connect to any 6346-6348 ports from my home dialup. I've done some tests and it seems to be my ISP upstream provider.


How about a randomize listening port option? Say pick a random port number between 5000-30000. Eventually it could become the default. It would help the clueless user who doesn't know about tweeking the listen port.

OTOH, netadmins will hate this, becoming even more fascist ;) Perhaps just a simple mention on the README file would do:

Q: Gtk-gnutella thinks I'm firewalled, but I don't think it is so. What do I do? or Downloads are always so sloow, what can be wrong?

Ans: Perhaps your ISP (or your ISP's upstream) is blocking restricting the default gnutella port. Try changing the listen port number to another unused* number between 1024-32767 and see if the firewalled status changes after a while or the download/upload speed improves.

*you can do a netstat -ta to see which ports are currently used.

--
Feel free to use the above in the documention.


Cheers,

-Rafael

Rafael Reilova
http://www.magepr.net/




-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
Gtk-gnutella-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel

Reply via email to