| reply to Gragnor
Re: Hidden traffic limits placed on P2P activity
I understand a lot of torrent trackers block the default port (6669?) that bit torrent runs on because some ISPs do block that port, and most law enforcement/traffic monitoring by software license compliance companies still use those ports. (Cause they're always behind the curve.)
What I describe is not altered by changing the port used.
If you change your port and either manually forward ports to your PC, or use UPnP or zeroconf (for airport users) on your router along with a UPnP/zeroconf compatible client you should have no problems. I don't have any problems.
You may not have problems because Comcast may not be regulating P2P at your node [yet]. Many other folks report problems like those I have decribed.
Is there any chance you're using a router without any type of port forwarding? Bit torrent has a heck of a time working behind NAT without it.
Other bittorrent clients have no problem connecting to my client. I am not using a router. The issue is that Comcast is forcibly closing P2P connections.
I don't think you fully understand what I described or what is going on. - perhaps you should reread about it at these links:
»[Connectivity] Comcast appears to be limiting bittorrent seeding |
