Drew Community

Drew Community (https://community.drew.edu//index.php)
-   Gripes (https://community.drew.edu//forumdisplay.php?f=11)
-   -   network issues (https://community.drew.edu//showthread.php?t=337)

David J. Wilson 12-05-2005 10:09 PM

The ups and downs in all of this enabled us to gain a better understanding of how the packet shaper operates & where adjustments needed to be made. These devices have to be tuned to the specific networks they're handling, and they don't always work in the most logical way. I'm glad for all the feedback.

As much as I might think so, I'd never go and say "we fixed it" without confirming it to be true. The last post I made was around the break and students weren't around, so there wasn't any way to tell for sure. Some more improvements were made last week. So many changes and fixes were made I don't think it's any single one that has made the difference.

At this point I'd say that it's much better. There is as always a limit on how much we can really do with the bandwidth we currently have, and there are times where games will be lagged or streaming media won't stream, just because there's only so much to go around. Like I said though I think we've made a lot of progress in optimizing the connection speed as a whole and especially for interactive applications. Where there's a way we'll continue working on it to provide the best experience to Drew users.

12-06-2005 10:47 AM

Quote:

Originally Posted by E. Axel Larsson
Find out who the student rep is on the Expense and Allocation Committee and ask them to support University Technology's budget request for additional internet bandwidth.


Just to update everyone on this, from the information that has been presented to the committee it seems likely that the campus will be getting a significant bandwidth increase next year, and perhaps even some extra bandwidth as soon as next semester.

12-06-2005 01:41 PM

yay bandwith! Good job, Gary. Hopefully some bandwith will come next semester, but that's great that we'll be getting a lot more next year.

Kevin P. Egan 12-06-2005 01:50 PM

Quote:

Originally Posted by Gary A. Hochman
Just to update everyone on this, from the information that has been presented to the committee it seems likely that the campus will be getting a significant bandwidth increase next year, and perhaps even some extra bandwidth as soon as next semester.

Thanks for the update

12-06-2005 02:18 PM

Quote:

Originally Posted by Zachary C. Kanfer
yay bandwith! Good job, Gary. Hopefully some bandwith will come next semester, but that's great that we'll be getting a lot more next year.


Don't thank me, thank whoever it was in the Technology department that did their homework on fiber rates.

12-06-2005 03:45 PM

yay. honestly, even if the situation stayed the way it is now i'd be happy. i haven't had a bit of trouble since all the new modifications have been put in place.

of course limewire doesn't work, but that's just due to the p2p restrictions which are rather necessary. so i don't mind.

especially since it seems likely that the p2p restrictions are partly what is keeping bandwidth usage down enough that i can have nearly lag free halo. and i'm definitely willing to trade limewire for halo anyday.

so in conclusion, go tech department! w00t!

Christopher L. Stave 12-06-2005 06:07 PM

We are pretty happy with how the network is running right now. The changes we made, including disabling peer to peer filesharing, seem to have had a very positive effect.
Peer to peer programs seem to be the major culprit in what was causing the problems that we were all seeing. We were limiting peer to peer and thought that would be sufficent, but many peer to peer applications are rather insistent and connection intensive, and will send a large amount of connection attempts. The traffic shaping tool was receiving all of these attempts, categorizing them, trying to fairly distribute all of the peer to peer connection attempts into the available peer to peer bandwidth, dropping the extra attempts (which would then typically get retried by the client program), and letting the set amount through. It was basically getting bogged down trying to accomplish this. Currently, it recognizes a peer to peer connection and drops it, which is a much easier process that, as you have noted, makes everything better. Disabling peer to peer was a difficult decision to make. We do recognize that there are legitimate uses of peer to peer filesharing and that it is a frequently employed use of the network.

While we are pleased with the improvement in network connectivity that people have experienced, we are moving forward with plans for further improvement. These plans include bandwidth increases, as Gary noted, fine-tuning the settings on our network equipment, and being responsive to the feedback from users.

Glad you like it!

Quote:

Originally Posted by Noah C. Rosenfield
of course limewire doesn't work, but that's just due to the p2p restrictions which are rather necessary. so i don't mind.

especially since it seems likely that the p2p restrictions are partly what is keeping bandwidth usage down enough that i can have nearly lag free halo. and i'm definitely willing to trade limewire for halo anyday.

so in conclusion, go tech department! w00t!



All times are GMT -4. The time now is 04:40 AM.

Powered by vBulletin® Version 3.5.7
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.

Drew University is not responsible for the content of posts made on this site. All posts and comments reflect the opinion of the author.