Jump to content

Whats in store for v1.3.X and above...


churchi

Recommended Posts

Posted
Second, you don't need UDP for hole-punching, it can be done over TCP as well. And personally, I'm not for hole-punching anyway. It's nice, but hides the fact that something is not properly configured. UPnP and Portforwarding should be used instead. And on most other networks, I always get the best speeds from Firewalled nodes! :-)

UPnP has proved to be a BAD configuration choice for a huge number of users. Many routers either poorly support it or cannot handle it when max connections tops over 100. Manual Port-Forwarding is simply a better choice if it's available at all, but it requires configuring router and computer/s on the network which is alot to do for people unfamiliar with networking.

UDP hole-punching is not the same as simply making the connection unfirewalled. UDP hole-punching is for the cases where users cannot access the router between them and the rest of the internet (such as at some colleges or businesses, even though they are legally allowed to use BitTorrent over them) or don't know how. There is many cases of this.

A similar trick with TCP simply CANNOT BE DONE.

UDP hole-punching takes advantage of most router's proper behavior of reusing connections. It is not an exploit. 2 firewalled-by-router connections can directly transfer files to/from each other without a proxy in the middle when it is done correctly. Even some software firewalls will allow access this way.

From what I've read, the official BitTorrent client already supports UDP hole-punching. No doubt other clients will follow suit.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...