Frequently Asked Questions
 

Q1. Why does everyone have to do this?

Sandvine sends RSTs to both sides of the connection, but only one side of the connection needs to receive an RST to cause the transfer to fail.

 Q2. Okay, I followed your instructions, but now uTorrent/Azureus shows a red triangle/red circle in the status bar!

It's a known problem with forcing an outgoing port range in Windows. You are still clever, your torrent client is just adjusting to using fewer outgoing ports. There is no known fix.

 Q3. My torrents are failing to update and they come up with an error like "Only one usage of each socket address..."

This is a known problem with forcing a single outgoing port in Windows.  Try using an outgoing port range instead.  See the Windows page for an updated firewall configuration that allows you to use an outgoing port range. 

Q4. This isn't a solution!  The solution is to drop Comcast/write to the gov't/contact the EFF!

While I wish you the best of luck, I doubt you'll get anywhere.  In many rural areas Comcast is the only low latency high-speed provider available and that is unlikely to change anytime soon.  Given the current media response to BitTorrent I doubt the government will do anything to promote Net Neutrality as it relates to throttling BitTorrent traffic and, quite honestly, the EFF has better things to defend.  In the meantime, this is the only way to show Comcast that their throttling measures are utterly pointless and hopefully, dissuade them from implementing any more throttling measures.

 Q5. Hey, this works great.   How can I thank you and shower you with eternal gratitude?

 Easy.  Make a peanut butter and jelly sandwich, buy a 20oz bottle of Gatorade, and give it to that homeless guy on the corner.  Ask him how his day is going.  And don't just walk away... listen to him.

 Home 

waffle recipes