From: Cedric Blancher <blancher@cartel-securite.fr>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: netfilter mailing list <netfilter@lists.netfilter.org>
Subject: Re: next topic: --limit and --burst-limit
Date: 31 Oct 2002 15:04:22 +0100 [thread overview]
Message-ID: <1036073063.21852.34.camel@elendil> (raw)
In-Reply-To: <Pine.LNX.4.44.0210310704480.30108-100000@localhost.localdomain>
Le jeu 31/10/2002 à 13:15, Robert P. J. Day a écrit :
> example:
> limit: 3/hour
> burst: 5
>
> what does this mean? it means that i start with a bucket of 5 tokens
> and, every time a matching packet comes in, i can accept it by paying
> a token. simple as that. when i run out of tokens, i can't accept
> any more packets until i get more tokens.
That's it. It another interesting point of vue ;)
> and with a limit of 3/hour, every 20 minutes, i get another token dropped
> into my bucket, up to a maximum of my burst value of 5, so that i can
> accept more packets. that's it. is it really that simple?
You begin with 8 tokens and that's you maximum number of tokens. 5 for
the burst (lower part of my bucket), and 3 that are time dependant
(upper part of the bucket).
Each time you receive a packet, you pay it with a token, so you can pay
for 8 packets within the first _hour_. Then, at the end of this first
hour, you will get three more tokens up to 8 tokens.
I can be wrong, but that's what I understood from the HOWTO, as for 1/s
limit with burst of 5, you first accept 6 packets.
Moreover, limit does not imply average value. You say 3 packets in an
hour. If you loose all your toeksn within the first second, then you
won't be able to match anything till the next hour. That's why limit
match is not really applicable for trafic shaping as an example.
Hope I've been more clear.
--
Cédric Blancher <blancher@cartel-securite.fr>
IT systems and networks security expert - Cartel Sécurité
Phone : +33 (0)1 44 06 97 87 - Fax: +33 (0)1 44 06 97 99
PGP KeyID:157E98EE FingerPrint:FA62226DA9E72FA8AECAA240008B480E157E98EE
next prev parent reply other threads:[~2002-10-31 14:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 18:47 next topic: --limit and --burst-limit Robert P. J. Day
2002-10-31 8:24 ` Cedric Blancher
2002-10-31 11:00 ` Robert P. J. Day
2002-10-31 13:51 ` Cedric Blancher
2002-10-31 15:04 ` Robert P. J. Day
2002-10-31 12:15 ` Robert P. J. Day
2002-10-31 14:04 ` Cedric Blancher [this message]
2002-10-31 14:27 ` Robert P. J. Day
2002-10-31 15:34 ` Cedric Blancher
-- strict thread matches above, loose matches on Subject: below --
2002-10-31 14:47 mailinglists
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=1036073063.21852.34.camel@elendil \
--to=blancher@cartel-securite.fr \
--cc=netfilter@lists.netfilter.org \
--cc=rpjday@mindspring.com \
/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