same problem here in london.... initially occurred two weeks ago then was fine for a week then it started again last friday. tried just about everything i could think of to fix but no luck..... then found this thread with possible explanation, thanks. just another reason to hate rogers.

note, rogers internet usage tracker is still not working for my account.

they can kiss my ass... will switch to another provider if this isn't remedied or a work around isn't found.

same problem here in london.... initially occurred two weeks ago then was fine for a week then it started again last friday. tried just about everything i could think of to fix but no luck..... then found this thread with possible explanation, thanks. just another reason to hate rogers.

note, rogers internet usage tracker is still not working for my account.

they can kiss my ass... will switch to another provider if this isn't remedied or a work around isn't found.
I've already decided to leave Rogers' internet as soon as my 2 years contract is done at the end of April. I'm not a super heavy user (probably about 50GB permonth), but enough is enough. I've found a DSL ISP that offers dry DSL (I have VoiP from Primus and no land line). They're called Teksavvy and I've read nothing but praises for them over at DSLreports.

check your ISP here:
http://www.azureuswiki.com/index.php/Bad_ISPs

I tried a couple of torrents this morning to check what I was getting with Rogers, and I'm still fine (utorrent 1.6: encryption enabled, incoming legacy connections disabled):
http://i85.photobucket.com/albums/k65/99gecko/utorrent.jpg

You sir, are lucky.

Well I tried uTorrent with the exact same settings...not sure what port "99gecko" is using but I noticed the speed dial is dead buried in the sand :confused:
Oh well, I guess Rogers Ottawa has me pegged as an abuser and belled my traffic...:eek:

D

port 34374; not randomized. You should use a port # greater than 10000.
UPnP port mapping enabled (I am behind a SMC Barricade G wireless router/printserver).

If you are using XP SP2, have you tried patching TCPIP.SYS ? Please note however that other forums believe this patch is not actually necessary.

However some people claim this works, and I am one of them. This will let you control the # of half-open connections. I have set my net max half-open connections = 50. Google for "lvllords event ID 4226". But use with caution! I suggest you set a restore point before installing. Also note if you use Windows Update you may have to re-patch.


Limited number of simultaneous incomplete outbound TCP connection attempts— The TCP/IP stack now limits the number of simultaneous incomplete outbound TCP connection attempts. After the limit has been reached, subsequent connection attempts are put in a queue to be resolved at a fixed rate. Under normal operation, when applications are connecting to available hosts at valid IP addresses, no connection rate-limiting occurs. When it does occur, a new event, with ID 4226, appears in the system’s event log.

[edit] I can't remember if port 34374 was default or if I changed it to that.... but if it ain't broke, don't fix it.

I've already decided to leave Rogers' internet as soon as my 2 years contract is done at the end of April. I'm not a super heavy user (probably about 50GB permonth), but enough is enough. I've found a DSL ISP that offers dry DSL (I have VoiP from Primus and no land line). They're called Teksavvy and I've read nothing but praises for them over at DSLreports.
thanks for the info.

i've since tried secureix and things are working much better now.

thanks for the info.

i've since tried secureix and things are working much better now.
I am using secureix as well, but I only see it as a temporary solution. It's only a matter of time before they either start charging for their service, close down due to over-use by people who stay connected 24/7, or they go the not-so-ethical way of having you install some spyware-filled application in order to be able to use their VPNs.

I am using secureix as well, but I only see it as a temporary solution. It's only a matter of time before they either start charging for their service, close down due to over-use by people who stay connected 24/7, or they go the not-so-ethical way of having you install some spyware-filled application in order to be able to use their VPNs.
"Always with the negative waves Moriarty, always with the negative waves."

LOL :D

"Always with the negative waves Moriarty, always with the negative waves."

LOL :D
I call it being realistic. :)

But seriously, I will very soon cancel my Rogers internet despite the $50 penalty that will come along with it and simply switch to Teksavvy. Much less of a hassle.

I am running into the same issue as well along the same timelines. I called and they confirmed they are packetshaping and throttling traffic.

I am dumping Rogers...this is the last straw. They have price gouged me long enough.

Lately, I can't even get 2kbps with uTorrent through SecureIX.

Anyone else having this problem?

I rarely use torrents are is it, but I'm beginning to wonder what it is I'm paying for, because it seems half of the services one could use through the Internet connection they provide are non functional.

I'm seriously eying Tecksavvy.

I just want to add my own frustrations with Rogers to this thread. I don't understand how they can advertise high speed downloads when they throttle them down to nothing.

This is especially disconcerting because they are throttling a protocol. Not illegal downloading. This will become more of an issue as more and more large companies jump on the bit torrent bandwagon to economically distribute their large files.

I'm seriously eying Tecksavvy.

I just signed up w/ TekSavvy earlier today. I didn't expect anything to happen till Monday, but I just got a call from them saying my modem will arrive on Tuesday, and the service activated by Thursday. So far, so good.

I didn't even realize that DSL was available in my area ( Greely ). I kept checking bell.ca every few weeks for years. I finally gave up and resigned myself to Rogers. Had they not done this throttling I probably would not have found out about DSL and TekSavvy. I quess in a way, I could say I'm glad it happened. Now I can dump Rogers HS like I did their pathetic 600Mhz digital TV service.

Glad to hear from another Teksavvy user. My modem should also arrive on Tuesday and I can't wait.

Another unhappy Rogers customer here...would be very interested to hear about how the experience w/ Teksavvy turns out.

ditto!!
Although I have not been slammed by Rogers yet, I can only assume it is coming soon. My bundling expires in the spring so I am starting to look at options now.

At the risk of exposing my satisfaction with Rogers :cool:, I can assure everyone on this thread that I have excellent BT down and upload speeds. I use uTorrent and located in the K-W area.

Got my modem on Tuesday as promised. I was supposed to be connected today, but the line just keeps connecting and dropping over and over :( . Tech support says they're still working on it; I should call tomorrow afternoon if it's still doing this. At this point, I'm willing to give them the benefit of the doubt. When it is connected, I see 1.4 Mbits speed; I hope they can improve on this.

Stay tuned - update when something happens.

Rogers is using a recent upgrade to what were formerly known a P-Cube devices (now known as Cisco SCE 1000 and 2000 Series Service Control Engines). These are designed to do deep application level analysis which means that they can understand exactly which application is generating the traffic regardless of the port number. This means that hiding behind certain ports - even those shared by Rogers' own VoIP solution (ie. port 1720) - is not going to cut it any longer.

Many people have been relying on using encrypted bittorrent traffic which hides the application layer so that it cannot be identified as bittorrent packets. This worked for a while... however, now Rogers has tweaked their systems to identify bittorent traffic through other means. It now appears that they are identifying torrent traffic by doing complex pattern matching and identification against the encrypted packets. They can't see inside the packets but they sure can see the connects and acknowledgments flying back and forth between the P2P hosts. They look for rapid multiple connects to P2P servers and other identifiable patterns. If your system attempts to make multiple connections to one or more P2P hosts in a short sequence and those connections all have the same general parameters it can be inferred that there is P2P traffic within those encrypted packets... I don't know what the parameters are that they look for but like most standardized protocols there are definitely some traffic patterns that are consistent with bit torrent. Ultimately they are guessing but it appears that they are getting pretty good at guessing correctly.

This explains why sometimes the torrent will start up ok, get to a certain point and then the traffic fall off rapidly. Rogers has watched the traffic, seen a consistent pattern and then put a block on it.

SecureIX works better because there are no distinct encrypted connects - it's just one connect to the SecureIX VPN server with lots of discreet packets inside. It's probably just a matter of time until they can tweak out the patterns within the encrypted VPN tunnel traffic that likely are bittorrent. They can't see the distinct messages but the pattern is still there. Perhaps the next generation of P2P will include random traffic generators to mask the real content. Not really a great solution though as it will just increase the type of congenstion that the ISP's are freaking out about (not to mention what it would do to your bandwith usage caps).

Ultimately it's not a pretty picture. The technology to monitor and alter the traffic is hitting a point where the ISP's can allow or deny whatever they want. One thing that I don't understand is why they appear to be putting a hard throttle on the P2P traffic instead of applying 'quality of service' rules to it. QoS would allow distinctions between tiers of services such that services that have latency issues (VoIP, etc.) could be high priority, 'core' services (http, https, smtp) have a medium priority and everything else (P2P, etc.) would be able to use whatever is left over. That way everybody can do their online banking without being impacted by bittorrent and the P2P services will continue to work as best as the network will support.