@chaser324: @brich:
(Sorry this got winded I was proud of the network we built, but TL;DR; We had issues like this and we fixed them, we serviced the students, it's our job. There are proper ways to run huge networks. I called my old co-worker last night, 173 students were playing a game with traffic like Destiny, zero call tickets)
It's not about opening ports, it's about running a network with 1000's of people with different needs properly. When COD: MW2 was released we had and issue where only 16 students could play multiplayer at once. At that time 40% of students had 360's in the dorms. (We allowed 3 devices per student in the dorm) after 4th week, they could request a 4th item). I know because at that time we had to manually add 360's because they didn't have a web browser to register the device with...
I still have nightmares about move in day....
Universities should never block internet traffic. We only did if it was on our known exploit page. which was mostly Russia and India IP's. We directed them to a page explaining why it was blocked and a petition page. As much as our administration wanted to restrict internet, Our faculty pushed that research is impossible with limitations. So, everything was accessible and possible.
What if you had a CS student that wants to set up a Linux server to solve a project, what good is it if no one can reach it due to network limitations?
What if a professor points to a torrent link for a Virtual PC image needed for a project?
Some P2P is valid and legit, so how can you discriminate it by blocking it across the board?
When the CoD issue hit us, we had meetings and then fixed it. A couple rule changes on the packet shapers and changing the way we assigned public IP's to students. (By assigning public IP's to a student in stead of NAT'ing students behind a couple, solves the torrent issue. If an IP is reported, it's passed directly to the student in question) The packet shapers examine ALL traffic going in and out of the dorms and classifies it, then throttles it as necessary. Dorm traffic was usually split up by P2P, Youtube(Flash), Music streaming, school services, and general http traffic.
Youtube was throttled to about 30% of traffic during the day and 60% at night. Otherwise it would eat 100% of the traffic. As for p2p which xbox 360 traffic and countless PC games would get flagged as, was our biggest rule set. Every Thursday, we checked the P2P traffic for unknown traffic, figure out what it was and assign it's throttling rate. Examples Limewire 3Kbps per instance, torrent traffic was 15% of available bandwidth. (As of now, netflix is the biggest offender of traffic there at 11pm it's using 175 MBps which is it's throttle limit. Once a packet type reaches it's limit then that limit is split by number of users.
Borderlands for the ps3 needed custom rule sets too. That one was a bitch...
I don't know, but we worked hard solving these issues and making an open adaptable network for students to use at their freewill. We also had many students lobby us with student council for stuff. We would be present and listen. All reasonable request should researched, students are paying your salary. Another great thing about our packet shapers was when a student complained about slow internet, we attached a detailed report of EVERYTHING they where doing for the past 30 days. Including list or URL's visited at 1:30 AM.
That's why I blame the university, we did it, so can they.
Log in to comment