From: David R <david@unsolicited.net>
To: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: iptables problem upgrading kernel from 3.18.8 to 3.19.1
Date: Sun, 08 Mar 2015 10:12:25 +0000 [thread overview]
Message-ID: <54FC2089.6080809@unsolicited.net> (raw)
I've just had an exception to my "uneventful kernel upgrade" monotony.
My boot scripts failed when setting up the firewall due to this :-
xt_recent: hitcount (1) is larger than packets to be remembered (1)
for table xxxx
This is a completely straightforward
iptables -A yyyy -j REJECT -p tcp --reject-with tcp-reset -m recent
--set --name xxxx --rsource
Looking at the history for xt_recent.c it looks like this was introduced
in abc86d0f99242b7f142b7cb8f90e30081dd3c256 but maybe corrected in
cef9ed86ed62eeffcd017882278bbece32001f86 ?
Whatever, 3.19.1 is still affected, it can be worked around by setting
ip_pkt_list_tot in the module parameters.
Cheers
David
next reply other threads:[~2015-03-08 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 10:12 David R [this message]
2015-03-08 17:55 ` iptables problem upgrading kernel from 3.18.8 to 3.19.1 Florian Westphal
2015-03-12 19:47 ` David Miller
2015-03-16 13:54 ` Greg KH
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=54FC2089.6080809@unsolicited.net \
--to=david@unsolicited.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).