Slashdot Mirror
RoadRunner Blocking Use of Kazaa
An anonymous reader submits: "You should know that RoadRunner is quietly blocking the use of Kazaa in
certain markets. Particularly in Texas, they have some sort of port scanner
in place which scans for Kazaa activity and then disables use of that port,
rendering the program completely useless. Grokster, iMesh, and all other
FastTrack programs are similarly affected. Yet RoadRunner is not disclosing
the practice in any way. Not only that, I'm troubled by the possibility of
them arbitrarily choosing to block other programs in the future. If this
becomes more widespread, they will have many angry (and former) customers." The poster provides these four links to forum postings with more information: one;
two;
three;
four.
The discussions are the result of a single post saying it's not working. Most replies to the primary posts say that everything is working fine for them. Other provide technically inaccurate information such as Kazaa "slowing down" before it just completely stops and then attribute that to port blocking. How about some general skepticism here before ranting about some mega-corp stomping all over the end users rights. Here's one of the initial posts:
"The only way i can search is if i log off and on real fast on kazaa. Doing that i can get one search off. I resume downloads fine jus no searches. I'm running XP if that helps. Can anyone please help. Thanks"
Hmmm, XP, and it works for a couple seconds and then stops. Yeah, rights, there's somebody at the RR NOC sitting there watching all traffic and manually flipping a light switch that controls your port 1214.
The second post linked to in the article is of about the same quality only by a jumpy conspiracy theorist. I couldn't stand to read the other 2.
P2P is cool in theory; but in practice people are using it merely to move around huge pirated mp3s and mpegs and as a result a small number of users are consuming a grossly disproportionate amount of bandwidth. It's a tragedy of the commons. See previous /. stories on how this has already played out at college campuses across the US (and elsewhere).
I'm in Austin, and I've actually switched away from Road Runner to SBC ADSL. Why? Because, of course, the bandwidth I saw decreased dramatically over the years since I was an early adopter; and they were charging me too damn much money, anyway. I don't get a ton of bandwidth with my ADSL connection, but the service is more reliable, and it's less expensive. And so far, I've not seen any port blocking or scanning for servers -- something I've been hearing about from the cable side of the fence.
Honestly, I'm ambivalent about a lot of these issues as my idealistic and practical sides of my personality come into conflict. Ideally, I'd like the consumer's access to the internet to be pretty much like what it meant to be hooked up to the interent in the good old days before it became commoditized -- the internet was designed for hosts to be servers, not just clients or even peers. I should be able to run my own web server, my own smtp and pop/imap server, my own nntp server, my own streaming multimedia server, share my filesystem, run distributed applications, network games, P2P apps....whatever. To me, that's part of the whole point. On the other hand, as a practical matter, there still isn't enough bandwidth available for every Tom, Dick, and Harry to use their home internet connections this way. Yeah, there's a lot of dark fiber -- but none of it is the last mile connections. And some people are consuming far more networking resources than they are paying for. That's a legitimate problem, and it certainly can't be justified on the basis of a need to share files that are illegal in the first place.
If this kind of thing becomes wide-spread, you can expect an arms race in the technology. It won't take long for the p2p guys to come up with stuff that is able to dynamically change ports as often as needed. Eventually the ISPs will either have to accept it and work with it or give up.
Meanwhile, don't forget that cable companies sell other services, like television and in some cases telephone. Right now I get all three from my cable company (ATT) but I am on the verge of going to satellite for my tv. If my provider tries something like that, it will probably be enough to push me over the edge to DSL (which is priced competitively in my area) and satellite tv, as well as the old baby bell for my telephone service - and I am not even much of a p2p user.
When information is power, privacy is freedom.
I work for an ISP in the Pacific Northwest, and we block access to all p2p file-sharing programs.
These programs {KaZaA, etc.) are blocked because the owners feel that they promote activities which are immoral and wrong. Yes, that _is_ the primary reason. If you can demonstrate to them that you have reasons for using a p2p file-sharing program which do not violate their principles, then they will remove the block for you individually.
As a beneficial side-effect, getting rid of, or limiting the 5% of our users who used these programs, saved us over 50% of our bandwidth. We are not weeping at their loss.
Neopets - the best free game on the Int
I work for an ISP in the Pacific Northwest, and we block access to all p2p file-sharing programs. These programs {KaZaA, etc.) are blocked because the owners feel that they promote activities which are immoral and wrong.
You are basically saying the medium is immoral somehow, without regard to the message. Given this logic, you can just as easily say FTP, HTTP, email, usenet, and every other port can "promote activities which are immoral and wrong". Hell, I would guess that kiddie porn is transmitted through each of the above protocols everyday, so why aren't you blocking them?
Why stop there? Most of the files transmitted through p2p can just as easily be sent through the mail on a disk. Why not ban mail?
It's pretty sad when your users have to "demonstrate" their piety to use a particular protocol. What ISP did you say you worked for again?