Mailing List Archive: nsp: extreme

rate-limit

Index | Next | Previous | View Threaded

networking at hostalia

Aug 17, 2007, 3:34 PM

Post #1 of 4 (1674 views)
Permalink

rate-limit

An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/extreme-nsp/attachments/20070818/d6f72978/attachment.html

infothec at web

Aug 18, 2007, 1:45 AM

Post #2 of 4 (1578 views)
Permalink

rate-limit [In reply to]

this depends on what you mean with creates more damage than help. I do not remember that i-series damage the traffic, because those are able rate shape. you have not a great granularity, but it works. if this damage your traffic, I think your traffic will always damaged by rate limiters (as in the 200, 450s) or rate shapers. is your traffic UDP or TCP? in the case of TCP it should work well. more bad for UDP traffic. reg hvm

*Von:* I?aki Mart?nez D?ez <NETWORKING at HOSTALIA.COM>
*Gesendet:* 18.08.07 01:36:17
*An:* extreme-nsp at puck.nether.net
*Betreff:* [e-nsp] rate-limit

Hi,

I need to limit a port to a bandwidth limit if possible inbound andoutbound.

I have 3 models, summit 200 with ExtremeWare (7.6 and 7.7), X250 andx450 with ExtremeOS (12).

In the ExtremeWare i use this:

create access-mask RATELIMIT ports precedence1000
create rate-limit <port_name> RATELIMIT port <port_number>permit limit <mbps> exceed-actiondrop

But this is no efficient and there is no real rate-limiting in theport and cause more damage than help.

Can anybody help me to rate-limiting a port??

Thanks in advance.

_______________________________________________extreme-nsp mailing listextreme-nsp at puck.nether.nethttps://puck.nether.net/mailman/listinfo/extreme-nsp

In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten!
Nur 3,99 EUR/Monat! *http://www.maildomain.web.de/?mc=021114* [http://www.maildomain.web.de/?mc=021114]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/extreme-nsp/attachments/20070818/4ebc2a4c/attachment.html

networking at hostalia

Aug 18, 2007, 2:22 AM

Post #3 of 4 (1573 views)
Permalink

rate-limit [In reply to]

infothec at web.de wrote:
> this depends on what you mean with creates more damage than help.
Well i mean than rate-limiting in the ExtremeWare cause this (limiting
to 16 Mbps):
1) a single connection does not go more than 300 Kbps
2) when the port (really the server behind the port) has an attack
(specially UDP) the traffic goes up to the limit of the port (10 o 100 Mbps)

> is your traffic UDP or TCP?

mainly TCP.

I need some configuration to limit bandwidth in a port and also prevent
UDP attacks.

Thanks.

swmike at swm

Aug 18, 2007, 2:44 AM

Post #4 of 4 (1592 views)
Permalink

rate-limit [In reply to]

On Sat, 18 Aug 2007, I?aki Mart?nez D?ez wrote:

> 1) a single connection does not go more than 300 Kbps

This is classical due to the burst size being too small, so TCP goes into
saw-tooth mode (slow-start, quickly rises in speed, hits rate-limiter that
drops multiple packets, goes back into slow-start, repeat forever).

I don't have access to any Summit200 so I don't know if the burst size can
be increased, but if it can you should try that.

--
Mikael Abrahamsson email: swmike at swm.pp.se

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads