main
Report a problem

FCC moves toward prohibiting Comcast traffic management

Daniel Fleshbourne   on 11 July 2008 - 15:12 · 12 comments & 8115 views

Advertisement (Why?)
Amid news reports that the U.S. Federal Communications Commission is moving to prohibit Comcast from throttling BitTorrent traffic on its broadband network, a Comcast official said the agency has provided no guidance on how to deal with network congestion. The Associated Press reported Friday that FCC Chairman Kevin Martin will recommend that Comcast be reprimanded for slowing peer-to-peer BitTorrent traffic. Comcast says it throttles the P-to-P traffic only during times of peak congestion, but Martin and a study from the Max Planck Institute for Software Systems in Germany have contended that Comcast blocks BitTorrent traffic during off-peak hours as well.

Martin told The Associated Press that Comcast's actions have violated FCC principles intended to protect Internet users by arbitrarily blocking some traffic and not telling its customers. The so-called net neutrality principles say ISPs (Internet service providers) shouldn't block or impair legal applications unless the blocking is part of "reasonable network management." Comcast does not block any Internet traffic, and only slows a small percentage of P-to-P uploads, said Sena Fitzmaurice, Comcast's senior director of corporate communications and government affairs. In most cases, the upload begins within a minute, she added.

View: The full story @ InfoWorld

Post a comment · Send to friend Comments · There are 12 additional comments
(2 replies) #1 X'tyfe on 11 Jul 2008 - 15:54
heres a hint: upgrade your network
#1.1 snyper256 on 11 Jul 2008 - 16:47
Exactly.


No, Comcast, you're not going to fix any bandwidth problems by limiting your users. It's called "growth" and the bandwidth usage will continue to do that whether or not your network can handle it.

They're running out of band-aids - soon they'll have to actually make upgrades in order to have a somewhat functional service.
#1.2 toadeater on 12 Jul 2008 - 05:12
(snyper256 said @ #1.1)
Exactly.


No, Comcast, you're not going to fix any bandwidth problems by limiting your users. It's called "growth" and the bandwidth usage will continue to do that whether or not your network can handle it.

They're running out of band-aids - soon they'll have to actually make upgrades in order to have a somewhat functional service.


I don't think they're really worried about bandwidth. What they're trying to do is set a precedent so they can charge for "premium" content like streaming video, and also so they can eventually control what content their users would have access to. They want it to work like cable TV, where you have to subscribe to content. Imagine if you had to pay Comcast to get access to Youtube--that's what they dream about.

It's the Net Neutrality debate again. Throttling should be illegal because what they're doing is sabotaging traffic that originated outside their network. They have no right to mess with it.
#2 -Hiroshi- on 11 Jul 2008 - 16:03
Interesting, never thought that the FCC would be in on net neutrality and help protect users on the internet, go figure. I don't care if Comcast throttles P2P activity during peak hours, I don't torrent that much to care, and when I do, I usually find an HTTP alternative, the only time in the past three to four weeks I ever used torrents, was to download Ubuntu 8.04.1 64-Bit.
(5 replies) #3 +Space Guy on 11 Jul 2008 - 16:13
When i'm getting anything from torrents my whole internet connection slows to a crawl. My other computers keep getting page cannot be found errors. Only after multiple refreshes does it load anything. It doesn't matter what the upload/download is from the torrent.
#3.1 Gio Takahashi on 11 Jul 2008 - 18:11
That might have nothing to do with throttling, but more to do with your client. Especially when you're upload speed is clogging up your bandwidth, you may want to check that first.
#3.2 chilliadus on 11 Jul 2008 - 19:24
(Gio Takahashi said @ #3.1)
That might have nothing to do with throttling, but more to do with your client. Especially when you're upload speed is clogging up your bandwidth, you may want to check that first.


Exactly. Many people don't know that without proper traffic shaping upload kills your download.
#3.3 ermax on 11 Jul 2008 - 19:48
You need to limit the out going bandwidth in your BitTorrent or P2P client. If you use up all your outgoing bandwidth then how do you expect to be able to make outgoing requests to other servers for more data?

You may also want to look into implementing QoS on your router. Then it doesn't matter what your torrent client does your router will always reserve a little and give priority to web traffic.
#3.4 axebox on 11 Jul 2008 - 19:53
I had the same exact issue, and throttling bandwith did nothing to solve it.

The issue is with the max number of incoming and outgoing connections. BitTorrent (the client) has 500 incoming (and a lower number outgoing - I forget), which is significantly higher than the max # connections that comcast allows. If you set those numbers to be lower you'll solve your problem. I'm using 300/150, incoming/outgoing, and that works for me, but local comcast networks vary.

Good luck.
#3.5 GreyWulf99 on 12 Jul 2008 - 20:45
(axebox said @ #3.4)
I had the same exact issue, and throttling bandwith did nothing to solve it.

The issue is with the max number of incoming and outgoing connections. BitTorrent (the client) has 500 incoming (and a lower number outgoing - I forget), which is significantly higher than the max # connections that comcast allows. If you set those numbers to be lower you'll solve your problem. I'm using 300/150, incoming/outgoing, and that works for me, but local comcast networks vary.

Good luck.


The problem is actually more of Windows XP and Vista limits on the maximum number of half-open connection attempts. With XP the default is 8 I believe, and barely higher with Vista. Torrents will easily saturate the limit and cause browsing to be almost unbearably slow unless you limit the torrent clients max half-open attempts to an even more ridiculously low number than the OS, or hack the tcpip.sys to allow more connection attempts, which can now be done even with Vista x64.
I'm not sure if the XP SP2 fix works for SP3 or not, but its worth a shot: http://www.yaronmaor.net/repair.htm

Also, you dont want your upload limit of the torrent client being set to more than about half of the maximum upload speed. I find that 40% or so of the max upload speed seems to be the sweet spot. Until recently, this was 17k/sec with Comcast. The limit was recently multiplied by 3, so I can comfortably set it up to about 50k/sec.

Last edited by GreyWulf99 on 12 Jul 2008 - 20:51
#4 axebox on 11 Jul 2008 - 19:56
One last note: I believe comcast uses your auto dns against you when using torrent software. I experienced significantly higher downloads when using opendns.org's dns. Try setting these on your router.

Also, if you haven't already make sure you're forwarding non-standard (just choose a random #) port for your torrent connections on your router. Use start->run->"cmd"->"ipconfig" and make sure your local ip address matches the forwarded port on your router.
#5 Xtreme2damax on 11 Jul 2008 - 22:35
Comcast users think they have it bad, wait until they see what I have to deal with. Perhaps the FCC should do something about this:

http://www.hughesnet.com

Take a look at their policies, specifically the Fair Access policy, their prices and what happens after you exceed their limit. Also the speeds/latency sucks compared to normal broadband.

However it's my only means to access High Speed despite how crappy it is and despite the restrictions I can browse faster than Dial-Up users and some Youtubing, as well as minimal downloading.

Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!

Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.

Advertisement (Why?)