From: Jesper Dangaard Brouer <hawk@diku.dk>
To: netfilter@vger.kernel.org
Subject: Re: iptables limit --limit limitations
Date: Sat, 31 May 2008 18:33:55 +0000 (UTC) [thread overview]
Message-ID: <loom.20080531T183021-215@post.gmane.org> (raw)
In-Reply-To: alpine.LNX.1.10.0805261319140.19084@fbirervta.pbzchgretzou.qr
Jan Engelhardt <jengelh <at> medozas.de> writes:
> It is known that the algorithm in limit and hashlimit are not quite
> accurate. Though, we seem to be out of solutions, too.
Here is a paper on it here:
http://people.netfilter.org/acidfu/papers/limit-tbf-analysis.pdf
I don't know if the solution proposed has been implemented (and accepted
upstream)???
Cheers,
Jesper Brouer
prev parent reply other threads:[~2008-05-31 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 7:20 iptables limit --limit limitations Payam Chychi
2008-05-26 11:20 ` Jan Engelhardt
2008-05-31 18:33 ` Jesper Dangaard Brouer [this message]
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=loom.20080531T183021-215@post.gmane.org \
--to=hawk@diku.dk \
--cc=netfilter@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