How to defeat Bell Canada traffic throttling

p2pnet news P2P | Freedom:- “This seems to work. It’s 10:30pm and I’m pulling 450kb/s down.”
That’s effbell on dslreports.
Subject?
Bell Canada bandwidth throttling.
Solution?
A, “fundamental flaw in the Traffic Management Solution championed by Bell Canada is revealed when one considers exactly how they dealt with the problem of encrypted traffic.” says Per Vices Corporation CEO Victor Wollesen, going on >>>
Forced to associate VPN connections with a specific port, they make it trivial for users of peer-to-peer applications to bypass the DPI.
A user wishing to download content via BitTorrent needs only to configure their client to use the VPN TCP port to transfer content, associate any remaining UDP ports with the standard IPSec Authentication and Encapsulating UDP ports, and strictly apply protocol encryption to all incoming connections.
What makes this really interesting is:
It comes in a Per Vices submission to the Canadian Radio-television and Telecommunications Commission (CRTC).
It adds:
“This effectively circumvents throttling by the DPI device, at the trivial cost of running an application over an unorthodox port. In contrast, VPN clients using unique ports remain throttled.”
Now you know
(Thanks, Luvie)
Jon Newton – p2pnet
.
.Stumble It!
Subscribe to p2pnet.net | | rss feed: http://p2pnet.net/p2p.rss | | Mobile – http://p2pnet.net/index-wml.php
Net access blocked by government restrictions? Use Psiphon from the Citizen Lab at the University of Toronto. Go here for details. Download here.






July 8th, 2008 at 11:52 am
money spent on throttling software = waste of time
July 8th, 2008 at 11:53 am
knew someone would figure it out one day.
cheers to all involved
July 8th, 2008 at 12:45 pm
And which port is that? 1194, 1723 and 5000 seem to be candidates according to:
http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers
July 8th, 2008 at 3:24 pm
its at the bottom of page 3/5 of the PDF Document which bell submitted
*The standard VPN TCP port is 1723/TCP, with IPSec key exchange protocol using UDP port 500/UDP, and TCP port 50
and 51 for IPSec Encapsulating Security Protocol, and IPSec Authentication Header traffic respectively.
July 9th, 2008 at 8:38 am
Time to switch up the ports… you think other ISP’s use the same kind of technique?
July 9th, 2008 at 9:57 pm
If you’re on TekSavvy or any other isp that supports MLPPP (Multilink PPP), this will bypass the throttle. I’ve been using MLPPP over a month to bond my 2 DSL lines together to make 1 faster internet connection, and it also has the added side-effect that the DPI boxes don’t “see” it due to the different PPP packet encapsulation, thus why it bypasses.
August 24th, 2009 at 8:40 pm
So how does one defeat the Bell DPI (Deep Packet Inspection) a lot of talk no real explanation.
you can’t just change the TCP port uTorrent uses (It doesn’t work) how would I use IPSec to Encapsulate my packets? Wouldn’t I have to have a VPN with Bell?
Anyone wanna break this down to plain english – maybe provide how to with uTorrent (most prolific)
September 11th, 2009 at 12:59 pm
http://www.dslreports.com/forum/r22141654-Evading-throttling-with-uTP-uTorrent-19a