From: Eric Garver <egarver@redhat.com>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v2 nf] netfilter: conntrack: set icmpv6 redirects as RELATED
Date: Wed, 23 Nov 2022 10:00:47 -0500	[thread overview]
Message-ID: <Y341n075lg67rm0U@wsfd-netdev-vmhost.ntdv.lab.eng.bos.redhat.com> (raw)
In-Reply-To: <20221123121639.27624-1-fw@strlen.de>
On Wed, Nov 23, 2022 at 01:16:39PM +0100, Florian Westphal wrote:
> icmp conntrack will set icmp redirects as RELATED, but icmpv6 will not
> do this.
> 
> For icmpv6, only icmp errors (code <= 128) are examined for RELATED state.
> ICMPV6 Redirects are part of neighbour discovery mechanism, those are
> handled by marking a selected subset (e.g.  neighbour solicitations) as
> UNTRACKED, but not REDIRECT -- they will thus be flagged as INVALID.
> 
> Add minimal support for REDIRECTs.  No parsing of neighbour options is
> added for simplicity, so this will only check that we have the embeeded
> original header (ND_OPT_REDIRECT_HDR), and then attempt to do a flow
> lookup for this tuple.
> 
> Also extend the existing test case to cover redirects.
> 
> Reported-by: Eric Garver <eric@garver.life>
> Link: https://github.com/firewalld/firewalld/issues/1046
> Signed-off-by: Florian Westphal <fw@strlen.de>
> ---
>  v2: fix up comment typo and reformat commit message.  No other changes.
> 
>  net/netfilter/nf_conntrack_proto_icmpv6.c     | 53 +++++++++++++++++++
>  .../netfilter/conntrack_icmp_related.sh       | 36 ++++++++++++-
>  2 files changed, 87 insertions(+), 2 deletions(-)
Thanks Florian!
Acked-by: Eric Garver <eric@garver.life>
next prev parent reply	other threads:[~2022-11-23 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 12:16 [PATCH v2 nf] netfilter: conntrack: set icmpv6 redirects as RELATED Florian Westphal
2022-11-23 15:00 ` Eric Garver [this message]
2022-11-26 10:06 ` kernel test robot
2022-11-30 17:30 ` Pablo Neira Ayuso
2022-11-30 17:53   ` Pablo Neira Ayuso
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=Y341n075lg67rm0U@wsfd-netdev-vmhost.ntdv.lab.eng.bos.redhat.com \
    --to=egarver@redhat.com \
    --cc=fw@strlen.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 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).