limiting the no of sessions on an ip or subnet will most likely work well
too, unless it limits other traffic types due to the session limit. Anyway i
have no idea how to do that on IOS
> -----Original Message-----
> From: Hassan, Shehzad [mailto:shehzad.hassan@bell.ca]
> Sent: 04 May 2002 19:07
> To: 'Mark Pace Balzan'; francisv@dagupan.com; cisco-nsp@puck.nether.net
> Subject: RE: [nsp] Limiting bandwidth of P2P traffic
>
>
> CAR(rate-limiting) is good i.e. if your HW/SW supports it AND no
> performance/service impacts(most important).
> Isnt there a way we can limit the # of TCP sessions for this P2P traffic
> (pre-defined layer-4 ports)
> SH
>
>
> -----Original Message-----
> From: Mark Pace Balzan [mailto:mpb@melitacable.com]
> Sent: Saturday, May 04, 2002 11:56 AM
> To: francisv@dagupan.com; cisco-nsp@puck.nether.net
> Subject: Re: [nsp] Limiting bandwidth of P2P traffic
>
>
> from my experience rate limting by acess-lists on specific tcp ports, or
> nbar and policing which is abit buggy does the trick.
>
> i'd be interested to know what others are doing
>
>
>
> Mark
>
>
> ----- Original Message -----
> From: <francisv@dagupan.com>
> To: <cisco-nsp@puck.nether.net>
> Sent: Saturday, May 04, 2002 4:17 PM
> Subject: [nsp] Limiting bandwidth of P2P traffic
>
>
> > Hi,
> >
> > Is there a way to limit the bandwidth of P2P (Kazaa, Morpheus, iMesh,
> etc.)
> > traffic? We have a 7206VXR on the border and 3640 facing the
> client side.
> >
> > ---
> > francis a. vidal [bitstop network services] | http://www.bitstop.ph
> > streaming media + web hosting | http://www.keystone.ph
> > v(02)330-2871,(02)330-2872; f(02)330-2873 | http://www.kuro.ph
> >
> >
>
>
>
>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:43 EDT