zincPremium
join:2004-02-17
Kitchener, ON
1 edit | The "what works and what doesn't" thread In case of the possibility of this not being resolved in a timely manner, let's put together a list of what works and what doesn't.
1. Please keep this clean, no bashing, outrage, etc. We all know they suck already..
2. Please only post things you've personally tested... e.g. HTTP download is fast without VPN, but 10KB/s with VPN.
3. Make sure you test during throttle hours (4:30pm - 2am) as noted here: »/r0/download/1···ar28.pdf
4. Note if you've tried it on non-standard ports and what application if applicable.
I'll start it off...
Working:
HTTP
OpenVPN over UDP with DHkey
Nortel Contivity VPN
CS:S, CS1.6, TF2, World of Warcraft
Throttled:
FTP over SSL (FileZilla + vsFTPD/SSL)
Bittorrent - uTorrent (any port, encrypted or not)
World of Warcraft updater (afaik - glorified torrent client with [slow] HTTP fallback) |
|
|
|
| We've already seen contradictory reports from different people. For example, HTTPS:443 works for some people but not for others. Because of this, it's probably impossible to come up with a conclusive list of what's blocked and what isn't.
Based on how signature-triggered deep packet inspection operates, it's quite possible that some protocols will be allowed or disrupted based on the exact brand and version of the software used by both the client and the server. For example, connecting to an Apache HTTPS server using Mozilla might work while connecting to an IIS HTTPS server using WGET might not. Because every server and client has subtly different connection semantics, ensuring that a given protocol will always work would require Bell's DPI boxes to have a whitelist signature for every possible client-server permutation.
I'm not saying that putting together a list of accepted/blocked protocols is a bad idea. Rather, I'm just pointing out that a 'working' report from one person is not an authoritative guarantee that a given protocol will work anyone else at any other time. That said, I strongly urge everyone to participate as lists of blocked applications are extremely important for PR and legal fight purposes.
I will post my findings when service degradation hits my area.
--
Coridon Henshaw -=- »www.talisiorder.ca |
|
 GuspazGuspazPremium,MVM
join:2001-11-05
Montreal, QC
kudos:16 | reply to zinc
Not throttled:
Standard PPTP VPN (MPPE encryption) |
|
| My scp/ssh is not being throttled. There is a second person to confirm this.
(Oh mppe, how I long for your ppp goodness...) |
|
| reply to zinc
What about third-party nntp? anyone? |
|
| reply to Guspaz
Have you tried L2TP with IPSec yet? |
|
1 edit | reply to cutoff
I'm downloading encrypted NNTP at full speed. My bittorrent is throttled. If I do both at the same time, encrypted NNTP is still not throttled. |
|
| reply to zinc
Everything encrypted I've tested has been throttled at 30KB/s in downtown Kingston... BT (duh), SFTP, IMAPS... |
|
| reply to zinc
3pm Today:
Throttled: Protocol: SSH-2.0-OpenSSH_3.8.1p1 Debian-8.sarge.6 (can't even connect properly)
7pm Today:
SSH2 (the above) is not throttled
BT is usually throttled on my account. Can't say specifically about today though. I'm with Sympatico in Toronto.
Strange that I was shut out earlier today but not this evening!
--
"a nerd is very similar to a geek, but with more RAM and a faster modem." |
|
 LiQuiDBSD geekPremium
join:2002-08-08
Anjou, QC
1 edit | reply to derekm
said by derekm:My scp/ssh is not being throttled. There is a second person to confirm this. (Oh mppe, how I long for your ppp goodness...) Present.
For the reccord, it appears sshd needs to be running on it's standard port 22 to work properly. The two people I heard from directly that did have problems with scp were not running on port 22.
So much for DPI looking beyond port number... |
|
