O Canada! > Canadian > Rogers > [Extreme Plus] Utorrent Settings and Rogers

reply to Vindari

Re: [Extreme Plus] Utorrent Settings and Rogers

while im not defending rogers or their traffic shaping policies your evidence is still lacking proof.
and i know rogers moves their throttle boxes around, and different nodes could have different results.

what i am looking at here, is reports when tested of no problems with download, but detection of throttle with upload.

why download packets are retransmitted could be due to a number of issues, one being congestion from a large number of connections and latency on the node, that isnt created when using other protocols.
if packets are killed from other protocols after, it seems more like a connection limit than anything.
therefore any protocol with a large number of connections would also be seeing this issue.

all your evidence points to is a protocol agnostic connection limiting issue, which could just be a node malfunctioning. unless you can prove otherwise, and be my guest.

reply to Vindari

it looks like you're on the 10mbit/sec DOCSIS2 network, is that right? from what I can gather it's only affected the 25Mbit/sec DOSCIS3 users.

reply to the cerberus

reply to Vindari
I only download a few torrents a week, but I've noticed a huge drop in speed over the past few weeks (Fredericton, NB). We're on Extreme.

My speeds were horribly slow when I first got Rogers, but magically increased as soon as they put on a bandwidth limit and started charging for overages. Now my speeds have gone back to the bad old days, dropping from 300-500 kB/s(sometimes more) to 2-20. My regular access (browsing) speeds are fine and speedtests come out normal, so Tech Support claims nothing is wrong.

The problem for me is that I work from home and use Remote Desktop. What ever Rogers has changed has had a truly crippling effect on my connection to the work server. It used to be just like working directly on a computer, but now my remote connection takes several seconds to respond to any command. Even typing in text is painful.

I noticed this issue well before the torrent slowdown problem.

reply to the cerberus

reply to the cerberus

And that's not an impossibility if Rogers recently upgraded their CMTS firmware! But it still is unlikely to be protocol sensitive.

When Rogers first introduced their throttling, they would just simply drop packets on their uploads ... any packets. This meant that any http: downloads going on could be slowed because they didn't get IP acks back. That seemed to ease off with time ... maybe because the service engines were more focused on dropping only packets on connections known to be torrents.

Since nobody in my house does torrents, I really can't properly test what's going on, but I would guess that Rogers has had a firmware upgrade on the p-cube service engines from Cisco and the new firmware has returned to the more agressive throttling. Whether Rogers requested/intended/wanted this more agressive behaviour is open to question, but I would similarly guess that with faster speeds being rolled out they noted more potential congestion and wanted more aggressive throttling.

As I said ... those would be my semi-educated guesses based on Rogers previous behaviour.

Complaints about throttling in the past largely went nowhere except to get rid of collateral damage from the throttling (like detecting encrypted email as being P2P!). That's about the best you can hope for that they'll ease back eliminating collateral damage.

reply to the cerberus
I think you're missing the part that this is Canada wide, not just localized to one area. Your argument is negated by this fact.

Not really, my node (richmond hill) is unaffected and your argument is negated by that fact.
Encryption still completely negates the throttle (on my node) and I have no problems with SC2 dropping out.
I do however get large amounts of latency if I am running torrents while playing online games, and it is not a wise idea because the torrent protocol does not care about latency.
If Rogers upgraded some nodes and not others with a faulty upgrade it could have caused the problem.

To prove that it is protocol agnostic one would have to open a large number of connections with another protocol to see what happens.
Since my node is unaffected I cannot test this.

reply to Vindari
Well, Rogers has in the past throttled some nodes and not others ... some phubs and not others. So that negates your negation!

reply to the cerberus

It's happening in Guelph too... bad old days are back. 10Mbps reduced to 150kB/s in the last week.

reply to shaded
Extreme plus.
this morning i was torrenting several files at 2.3 MB/s with many connections.
tonight i eat my own words, connection limiting has begun on my node, perhaps i should not have spoken. i feel your pain.
i will conduct some tests on protocols and report back.
so far what ive got is 1 connection can yield 25Mbits on speedtest.net
3 well seeded torrents, start one, goes to about 500-800kb/s, start another, goes to about 500kb/s got about 35 connections, start the last and it goes 10kb/s adds only another 5 connections out of 20, in total limited to about 1MB/s.
stop them all.
restart the same 10kb/s torrent, now is 500-800kb/s start another random one, goes 500, hit around 35 connections, start the last goes 10kb/s with 40 total connections at about a total of 1MB/s
yuck i see what you mean.
(sidenote: in total im at around 50 connections with some http, msn, antivirus running (but not downloading while testing) in the background)

UPDATE: new test, changed my router WAN MAC for a new ip, restart the 3 torrents, 3MB/s 80kb/s up tons of connections (over 100), whoa, this is ip targeted. will let you guys know if it starts up again

took about 10 minutes, just long enough for my torrents to finish.
started a new 3, same old results. yuk. and yet somehow upload remains unthrottled with encryption on (managed to get 100kb/s to 3 peers) but the connections are limited to about 50.

See, told ya.... Rogers is fucking with us again.

i'm trying to confirm if the older DOCSIS 2 10mbit/sec service has this throttling, so far the only person i know who has it says he's still getting full line speed (1MB/sec), can anyone else confirm this?

so far the only way to get around this is to use a VPN.

reply to Vindari
The Cerberus:

I was able to do that exact same thing with changing my WAN MAC, like a month ago, but now once I read your update I tried to do it agian, Yea NO luck here anymore, I was get the same ip number, I even changed firmware to DDwrt, yep same IP...

Even changed routers I cant beleive it I still get that same IP address. and yes my torrents are sloooww

I'm on the 10/1 service and only download is throttled.

some good news from somebody at Rogers:

"The investigation is still ongoing but here's what I've been able to find out. Rogers recently made some upgrades to our network management systems that had the unintended effect of shaping non-p2p file sharing traffic under a specific combination of conditions. We will be rolling back this upgrade until we can resolve these issues, but the rollback will take a few days. Meantime, we're continuing to look into some of the other issues that have been raised."