From: Mohan Sundaram <smohan@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Suggestions/Pointers on where to begin my search for
Date: Thu, 24 Aug 2006 14:21:00 +0000 [thread overview]
Message-ID: <44EDB2FC.7080201@vsnl.com> (raw)
In-Reply-To: <6aa4d09a0608240632q47de4e83k89f6de0eb078bdd4@mail.gmail.com>
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)....
>
> 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?
>
> Regards,
> Bill Blum
>
> --
> Bill Blum
> Bill.Blum@gmail.com <mailto:Bill.Blum@gmail.com>
>
Try a Linuc m/c in between with ipp2p patch on iptables. Have you tried
using the NBAR facility on the CISCO. That should also help.
Mohan Sundaram
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-08-24 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 13:32 [LARTC] Suggestions/Pointers on where to begin my search for a Bill Blum
2006-08-24 14:21 ` Mohan Sundaram [this message]
2006-09-18 13:38 ` [LARTC] Suggestions/Pointers on where to begin my search for Andy Furniss
2006-09-18 15:34 ` [LARTC] Suggestions/Pointers on where to begin my search for a David Sims
2006-09-19 2:21 ` [LARTC] Suggestions/Pointers on where to begin my search for Mohan Sundaram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44EDB2FC.7080201@vsnl.com \
--to=smohan@gmail.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox