Bill Blum wrote:
Hi-
I'm working in the IT department of a small liberal arts university-- we're
getting *massacred* by P2P traffic.
Informal testing/probing indicates that about 60% of our traffic from the
dorms was P2P-- we've taken the initial step of hardlimiting the dorms
to no
more than 40% of outgoing university bandwidth. Also, we've blocked the
'standard' ports for KaZaa, Gnutella, etc. in our firewall/switch setup
(Cisco Catalyst 6500 between us and the net at large)....
Would be more liberal to try and allocate bandwidth per user - Do they
have real IPs?
However, the Powers That Be want a better, more effective solution---
without a performance hit for the VOIP phones on campus.
Any suggestions on what part of the FM I should be reading/etc, so that I
can make a better informed decision about how to proceed?
Well I like to think Linux Qos could do it, but can't point you any
manual as such. Classifying traffic can be hard and will need ongoing
maintenance, but it's doable. I have no experience with the size of
network you have - I guess the cisco can't do anything more for you.
What to do and what you can do also depends on how much bandwidth you
have and how many users - you wan't prio for voip, do you know how many
voip calls your link can sustain without any other traffic.
Andy.
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
