hockeynomad
join:2007-06-19
Mississauga, ON | Setup Multiple VPN servors to combat Bell Throttle?
A friend of mine just signed up with Acanac and they will do the above stated:
»community.acanac.com/acanac/view···throttle |
|
Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC
 ·Colbanet
·TekSavvy Solutions..
| 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. |
|
Turbinator
join:2007-10-14
Mississauga, ON | reply to hockeynomad
Oh, that's one bad ass ISP. I'll stay here and see if TekSavvy does the same. |
|
Name
@teksavvy.com | reply to hockeynomad
It will not help.
Bell is limiting all VPN traffic to 30kbytes/sec regardless of destination or volume. |
|
Flannel
join:2007-11-28
·Bell Sympatico
| 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. |
|
Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC | 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. |
|
TemporalFlux
Premium
join:2003-08-07
Ont, Canada
 ·Rogers Hi-Speed
·TekSavvy Solutions..
| 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? |
|
Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC
·Colbanet
·TekSavvy Solutions..
| 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. |
|
TemporalFlux
Premium
join:2003-08-07
Ont, Canada
·Rogers Hi-Speed
·TekSavvy Solutions..
| 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? |
|
canadabound
join:2008-03-27
·RCN CABLE
| said by TemporalFlux  :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 But it's nothing to do with usage. You're falling for their propaganda. Even if you did keep the pipe "close to full" they wouldn't care.
This issue is about greed and how much money they can extort from the public. The solution is not to fill their pipes with data but to empty their pockets of cash. |
|
Flannel
join:2007-11-28
·Bell Sympatico
| reply to TemporalFlux
said by TemporalFlux :[...]That will fill up the pipes! Yeah, it's pointless and lazy passive aggressive terrorism. If you want to actually make a difference you need to take the time to make logical sense and affect change from the top, in this case, the regulators/government. |
|
anonman
@teksavvy.com
| 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). |
|
Deadpool
Go Sens Go
Premium
join:2001-03-29
Canada
·Bell Sympatico
| reply to Guspaz
said by Guspaz :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. Historically what we've seen with Sympatico customers is that their VPN/SSL/SSH/encrypted data would be impacted if they were to use a non-standard port for those applications.
For example, using Port 50,001 for SFTP (official port is 22). This causes confusion and ends up being affected as a "better safe then sorry" type rule.
--
Leafs lead season series 4-3  ...GO SENS GO  |
|
Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC
·Colbanet
·TekSavvy Solutions..
| said by Deadpool :Historically what we've seen with Sympatico customers is that their VPN/SSL/SSH/encrypted data would be impacted if they were to use a non-standard port for those applications. For example, using Port 50,001 for SFTP (official port is 22). This causes confusion and ends up being affected as a "better safe then sorry" type rule. That's the problem with relying on the test results of others; you often lack all the details. The one user who is throttled and had unfettered SCP did show his entire commandline, which lets us verify that he's on the standard port (22). The other people posting results, I don't believe they confirmed which port they use.
I must admit, the "better safe than sorry" policy is a bit worrying. It implies that all existing (but not yet classified) or new protocols will be throttled until Bell decides to whitelist them.
That said, I'll be happy enough if VPN/SSL/SSH/etc connections are, when used in a standard way, not throttled. Writing HTTP tunneling applications to be able to get an NX remote desktop connection to my server might be fun, but a waste of time :P |
|
excaliber
join:2007-04-18
Laval, QC | 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? |
|
Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC | As long as SSH on port 22 isn't throttled, worst case is you tunnel VNC  |
|
excaliber
join:2007-04-18
Laval, QC
edit:
March 28th, @05:46PM
| 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. |
|
Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC
edit:
March 28th, @05:50PM
| 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. |
|
Deadpool
Go Sens Go
Premium
join:2001-03-29
Canada
·Bell Sympatico
| reply to excaliber
said by excaliber :What does Bell consider to be the "official" standard ports for various services? I use RealVNC on port 5900, would this be allowed? It's not so much what Bell considers "official" moreso then what's been defined as "official" by the IANA (Internet Assigned Numbers Authority).
See here: »en.wikipedia.org/wiki/List_of_TC···_numbers
And here:
»www.iana.org/assignments/port-numbers
--
Leafs lead season series 4-3 ...GO SENS GO |
|
Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC | 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). |
|
