Slashdot Mirror
Comcast Raises Bandwidth in Shot at DSL
bigtallmofo writes "In a move sure to be applauded by DDoS botnet owners everywhere, news.com.com is reporting that Comcast is raising the speed of its cable Internet offerings. The standard rate will change from 3 Mbps downstream and 256 Kbps upstream to 4 Mbps downstream and 384 Kbps upstream. Customers that currently pay extra for faster service will see a 50% speed increase over what they have today to 6 Mbps downstream and 768 Kbps upstream." Combine this move with the VoIP announcement and the rumblings about more Baby Bell mergers -- we should see an...interesting landscape soon.
Doesn't matter how much more bandwidth you're given if you can't use it without fear of getting a letter saying you're over whats considered reasonable bandwith use in your area, which is why I've stuck with 1.5m/384k DSL.
comcast also has invisible bandwidth caps of which they have been reluctant to publicly disclose. for those that have sbc's 6/608 or verizon's 3/768 service available to them, i would suggest dsl instead. oh yeah, comcast only gives out a paltry 2GB of newsgroups transfers, further diminishing the value of their services compared to dsl offerings with unlimited newsgroup access.
Their keeping your bandwidth low has less to do with the wiring between you and them than it does with the head end setup. Most cable modems support data transfers around 40mbs, each way. Most cable companies do not have enough bandwidth or hardware at the head end to support so a large number of people having so much bandwidth... so they cap you nice and low to keep their network running fast.
Help Brendan pay off his student loans
Comcast won't allow servers, but most DSL providers do, and they don't block your ports either usually. SBC lets you opt-out of any port blocking they do (currently just some outbound port 25 blocking I think, but only for the residential package)
Morphing Software
Really, it sounds more like a question about a change to their TOS, actually.
This is easily solved by services like DynDNS. But it's still in violation of the TOS.
I've been using it for sometime and never had a problem with them, however. But then, all I have is a crappy webpage I rarely update. Other than that, it's primarily so I can map my domain over to my DHCP addy and get to my mailserver (I don't use their mail services -- rather host my own thanks), move stuff around with scp or admin things with ssh remotely.
If you never make mistakes, it's probably because you're not doing anything.
"(xiv) run programs, equipment, or servers from the Premises that provide network content or any other services to anyone outside of your Premises LAN (Local Area Network), also commonly referred to as public services or servers. Examples of prohibited services and servers include, but are not limited to, e-mail, Web hosting, file sharing, and proxy services and servers;"
Insert Generic Sig Here:
Few people understand how Cable bandwidth actually works. It all hinges on your QAM modulation and the number of customers combined to the downstreams and upstreams. The max dowstream bandwidth at docsis 1.1 per cmts blade is about 35Mbit and the max upstream is roughly 10Mbit. This is at 256 QAM on the downstream and 16 QAM on the upstream and upstream channel width of 3.2Mhz. Now I manage 18 CMTS in my day job, that average customer count per blade is around 1250. Each blade has it's own downstream channel and 6 upstreams. So now you have 35 Mbit on the downstream shared between 1250 customers and approximately 125 customers sharing 10 Mbit up. You can get more bandwith by reducing the node combining down to a 1:1 ratio where each node has it's own upstream channel but that involves plant redesign work and additional investment in more CMTS's (big $$$$) and by running different frequencies. But the big gain would be to move to docsis 3.0 (2.0 only offers an additional 10Mbit on the upstream) where they say each downstream channel will be able to offer 200Mbit down and 100Mbit up. And yes I am a RF Network Engineer.
Cable modem companies had serious performance problems in the early years - cable TV distribution equipment was pretty shoddy, and the cable modem equipment was relatively experimental, so the native performance wasn't very good, and they didn't have any effective way to limit user's upstream bandwidth. They were absolutely terrified that somebody would trash their neighborhood's cable modem performance by using too much upstream, and especially terrified that the bandwidth would be hogged by somebody running a Pr0n website, back when pr0n on the internet was still a somewhat scandalous concept. Their performance really wasn't all that good, and Pac Bell's "Web Hog" TV ads, while dishonest, were extremely effective.
So they made inflexible hard-core policies against running anything server-like, and it became a religion for them. The fact that they didn't understand what a "server" really was wasn't relevant - an Instant Messaging client is a server, and interactive game programs are servers, and they like both of those, and "email servers" don't consume scarce upstream bandwidth, they use plentiful downstream bandwidth.
Napster was another big issue - not only was it a bandwidth hog, but it was Pirating Content, and TV stations are really in the content business so that was obviously Bad Bad Bad. Not everybody at Comcast was clueless - when I talked with some of their engineers privately, their opinion was "Like, duh, why do you *think* people buy broadband? It's so they can download music faster, and Napster's the best marketing tool out there for us, even if we officially pretend to hate it."
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
Try Speakeasy.
As one of their tech support told me the other day, "That's the great thing about Speakeasy, you buy the connection from us, and then do whatever you want with it."
That was in response to, "can I sell wireless internet to my neighbors, and not tell you about it?"