From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 2/2] extensions: restore matching any SPI id by default
Date: Wed, 15 Jul 2015 19:30:35 +0200 [thread overview]
Message-ID: <20150715173035.GA5675@salvia> (raw)
In-Reply-To: <alpine.LSU.2.20.1507151907560.1320@nerf40.vanv.qr>
On Wed, Jul 15, 2015 at 07:10:29PM +0200, Jan Engelhardt wrote:
>
> On Wednesday 2015-07-15 18:55, Pablo Neira Ayuso wrote:
> >> >> +-p esp -m esp;-p esp -m esp --espspi 0;FAIL
> >> >> -p esp -m esp;=;OK
> >> >
> >
> >Given that this is changing the behaviour again, I would suggest that
> >-p esp -m esp displays -p -m esp --espspi 0:4294967295 via
> >iptables-save.
>
> The printing via iptables -S was not the problem.
> The patch is about that no AH/ESP packets were matched when using
> just "-m esp" because of the implied --espspi 0:0.
Without your patch:
iptables -A INPUT -p ah
# iptables-save
...
-A INPUT -p ah -m ah --ahspi 0
With your patch:
iptables -A INPUT -p ah
iptables -A INPUT -p ah --ahspi 0:4294967295
# iptables-save
...
-A INPUT -p ah -m ah
-A INPUT -p ah -m ah
what I'm suggesting is that this prints what it indeed does:
# iptables-save
...
-A INPUT -p ah --ahspi 0:4294967295
next prev parent reply other threads:[~2015-07-15 17:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 12:53 iptables: AH/ESP init fix, and a build fix Jan Engelhardt
2015-07-15 12:53 ` [PATCH 1/2] build: resolve build error involving libnftnl Jan Engelhardt
2015-07-15 16:28 ` Pablo Neira Ayuso
2015-07-15 12:53 ` [PATCH 2/2] extensions: restore matching any SPI id by default Jan Engelhardt
2015-07-15 16:24 ` Pablo Neira Ayuso
2015-07-15 16:41 ` Jan Engelhardt
2015-07-15 16:55 ` Pablo Neira Ayuso
2015-07-15 17:10 ` Jan Engelhardt
2015-07-15 17:30 ` Pablo Neira Ayuso [this message]
2015-07-15 17:46 ` Jan Engelhardt
2015-08-07 11:07 ` Pablo Neira Ayuso
2015-08-07 11:38 ` Jan Engelhardt
2015-08-10 12:04 ` Pablo Neira Ayuso
2015-08-10 12:15 ` Jan Engelhardt
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=20150715173035.GA5675@salvia \
--to=pablo@netfilter.org \
--cc=jengelh@inai.de \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.