Slashdot Mirror


Bandwidth Demand at American Universities

Robert Rwebangira writes: "There is an article in The New York Times (free reg required), discussing college students 'insatiable demand for bandwidth.' Of particular interest is the continuing prominence of file-sharing (inspite of the demise of Napster) and the amount of bandwidth consumed in even 'legitimate' activities. It seems students demand for bandwidth just keeps growing."

48 of 392 comments (clear)

  1. Scarcity by exceed · · Score: 3, Troll

    What are the three things that will always be scarce? Money, time, and bandwidth. You can't have enough of all three.

    --

    void women (int money, time_t time);
    1. Re:Scarcity by faichai · · Score: 3, Funny

      What are you? Some kind of freak? ;-)

  2. It's a sad day by Rostoff · · Score: 5, Funny

    When the demand for bandwidth has usurped the demand for beer. What's wrong with children today?

  3. The same thing happens in the UK by -douggy · · Score: 5, Interesting
    The university network run in the UK by Janet is in constant need of extra bandwidth be it for normal use (downloading linux isos from mirror.ac.uk) or for filesharing. Janet charges the UK unis around 2p per MB which can mount up if 1000s of users in halls are pulling stuff over the atlantic but interuni stuff is free.


    Some universitys are now capping people at around adsl speeds to try and limit the charges

  4. IT's not just students by Heem · · Score: 5, Insightful

    Without specific proof, I'd be very willing to say that it's not just students. As the internet grows, and we get faster computers, and more visually intense websites, its only obvious that bandwidth demands for EVERYONE is going to grow. The size of applications and games has also risen, and even downloading legal demos and share/freeware games is bandwidth intensive, this is not even to mention 'warez' and the fact that nobody seems to be happy with porn 'pics' anymore, they want vids. So, as download sizes grow, its only obvious that bandwidth demands will also grow.

    --
    Don't Tread on Me
    1. Re:IT's not just students by baptiste · · Score: 5, Interesting

      I've got proof, at least from our university. We hit 400-500Mb/s usage on our Internet pipe. We put a bandwidth limit on the dorm network of 25Mb/s and overall usage dropped to 70-90Mb/s You do the math.

    2. Re:IT's not just students by baptiste · · Score: 4, Interesting
      This could be for a barrage of reasons

      True. However, port usage reports showed it was mostly music sharing/P2P programs. Also - the bandwidth usage was peaking during the day when students were in class...

  5. Re:And expect it for nothing by 1stflight · · Score: 3, Interesting

    Actually nothing in college is free, you really pay for everything. Spend 4 years in one and you'll be amazed at the high cost of everything. And with every year they're raising tuitions you ought to expect to get something for the thousands you're forking out each year ..and some each month.

  6. Its not the bandwidth everywhere. by LWolenczak · · Score: 3, Informative

    I attend a UNC system school, and we have NCREN powering the internet access. A little background info, everybody has one or two ds3 or oc3 lines. NCREN has an oc48, an oc12, and a handfull of oc3 lines uplinking them to the world. The problem is, that NCREN has given oc3/ds3 lines to companies like microsoft, and they load down the entire system. The traffic graphs for my university never really exceed 40mbit/sec on one line, and 12mbit/sec on the second line. We even have a third line, and its dark most of he time.

    But the NCREN oc48, oc12, and all the oc3 line outbound are allways loaded at 99%. In ncren before you hit the core routers, pings are below 30 ms, once packets leave, they have gone as high as 2000 ms. NCREN refuses to admit there is a problem, or resolve the issues. One problem also seems that one of sprints core routers that peers with NCREN is faulty or over loaded.

    I must admit, when I lived in the dorms, it was nice to sometimes be able to play the major ra3 servers at 35-55ms.

  7. one nice upshot from 'insatiability' ... by timothy · · Score: 4, Insightful

    ... is that people get used to high bandwidth as customers. Even though they may technically be customers who are supposed to be buying an 'education,' the fact is that (typical, 4-year, residential) colleges / universities seem to provide professors and classrooms only to supplement their provision of high-speed, on-site-service, always-on, relatively unrestricted network access. This is one reason I regret not living in the dorms at Univ. of Texas, which it turns out grew some good-at-the-time ethernet ports while I was in school, and I bet are still good.

    As someone who wants to be a customer for better internet access of all sorts (true all-continent roaming access for N. America at least would good ... I'd pay $300/mo for the always-on mediumband available in rural Montana etc), I want there to be an increasing supply of college grads used to insane, insanely cheap bandwidth to help drive the market :)

    timothy

    --
    jrnl: http://tinyurl.com/c2l8yr / foes: http://tinyurl.com/ckjno5
  8. Bandwith by GenomeX · · Score: 5, Interesting

    I am a student at a university in South-Africa. From campus you are only allowed internet if you have an account for which you pay, and once you have this you are only allowed HTTP. I had to use tunneling to get on IRC for instance. Another thing is our whole university probably has about the same amount of bandwith in total as about 10 computers in the US use. This is not the universities fault, but rather out countries weak communications infrastructure and the fact that we have one telco with no compitition.
    All you students and other people in the US should stop complaining, you have _loads_ of bandwith.

  9. Bandwidth Cap and Upload/Download restrictions. by akula1 · · Score: 4, Interesting

    At my big ten University bandwidth use by the residence halls has been enough of a problem to cause our keycard access system to become DOS'd. You need keycards to buy food, enter buildings etc...

    As of Monday 1.5 GB a week upload and 1.5 GB a week download restrictions go into place. You get two warnings if you exceed these limits and then your residence hall connection is yanked for a semester.

    1. Re:Bandwidth Cap and Upload/Download restrictions. by MindStalker · · Score: 4, Insightful

      Dude, thats harsh, 1.5GB a week is absolutly nothing if yoou really think abut it. Thats an average of 2KB/s constant use, which you could easily pull if you ever just play internet games freqently and surf the web. Or just download 3 iso in 1 week.

      But seriously what stupid network engineers put the keymcard syste on the same network? Talk about securuesity iss.
      Segment the 2 networks. Install a 200MB/s cap so they can't pull faster than that. And if penalties are needed, put them at 10GB a week at least.

    2. Re:Bandwidth Cap and Upload/Download restrictions. by kenthorvath · · Score: 5, Interesting

      My university has similar restrictions, I believe the quota is 1 GB /week or so and 400 MB upstream. However internal bandwidth is not counted so with a little help from Direct Connect. We were all sharing a lightning fast connection to a P2P system with approximately 5-6 TB of files! In fact, We have almost every movie, song, and video game on this server with little or no remote queueing. In fact, the university not only turns a blind eye to this type of behavior, but I've been told by some of the higher ups that it is the best thing that could have happened to the university financially. Legality is hardly an issue because only university computers can connect to the server. It's a great system.

    3. Re:Bandwidth Cap and Upload/Download restrictions. by zhensel · · Score: 4, Interesting

      We have a sensible system at my Big 10 university (UIUC). 750 MB per day limit, with rate limiting kicking in as you approach the limit - 1.5 mbps at 80% of the limit, 128kbps after hitting the limit, 32kbps if you go to, I believe, 150% of the limit. Works much better than the system they had at the beginning of the year: contacting students if they exceed the limit and shutting down their connection for two weeks in combination with disciplinary action should they repeat the offense. I'd wager that the amount of time they save with the automatic system saves enough money to afford any extra bandwidth used by students with the new system.

  10. Morpheus is the killer by baptiste · · Score: 5, Informative
    Sure, legitimate bandwidth use is high. But student use of bandwidth is huge.

    The university I work at has a huge pipe (1Gb I think) shared with two other local universities. Generally we use the least amount of the bandwidth, but at one point our usage had hit like 500Mb/s Needless to say teh other schools were freaking - they were losing packets due to teh pipe being so full. Well, our dorms are on their own network. Sure enough, thats where most of the bandwidth was going. Blocking Kazza/Morpheus and co is tough since it'll switch and seek out other ports. So the only solution was to limit the total bandwidth for the dorms to 25Mb/s Sure enough, once that block went in place our usage overall dropped to like 90Mb/s. 300-400Mb/s of bandwidth just for the dorms????

    The students were upset since their pipe was now slam full and they had trouble getting out, but the response basically was - stop running servers and stuff for music that suck up bandwidth and you'll be able to get on the Net to do the stuff you need to do. Its not perfect, but for now it works and keeps us from totally saturating our pipe.

    1. Re:Morpheus is the killer by Imperator · · Score: 4, Insightful

      The problem is not that students are sharing files. The problem is that students are sharing files outside the campus network. There's almost always extra bandwidth within the dorms. If a school were to encourage some method of sharing that first tried to download from within the campus, the vast majority of desired files would be found within the dorms, and the external bandwidth usage would diminish. Of course, such a pragmatic approach would make the stop-it-all crowd very unhappy, so it is unlikely to ever be implemented.

      --

      Gates' Law: Every 18 months, the speed of software halves.
    2. Re:Morpheus is the killer by PhoenxHwk · · Score: 3, Interesting

      Blocking Kazza/Morpheus and co is tough since it'll switch and seek out other ports

      No it doesn't! Just block destination port 1214 and they can log in and search, but can't download squat because everyone else's Morpheus copy is listening on 1214. I did it to my bandwidth-hog roommate and we're lag-free all the time now.

    3. Re:Morpheus is the killer by cmkrnl · · Score: 3, Interesting

      Yes idiot, it would also make the owners of the campus infrastructure responsible and therefore liable for copyrighted material exchanged through such a facility.

      Plausible deniability is an defence when its a bytestream crossing a network. Impossible when its on college owned and managed P2P server.

      Never mind the ethical/politcal considerations of some of the material transferred.

      Curmudgeon

  11. the soln by gargle · · Score: 3, Insightful

    The problem is unlimited, flat rate access. The solution is a market based approach where people are charged according to how much bandwidth they use, and not draconian anti-market restrictions on utilization.

    Want to use more bandwidth? Sure, as long as you're willing to pay for it.

  12. Re:Cut 'em off by RC514 · · Score: 4, Insightful

    There's no way to stop filesharing except at the endpoints of communication. Unless the users stop wanting to use filesharing, there will always be workarounds for all the filtering and blocking you can think of. The next step is encrypted connections below tcp level, aka ad hoc virtual private networks. Since there's a heap of good reasons why one would want all traffic (even the "non-shady") encrypted anyway, universities will most likely refrain from blocking the necessary protocols. Once the traffic becomes opaque to the transport, there goes the ability to filter based on contents or protocols.

    What can be done is this: Restrict bandwith or volume of data. That however will limit certain promising aspects of network development like freenet and other decentralized protocols. That's why especially universities which are supposed to be interested in innovation should think twice before crippling network access.

    --

  13. 90% of the people = 10% of the bandwidth use by reddawnman · · Score: 5, Informative

    I work in the Academic Computing Services department of one of the UC Schools...

    The majority of our problems come from about 10% of the population on campus who are online 24/7 downloading their pr0n, thus giving most of the other students probably polled in this study a reason to start asking for more bandwidth. I should also add that these are the same 10% who are hogging internal bandwidth playing counterstrike, etc.

    I think that the term "Insatiable Demand" is definitely a misnomer. Although the "Prominence of file sharing" does apply to quite a few people in our dorms, 90% of the people are utilizing the network for, at most 10-20 megs a day. In fact, we have a 2Mbit cap on the routers coming out of the dorms, and most users find that they can surf the web and get their 3 or 4 files a day with no problems, and are pleased that, at 4AM, they can get an insanely high throughput. The reason that the students complain about the network being slow is because of the caps (which most don't know about) at peak times, because, again, the 10% that actually do have an unquenchable thirst for data would take full advantage of the situation.

    I should add also that we block Morpheus, thereby removing those oh-so-lovely TCP standards hacks it implements, so YMMV

    1. Re:90% of the people = 10% of the bandwidth use by AnotherBlackHat · · Score: 5, Informative

      Yeah, I know what you mean. I used to help with the administration of the pianos in my college, and it was much worse. Seems like the music majors consumed way over 90% of the time available, even though the other students barely touched them. More than once I was on the receiving end of complaints that there weren't enough pianos. And I heard that the swimming pool was in a worse situation, with the swim team hogging nearly 95% of that valuable resource.

      The worst part was the huge number of administrators who seemed to think that the situation was completely acceptable. I would constantly hear phrases like "The equable distribution of resources does not mean everyone must use exactly equal portions.".

      Each of us is an individual. And the name of that individual is Clancy Jones. - Clancy Jones #148.

  14. My experience by UnrefinedLayman · · Score: 5, Interesting

    At an unnamed university in California for whom I work, we have available at any given time ~ 40 Mb/s, with around 800 students living on campus. Normally our network situation isn't bad, but this last fall semester it got completely out of hand.

    Of the 40 Mb/s, on average one-half of it would be in use directly by students in the dorms. At times, individual ports would be using 7-8 Mb/s, for as long as ten hours at a time. Eventually, it was decided that the impact on the university's bandwidth was affecting the educational functions of the campus network and all users were reminded by mail of the campus AUP for the network.

    Students, being students, ignored it largely. The offenders who chose to ignore it and flaunt the fact they were ignoring it (anything above 2 Mb/s for over a few hours) were warned by mail individually, and after that, had their ports shut off and the MAC address of their computers banned from the DHCP pool, so no matter where they went (i.e., plugging it into their roommate's port), they were locked out. To receive service again, they needed to contact the student judicial affairs, which involved only signing an agreement not to be naughty again, with the threat of being kicked out of the dorms.

    Long story short, a few people got their ports shut off and had to go through all the rigamarole. Most of they had no idea what they did was wrong, and didn't understand that leaving Kazaa, Morpheus and all their other file trading utilities on all day long was not only illegal, but the reason they received the notices in the first place.

    It boggles my mind to think that these kids got into a university and don't understand that downloading the new N'sync album before it's on store shelves is illegal. Theft is theft, no matter who you're screwing over, but luckily, most will figure it out pretty quickly when the university tells them they were disconnected because Sony contacted the university about their particular computer, and yes, both the university and Sony would be more than happy to have them kicked off campus rather than deal legally with a pirate.

    1. Re:My experience by ajs · · Score: 5, Insightful

      didn't understand that leaving Kazaa, Morpheus and all their other file trading utilities on all day long was not only illegal,

      Hello! Why would leaving Kazaa running all day be illegal?!

      I think you're making some interesting conclusions about legal precidents which have yet to be set. Now, I could buy that explicitly downloading something which is copyrighted is a violation of copyright (assuming that no other provision, e.g. licensing, has been made), but you're way out on a limb otherwise.

  15. Proof by AmigaAvenger · · Score: 5, Insightful

    Here are just a few router stat graphics from my university. As you can see, Kazaa/Morpheus is 85% of the outbound traffic!! Inbound isn't quite as bad, only 63% or so.

  16. Is it really so unreasonable? by schnurble · · Score: 4, Insightful

    OK, first off, I'm very serious. And I'm ignoring such things as Morpheus, Gnutella, etc. Those should be blocked.

    But honestly, is it so unreasonable for bandwidth demand to go up? The medium is getting richer. Websites are taking advantage of media like Flash, movies, and sound more and more. More information abounds. People want stuff in more than just plain marked-up text. Maybe the increase is disproportional, but there are people (like my parents) that still believe that a 28.8kbps modem is sufficient. Not true.

    Yes, as new services (including gnutella and napster) come about, there is a natural demand for more access. Deal with it.

    More, quicker, better. It's the way things will go.

    --
    "To err is human, to forgive is simply not my policy." --root
    1. Re:Is it really so unreasonable? by ajs · · Score: 4, Insightful

      Morpheus, Gnutella, etc. Those should be blocked.

      This is the classic application of authority to solve a technical problem. Look how well that works for the Chinese ;-)

      Now, if a University *really* wanted to solve the problem, they would devote some research dollars to p2p networking.

      For starters, yes the majority of p2p communications these days is porn and music. You will also find humor, news footage, open source software, movie trailers released (quietly and so as not to endorse the media) by the studios, text documents authored by fanatics, fools, story-tellers and tech writers.

      If Universities have a problem with high bandwidth utilization, they should 1) work on the protocols to make them more sensitive to network topology so that they prefer cheaper resources (ala UUCP) 2) impose per-port bandwidth monitoring and charge students per-Gb after some nominal "you can do your homework and send mail to the folks" cap 3) educate students on how the services they use affect bandwidth.

      This idea that Gnutella should be banned because we don't like what it *can* (and often is) used for is counter to what Universities profess to offer to their students. If I wantsed to get a lesson in authoritarian control, I'd work for the IRS.

  17. Some Universities are on top of the problem by flsquirrel · · Score: 5, Interesting

    I attend a small state school of about 7000 undergrads(well, maybe not super small) and across the past year we have experienced precisely this problem. We have ethernet jacks in all the dorm rooms and everybody was running all the usual file sharing apps and it got to the point that you could not surf the web. The browser would time out because it went to long between packets! So the beginning of this year, A QoS package(I beleive we're running packeteer) was set up on our firewall to hunt down and block the packets for these programs as well as streamline some other network traffic and things have really cleared up. It's not blazing fast but surfing happens at a reliable 20k/second which is pretty snappy for browsing. Linux ISO's still take a while though ;-)

    Things to think about in the current suggested solutions:

    1. Limiting bandwidth to dorms just hurts students who don't run these programs! Yes there are some of us out here. The majority of students even in a small school can not be organized to stop running this type of software. They just bitch about the slow connection and keep right on downloading mp3's. At least that's what happened when our college tried it.

    2. Blocking ports isn't effective. One of the earlier posts mentioned about how Morpheous and others seek out new ports. This makes normal port blocking on a router or firewall useless and may arbitrarily block other software that is not a problem but happens to use the same port. You have to have software smart enough to look at packet type/content to be effective.

    3. QoS software works if you get the right package. I work for the computer center at my college and I know we went through a number of packages before we settled on one. But it really makes a difference and it's suprising how many people don't even know this sort of software exists.

    1. Re:Some Universities are on top of the problem by AaronStJ · · Score: 3, Insightful

      The majority of students even in a small school can not be organized to stop running this type [morhpeus, et al] of software. They just bitch about the slow connection and keep right on downloading mp3's.

      There are a reason most college kicks complain about bandwidth while running the same bandwidth sucking program: that's what they want to do. Surfing the web at top speed is nice, but most college students really just want to download music. So it doesn't really make sense for them to stop doing it in order to free up the bandwidth. Telling college kids to stop downloading music in order to free up bandwidth is like telling a computer gamer to stop playing games in orer to free up CPU cycles. What good are the freee resources if you're not using them for what you want to do?

      In the end, college kids mostly just want to download music. I know, because I am one. So no matter how well intentioned, any kind of packet filtering scheme is just making the college kids madder.

      --
      Stupid like a fox!
  18. Why do gamers have to get scrood? by coding_ape · · Score: 3, Interesting
    They instituted a packet shaping policy at my school (Harvard) last semester to kill file sharing apps. It apparently does a lot of packet dropping on ports above 1000. Unfortunately for me, it destroyed my beloved Counter-Strike (300+ pings, 30-40% packet loss etc), along with every single multiplayer game I have tried. Now no one can convince me that CS is a bandwidth hog - the netgraph shows an average usage of a little over 1kb/s. It was designed to be played over a 56k.

    Problem is, no one at school wants to hear about the problem; they just accept the collateral damage.

    Does anyone know why/if this must be the case? i don't really understand why the software (perhaps Packetshaper as mentioned above) ruins the ping times - shouldn't it just drop enough packets so a TCP connection stays at a slow transfer rate?

    Also, shooters generally use UDP to send the state information. I imagine file transfer programs use TCP. Not knowing much about the software, would it be possible to shape TCP connections and not UDP? (this would require reading the header)

    1. Re:Why do gamers have to get scrood? by Corgha · · Score: 5, Funny
      Problem is, no one at school wants to hear about the problem; they just accept the collateral damage.

      I suppose you don't remember the day this fall when packet shaping was turned off and absolutely nothing worked. The "poor performance" mentioned in that announcement is quite an understatement -- traceroute probes came back in times on the order of seconds or not at all. I also remember the days just before the traffic shaping was put in place and I was getting over 5-second ping times. People like games, but when email and the web stop working, people quickly start thinking about realistic priorities.

      You also might ask yourself: did your games work when no traffic shaping was in place and ping times were measured in seconds and packet loss was rampant? I doubt it. How, then, can you blame the shaping for your problems if your problems didn't go away when the shaping did?

      Does anyone know why/if this must be the case? i don't really understand why the software (perhaps Packetshaper as mentioned above) ruins the ping times

      First of all, because of retransmits, dropping packets can lead to high "ping" times, depending on the protocol/application and what it considers a "ping." Second, the software may be trying to "smooth" out the traffic to fit under some limit -- queueing packets from burst periods to be transmitted in lower-traffic periods.

      shouldn't it just drop enough packets so a TCP connection stays at a slow transfer rate?

      That's a nice idea in theory, but the problem in practice is this: tracking all those individual TCP flows would require immense amounts of computation by the router. AFAIK, we're talking orders of maginitude greater than what is currently available. From what I hear, the really expensive Cisco router at the border is already extremely busy doing just the simple packet shaping, which just limits the aggregate high-port traffic. Breaking that one giant flow into millions of little flows is non-trivial and probably impossible.

      Now I'm no networking expert, but it seems to me that doing traffic limitation on a per-user or per-flow basis would probably require some sort of distributed model that did the limiting closer to the user. This might mean not only replacing all the switches with more expensive models, but also hiring new staff (non-trivial) to install and integrate the new hardware into the existing network and to maintain the configuration on all those switches or to write some fancy new automated system to do the maintenance. Of course, all that is just another idea, and there may be some other pratical considerations that make it even less feasible. It also sounds like a lot of work, and considering why you would be asking them to do it, I can imagine that it would end up a lower-priority item than other things that the FAS network people have to do.

      Not knowing much about the software, would it be possible to shape TCP connections and not UDP? (this would require reading the header)

      I don't know either, but the file-sharing folks have shown themselves to be pretty adaptable. If they would play nice and limit themselves to certain ports and protocols, then everything would be easy. And, of course, who knows whether this would just require too much CPU time, as well.


      Anyway, some background/historical info:
      The undergraduate dorms get their connections through the FAS (Faculty of Arts and Sciences) network, which in turn gets its connection through UIS (University Information Services), which provides networking for all of Harvard. Back in the good old days of 2000, before the file-sharing people went crazy, UIS had just upgraded its internet connection (to a 155MB/s OC-3, IIRC) -- oh what heady and naieve days those were. Now, however, the situation is this: file-sharing programs seem to act as a gas that consumes all available bandwidth. That first started happening, IIRC, the weekend when Napster was going to be shut down. Suddenly, the undergraduates doing file-sharing shut down the connection for the entire university (which is much larger than the undergrads).

      This is a classic "tragedy of the commons" scenario. The file-sharing folks abused a shared resource and ruined it for everyone else. What the traffic shaping essentially does, since it limits the student network to some portion of the FAS-UIS feed, is allow the file-sharing programs to ruin only the undergraduate dorm commons. Now, it's easy to blame the shaping for the bad performance, but the real truth of the matter is that if the file-sharing programs weren't trying to consume essentially infinite traffic, your games wouldn't have a problem. The router doesn't slow things down just to mess with you. Gamers are getting "scrood" by the other undergraduates doing file sharing, not the traffic shaping. Incidentally, the shaping is similar to the sometimes-raised suggestion of giving the students their own internet connection and fighting it out amongst themselves, except that traffic shaping makes it easier for people to complain about "the Man" and that a separate feed would be stepping on UIS's toes a bit. Also, a student-only connection would have to be much bigger than an OC-3, because it has already been demonstrated that an OC-3 can't handle the file-sharing traffic.

      What most people want is for the file-sharing people to be moved out of their commons and into someone else's. That's what you're suggesting when you want TCP but not UDP to be limited. As an off-campus user, the file-sharing people are already out of my commons, so I'm happy that I can access Harvard websites and mail and login servers again. Most of the users of Harvard's network aren't on-campus undergraduates, either. Perhaps you can understand, then, why I'm defending the shaping. I like the network to be actually usable instead of the packet-dropping mess that it is when shaping isn't there.

      There's also the option of getting rid of the commons, which is the shaping-per-user suggestion, but that has some disadvantages, too. Even if the undergrad dorms get one third of that university-wide OC-3, that's only 7.5kb/s per undergrad, which is not too great. Up the per-user bandwidth to something reasonable and now a certain number of file-sharing people can take everything over again.

      Then there's the get-a-bigger-commons option. There are several problems with this. First, it's not clear that there exists a pipe fat enough for the number of file-sharing users among the undergraduates plus the other uses from the university at large. Second, of course, is what someone else has already mentioned -- try to imagine the FAS network admins justifying to UIS the need for the university to get a bigger feed, and UIS in turn having to justify that budget item, just for undergraduate file-sharing.

      Everything I have said is based on what limited stuff I have seen and heard, but it seems to me that it's all really complicated, and if there were an easy solution, I'm sure it would already have been adopted.

  19. 640K Should Be Enough For Everybody by Enonu · · Score: 5, Funny
    As history has shown, people will use a resource to its full limits until there is none left, and then complain for more. As a college student myself, I can't wait for the day until I can host 640x480 HQ MPEG2 videos at let's say 80 megabytes a pop, downloaded at lets say 10 times a minute. I can't wait for the day where a Linux ISO download is burned straight from the net onto my DVD-R @ 10X. On top of that bandwidth, I want it all wireless, 1 ms per hop for latetency, and at most 5 hops to anywhere in the world.

    Of course by then I'll be demanding real-time, life-size holographic video of a "phone-call" to a friend in Asia @ 3 million DPI.

    Then finally, matter transport. I wonder how many bytes it'd take to decribe each atom and all its subatomic particles. How many atoms to a human body? Let's do it Star Trek style, and do it in about 5 seconds.

    Fast forward a million years, and let's say we haven't blown each other up yet. We'd probably be at the equivalent of God by then.

    "Hey Jeff, fancy creating a solar system today?"
    "Why not Bob?"
    "Well fancy that. OK." *click* "What do you think of that for a Sun?"
    "Pretty impressive. Hey let's transport Dave's planet from quadrant four over here. That bastard is always gloating. It'll take him a few seconds to find it."
    "OK." *click* "Hey it sort of looks nice doesn't it?"

  20. Re:Cut 'em off by invenustus · · Score: 3, Interesting
    Unless the users stop wanting to use filesharing, there will always be workarounds for all the filtering and blocking you can think of.
    Wrong. At my university, they put in place an internal IP system such that dorm computers can ONLY be accessed from other computers inside the university. I can go on Morpheus and download, but anyone who tries to get files from me (and is outside the university) is going to get a failed download.

    The system was not put in place to hurt filesharers, in fact, because we had that under control - if you exceeded 2 gigs a week downstream or 500 MB a week upstream you got shut off for 1 week - but because too many dorm computers were getting h4x0red and used for DDOS attacks, and the university was getting blamed. (Just be glad they did this BEFORE WinXP came out.)

    There's a happy ending, though. Somebody set up a Neomodus DirectConnect hub on a dorm computer, and it spread like wildfire. The university only really pays for bandwidth that leaves the university, right? So now we share files to our heart's content, there's no upload or download restrictions, and the downloads are fast as all hell because they're all within the same organization.

    --
    grep -ri 'should work' /usr/src/linux | wc -l
  21. Re:Firewalls by greyguppy · · Score: 3, Interesting

    I am currently at durham university.
    The IT Service, only have a few college rooms cabled up. I had one last term, but not this term. What you get is 10Mb/s but ALL web is forced through a proxy server. This is not transparant, but rather blocking outgoing ports. MSN works if you put in the address of the proxy server, and audiogalaxy will figure out the proxy settings. You can ssh out, and in from/to anywhere, and with port forwarding, this is very useful. The ITS NT machines in the computer rooms, are even worse. You get a VNC server running all the time as a service. I am expecting a visit from the director of ITS dressed in a black suit brandishing a gun.
    Noooo. Dont sho..........

  22. A side effect... by Shoten · · Score: 5, Interesting

    I did a security assessment at a large university late last year, and found something astonishing. The number one expenditure of time for the computer security staff was dealing with cases of "copyright infringement" from the representatives of record companies. And I mean, it was something like 80% of the manpower. What was also infuriating was that a lot of these cases involved MP3s that had been posted by the band to their own website (that week that I was onsite, most of the warnings given to the university had to do with a song by Incubus, if I remember correctly, that had been downloaded from the official Incubus website.)

    --

    For your security, this post has been encrypted with ROT-13, twice.
  23. No one seems to have mentioned this yet by Wyzard · · Score: 5, Interesting

    At my school (Lehigh University), we address bandwidth problems this way...

    Each student (each MAC address, really) is allowed to transfer one gigabyte within a 12-hour period. If you go over the limit, you get put in a "penalty box" (basically sub-58k speeds) for a while until your transfer total for the past 12 hours is under a gig. Uploads and downloads are counted separately, and transfers that don't go off-campus don't count at all. One of the university's servers holds a list of what addresses are in the penalty box, and what their transfer totals are.

    This is quite effective - it gives each student a reasonable amount of bandwidth, and it only punishes those who actually use too much of it. And our 45mbit internet connection is rarely maxed out.

  24. Re:Cut 'em off - no, just make it fair by stripes · · Score: 3, Insightful
    There's no way to stop filesharing except at the endpoints of communication. Unless the users stop wanting to use filesharing, there will always be workarounds for all the filtering and blocking you can think of.

    The point isn't to stop it, but to treat it like a second class citizen. So if there is no shortage of bandwidth you can do all the filesharing you want, if the "legit" traffic uses 75% of the available bandwidth then there is 25% left for filesharing. The only blocking would happen if the "ligit" traffic manages to use all the bandwidth.

    From a technology point this is a pretty easy thing to do, the first paper I read about it was in, um, '94 I think, and was oddly enough about a UK to USA pipe that was jointly owned by a research university and a business, they carved it up to 1/3rd of the traffic to the business, 1/3rd for faculty, and 1/3rd for other uni uses (students mostly). Any of the 1/3rd were unused the other two could split the slack.

    This scheme is much better then outright blocking for a lot of reasons. First is fairness, it is fair to let the filesharing go on when there is spare bandwidth. Second is practical use, if you block a port people will quickly use another port, if a port is "just slow" it will take way longer for anyone to realize they should try to work around it. In fact as long as the reasoning is explained many people won't even try to work around it.

    What can be done is this: Restrict bandwidth or volume of data. That however will limit certain promising aspects of network development like freenet and other decentralized protocols

    Depends on the limit. In this case "whatever is left over" seems pretty reasonable. It would work out to far more "network time" then most astronomers get "telescope time", right?

  25. Re:In my college days ... by dattaway · · Score: 4, Funny

    Oh,dear boy, you had it easy, why back in my day we used beads carved from rock with holes chipped inside so they could be fashioned on spun strings. We had slaves to slide the beads according to set rules. In fact, it was a dangerous job due to the overwhelming number of beads required for basic computational analysis. To calculate prime numbers, MMMCX tons of beads were required and a failure of the supporting members meant an avalanche of rolling beads upon the camp. Begin worker's rights and other heretic movements that impeded technology.

    But I digress. You young whippersnappers think you have it so good with silicon, you ought to try pushing carts of beads uphill by the bucket uphill both ways with no round wheels.

  26. The Original USC by JamesKPolk · · Score: 3, Funny

    What next, UCLA is rally the University of Central Louisiana? MIT is the Michigan Institute of Technology? CMU is Collge of Medicine of Utah? :-)

  27. Need more local file sharing priority. by Restil · · Score: 5, Insightful

    I've said this before, but its a good point. Even though its been pointed out to me that some of the file sharing software supports this, people don't primiarly share locally. They abuse the upstream connection for all of their sharing, when chances are good on a large university campus, there will be numerous others sharing similiar things, and the local bandwidth is cheap and plentiful.

    The clients used for this purpose need to prioritize on local networks. Even if there is a limit on the number and speed of the connections, give immediate unrestricted access to anyone thats on the local net. This will encourage people to look first from within and only search the rest of the internet if it can't be found locally. If other large universities did the same thing, then the incoming requests would also be significantly minimized.

    Remember, if the upstream connection is used or a local one is used, the local bandwidth is spent anyways. Might as well quit wasting one of them.

    -Restil

    --
    Play with my webcams and lights here
  28. it's the students view of computers by htmlboy · · Score: 3, Insightful

    as i see it, the problem lies in students' view of computers as music storage devices rather than tools to do classwork. napster/audiogalaxy/kazaa/whatever is now seen as the primary use for a computer in a dorm room, and the students with those computers, being the unwashed masses of the internet, will often leave the default settings on, sharing all the files they download. large numbers of people doing that will slow down any internet connection.

    but that's not it. because this is how the students see their computers to be used, they expect that the campus resources for internet access should be adjusted for their obviously non-academic activity. this sense of entitlement is at the root of the problem. without all the people who only know their pc as a souped-up jukebox, there would be plenty of bandwidth for legitimate use.

    that may sound pretty out there -- i'm just speaking as someone who's seen the cycle of network saturation leading to a blocked ip or rate limited port too many times.

  29. Acceptable Usage by shut_up_man · · Score: 3, Insightful

    I don't like Acceptable Usage Policies. I see them and think "these guys haven't built their network properly". I want their network to let me do whatever the hell i want, and restrict me automatically through technical means, not allow me to overload everything, THEN tell me I've been bad.

    I'd like to see bandwidth restriction based on current overall usage too, rather than times of the day, ports, or locations around campus. If no-one is using the 10Mbit link, I should be able to use it! When things get busy, my pr0n downloads should be throttled back.

  30. A little UK university history by Anonymous+Brave+Guy · · Score: 4, Interesting
    I am at cambridge, each department/college has to pay for its bandwidth costs.

    Yep, that kicked in around the very late 90s (until which point JANet had been charging flat rate, or the University Computing Service had been absorbing the variation, but either way the individual colleges and departments didn't take the hit).

    Perhaps slightly surprisingly, it wasn't the zillions of us playing Quake II over the 'net that did it. We were generally responsible enough to avoid doing so at peak times and keep it to the evenings and weekends, and many college computer officers had an informal policy of allowing such use as long as it was fair and didn't disrupt legitimate academic things.

    Also perhaps surprisingly, this all predates things like Napster. Mass music interchange wasn't going on then on the scale it was until a few months ago.

    What did it was the Warez servers blatantly running on university networks. They knew where they were, of course, and for legal reasons closed them down every now and then. But a certain type of hax0r dudez just kept abusing the system. So, now small groups or individuals get charged, caps are in place, traffic is presumably monitored, yada yada.

    Sadly, and as all-too-usual, the irresponsible and downright illegal behaviour of a few has now impacted the facilities available to the rest.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  31. The billing costs eat you alive by Animats · · Score: 3, Informative
    Telephony billing costs more for off-peak periods than the transmission costs. Billing, marketing, collection, and support for an ISP cost much more than the back-side bandwidth. It's not economic to meter. And it kills you competitively.

    You need some throttling to hold back the few percent of the user population who will suck up all available bandwidth, but the practical cap is maybe 10x the median.

    As a technical matter, I hate packet drop as a throtting measure. Packet reordering is much more effective at throttling TCP, especially for long TCP connections.

    [I used to do network congestion research. I invented "fair queueing", discovered "congestion collapse", and was the first to describe the "tragedy of the commons" problem for networks. I introduced all three of those phrases to networking. See the RFCs that bear my name. So I do know something about this, although I got out of networking and into graphics years ago. J. Nagle]

  32. Re:Cut 'em off - no, just make it fair by stripes · · Score: 3, Insightful
    The first step is slowing or blocking known filesharing ports and protocols. Users will find a way around this (they'll download the next generation of filesharing tools). So then inbound connections will be blocked. That removes all peer to peer capability, at least for connection based protocols.

    I believe that some places are doing blocking, and I think the blocking is a bad idea for very much the reasons you state.

    My proposal is different from blocking the ports. I merely want to give preference to other traffic. Assume for the moment that a university has a T3 (I know, that's not much bandwidth anymore, but I happen to know the numbers for that). So there is about 45Mbits/sec of bandwidth. Now assume that you and one other guy are using the net, he is streaming some data from a telescope and has a demand of 22Mbits/sec. You are grabbing a NetBSD ISO from a P2P network and also want 22Mbits/sec. Without traffic shaping you would both get right about 22Mbit/sec for a total of 44Mbit/sec. With my proposed traffic shaping you also both get 22Mbit/sec since there is 45Mbit/sec available. Now lets say I show up and want to use 22Mbits/sec to download CivIII. In the ideal world I'll get 1Mbit/sec and the two of you will both stay at 22Mbit/sec (unless I am really going to use CivIII in some educational manner). As I proposed it you and I get 11.5Mbit/sec and the telescope guy sticks at 22Mbits/sec.

    Not blocked, but there is an implicit assumption that the file sharing traffic is less important the the other traffic, one that isn't totally fair, but it probably as good as it gets.

    When the point is reached that filesharing is "impossible", the network will be web only. The bad thing about that is the message: The internet is the web, the web is what bigger entities serve and you consume. (All peer to peer had to be removed to stop filesharing, but that's known only to historians.)

    That clearly isn't my intent, just to make sure the other traffic gets first crack at the bandwidth.

    Is there a better way? I think so. Don't cripple the network technologically, but involve students in the economics of the net.

    Hmmm, now who has:

    put students into a consumer role which I think is the direct opposite of educating them.

    I know, cheap blow.

    At that price, most students would be happy to pay for the used bandwidth, if that meant no more "you can't do this, you can't do that". Offer 1 or 2 GB per week free, charge for anything exceeding that and offer some means by which the user can monitor and limit his/her bandwidth usage and everyone but the most hardcode filesharers will be happy.

    That doesn't seem too bad either. I have nothing against that solution. In fact it can co-exist with the traffic shaping. You can give some amount of shaped bandwidth for "free" with normal dorm fees, and allow people to buy more non-shaped bandwidth at market rates (which may include fees above what you quoted for equipment and other things).

    I don't know how many people would be happy with it and how many would not view it as an escape from being hemmed in, but another excuse to nickel and dime them to death, but that's what pilot studies are for :-)

  33. This will drive bandwidth in 10 years by Hangtime · · Score: 3, Insightful

    Like many here on Slashdot, I came from college away with a need for high speed bandwidth. Not only am I not alone, the ranks are growing. Each year, students with a need for speed leave looking for residences that offer these conveniences. Where a small number of individuals in their mid-30's consider bandwidth a necessity many of us in our early to mid 20's consider it a requirement of our living spaces. In my own case, high speed access was a requirement when looking for an apartment, (wireless 100KB both up and down, nice). Complexes outside of college towns are beginning to take notice as they begin to string CAT 5 through their buildings. In addition, many home builders are getting into the act with prewiring the homes with CAT 5 where traditionally they would drop CAT 2 and 3 for phones. While the bandwidth market won't take off tomorrow like so many had hoped "AT&T wireless, CLECs, etc." Give it 10 years when individuals like myself are ready to buy homes, THEN we will see the broadband revolution we were promised over the past few years.

    HT

  34. Round by Graymalkin · · Score: 3, Insightful

    A good portion of the posts by students are their tales of woe about not being able to share gigs of porn and MP3s. Big fucking deal. The fees for your semester's worth of internet access isn't higher than what I pay in the same period for a cable modem. Stop being whiny bitches. I think legitimate uses also fall short of downloading a new Linux ISO every day. No matter what you think you need, you don't REALLY need a new Linux ISO every day. There's also a good chance your school's got a mirror on their internal network somewhere of all the ISOs you could want. If you need an update use apt-get or some other installer program with FTP support for fetching new RPMs. You might talk to some network admins to see if they would provide a mirror for said FTP so you wouldn't have to go outside the network to keep your system up to date. Browsing the web and playing counter strike or Quake all day long is easily legitimate because it isn't going to put you over any quotas. As for admins, put mirrors of stuff like Linux ISOs and FTPs on boxes in the internal network and advertise them to students so they know they don't have to tax your internet connection to get them. Also set up HTTP caching proxies at the head end the dorms or library or whatever hooks up to. It will offload stress on your outgoing connection to the net by a good deal.

    --
    I'm a loner Dottie, a Rebel.