O Canada! > Canadian > TekSavvy > Setup Multiple VPN servors to combat Bell Throttle?

Setup Multiple VPN servors to combat Bell Throttle?

Reports are that VPNs are throttled too. Deadpool says they're not supposed to be, but then we have tests that show SCP is being throttled.

It's likely that any solution will have to masquerade as HTTP. We'll be investigating possible options once the throttling hits Montreal. Hopefully it won't come to that, hopefully the League of Independent ISPs (a name I made up) will get an injunction.

reply to hockeynomad
Oh, that's one bad ass ISP. I'll stay here and see if TekSavvy does the same.

reply to hockeynomad
It will not help.

Bell is limiting all VPN traffic to 30kbytes/sec regardless of destination or volume.

reply to hockeynomad
When I was with Sympatico and they started throttling, encrypted VPN was affected (Because Bell wants to prevent P2P obfuscation / encryption, which was originally the work around to throttling). However you try to hide/mask P2P, if Bell wants to throttle it, they will, even at the expense of throttling other services.

Luckily, HTTP is the one service they can't throttle. And if they did, then they'd be in a lot more trouble, which is good.

We should get a server at the TS POP and use HTTP to download from /dev/zero and on our machines (Linux etc) download it to /dev/null. That will fill up the pipes!
--
If you need a compiler to compile a compiler then where did the first compiler come from?

Once again, no. That will only serve to saturate TekSavvy's four GigE pipes, destroying service for all TekSavvy customers, without significantly impacting Bell.

Colocating a box with TS is indeed under consideration, but we're waiting to gather more information on the exact nature of Bell's throttling before we pursue it any further.

Agreed. We need to have something monitor the bandwidth usage and throttle the /dev/zero server so that we keep the pipes close to full all the time but don't impact the performance of the customers. hehe
--
If you need a compiler to compile a compiler then where did the first compiler come from?

reply to TemporalFlux

said by TemporalFlux:

[...]That will fill up the pipes!

reply to hockeynomad
well, Id like the government to step in asap like anyone else, but we all know that it will take time for anything to occur. I think investments into other ideas fro the time being should be viewed. Perhaps this will help decision makers realize that what bell is doing is going to just create a cat and mouse chase across all the commonly known protocols on the net. Eventually everything will become capped not heading directly towards bell site or we get this resolved. But until it gets resolved, the throttling is hard to live with (Homer throttling Bart Like Sympatico Throttling other ISP's).

reply to Guspaz

--
Leafs lead season series 4-3 ...GO SENS GO

reply to Deadpool
What does Bell consider to be the "official" standard ports for various services? I use RealVNC on port 5900, would this be allowed?

As long as SSH on port 22 isn't throttled, worst case is you tunnel VNC

The whole point of buying the realvnc enterprise edition is to not have to use something else to create a tunnel. If it gets throttled then the major selling point of the product is worthless.

I don't see anything that particularly would avoid the use of a tunnel. Regardless, I'm merely pointing out a potential workaround. While the throttling sucks, we've got to deal with it until it's gone.

reply to excaliber

--
Leafs lead season series 4-3 ...GO SENS GO

Neither list has anything but 5900 for VNC, while VNC setups sometimes use the ports 590x where x is the display number (display 1 is port 5901, display 2 is 5902, etc).