From: Phil Sutter <phil@nwl.cc>
To: Roman Mamedov <rm@romanrm.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: iptables: considers incomplete rule in -C and finds an erroneous match
Date: Tue, 6 Feb 2024 16:07:25 +0100 [thread overview]
Message-ID: <ZcJLLfd6mqN-kGF2@orbyte.nwl.cc> (raw)
In-Reply-To: <20240205044519.45334f8e@nvm>
Hi,
On Mon, Feb 05, 2024 at 04:45:19AM +0500, Roman Mamedov wrote:
> Hello,
>
> According to my ip6tables, a rule like this already exists:
>
> # ip6tables -C INPUT -p tcp -m multiport --dports 80,443 -j ACCEPT && echo Exists
> Exists
>
> Except that it doesn't, and an extra IP filter is present:
>
> # ip6tables-save | grep 80,443
> -A INPUT -s fd39::/16 -p tcp -m multiport --dports 80,443 -j ACCEPT
>
> Is that the expected behaviour?
>
> ip6tables v1.8.9 (legacy)
This is already fixed in v1.8.10 by commit 78850e7dba64a ("ip6tables:
Fix checking existence of rule").
Cheers, Phil
prev parent reply other threads:[~2024-02-06 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 23:45 iptables: considers incomplete rule in -C and finds an erroneous match Roman Mamedov
2024-02-04 23:59 ` Roman Mamedov
2024-02-06 15:07 ` Phil Sutter [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=ZcJLLfd6mqN-kGF2@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=netfilter-devel@vger.kernel.org \
--cc=rm@romanrm.net \
/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).