From: Marco Padovan <evcz@evcz.tk>
To: netfilter <netfilter@vger.kernel.org>
Subject: xt_hashlimit: max count of 8192 reached
Date: Sun, 18 Nov 2012 17:45:42 +0100 [thread overview]
Message-ID: <50A910B6.4000607@evcz.tk> (raw)
I'm using this ruleon iptables v1.4.7
iptables -A INSYNSRCLIMITER -m hashlimit --hashlimit-htable-expire 10000
--hashlimit-htable-size 8192 --hashlimit-htable-max 8192
--hashlimit-mode srcip --hashlimit-name insynlimiter --hashlimit 1/s
--hashlimit-burst 25 -j RETURN
while being "synflooded" and I'm seeing a lot of
xt_hashlimit: max count of 8192 reached
errors logged... really a lot (just to explain how many of those: got a
bunch of "net_ratelimit: 42695 callbacks suppressed"logged too...)
What does exactly that errors mean?
did there was more then 8192 srcip to track and hashlimit went in
overflow or am I using --hashlimit-htable-size and
--hashlimit-htable-max in the wrong way?
next reply other threads:[~2012-11-18 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 16:45 Marco Padovan [this message]
[not found] ` <CAJygYd3kr9a-LVXAhPyrDyXuPCGo2GZeOj156yLV=Tfen_+09w@mail.gmail.com>
2012-11-19 5:41 ` xt_hashlimit: max count of 8192 reached 叶雨飞
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=50A910B6.4000607@evcz.tk \
--to=evcz@evcz.tk \
--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