Andrew Sackville-West wrote: >>1) Don't use port 6881. Pick something random in the 49152-65535 range. > > Are you suggesting this for a reason? or just for diagnostic purposes. I don't do much with torrent, but once in a whileI do and it never seems to quite work very well. and yes I port forward something like 6881-6999 or some such. just curious I've already replied to that question on this thread. But basically it makes it harder for ISPs to censor p2p traffic, as they've started doing of late. If everyone picks a random port in the unassigned port range (49152-65535) there's not a whole lot the ISPs can do short of block the whole range, which would in turn break a lot of things. IMO a good solution to ISPs censoring bittorrent traffic would be to have all traffic (tracker and data) wrapped in TLS or SSL and have the port number change every tracker update. The last random port would be left open for clients that hopped aboard the tracker right before the last update. E.g. when a torrent is started, pick a random port A in the unassigned range, open it for traffic and notify the tracker. At the next update, pick a new port B, open that one and send the new port to the tracker. Next update pick yet another port C, open that one, inform the tracker of port C and close port A. Next update, open D, give D to the tracker, close B, and so on. Everyone's happy, providing that every client updates on roughly the same schedule. Watch ISPs try to filter that. The TLS/SSL wrapper keeps them from filtering by analyzing the protocol. -- Chris Howie http://www.chrishowie.com -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/IT d-(--) s:- a--->? C++(+++)$> UL++++ P++++$ L+++>++++ E--- W++ N o++ K? w--$ O M- V- PS--(---) PE++ Y+ PGP++ t+ 5? X- R(+)>- tv-(--) b- DI+> D++ G>+++ e>++ h(--)>--- !r>+++ y->+++ ------END GEEK CODE BLOCK------
Attachment:
signature.asc
Description: OpenPGP digital signature