From: Florian Westphal <fw@strlen.de>
To: Eugene Crosser <crosser@average.org>
Cc: Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org,
Jinpu Wang <jinpu.wang@ionos.com>
Subject: Re: In raw prerouting, `iif` matches different interfaces in different kernels when enslaved in a vrf
Date: Thu, 7 Oct 2021 11:31:31 +0200 [thread overview]
Message-ID: <20211007093131.GC25730@breakpoint.cc> (raw)
In-Reply-To: <060e0d5e-b40f-204a-1894-c1eef8c8411d@average.org>
Eugene Crosser <crosser@average.org> wrote:
> On 06/10/2021 17:03, Florian Westphal wrote:
>
> > > It looks like Jinpu Wang <jinpu.wang@ionos.com> has found the offending
> > > commit, it's 09e856d54bda5f28 "vrf: Reset skb conntrack connection on VRF
> > > rcv" from Aug 15 2021.
> >
> > This change is very recent, you reported failure between 5.4 and 5.10, or was
> > that already backported?
> >
> > This change doesn't influcence matching either, but it does zap the ct
> > zone association afaics.
>
> Yes, looks like it was backported to Debian/Ubuntu kernels
>
> Jinpu reported that reverting the change restores the "old" behaviour.
>
> But we have not yet checked how it affects SNAT.
Can you start a new thread on netdev and CC author of that commit
and l3m/vrf maintainers/authors?
I'm afraid you won't find anyone on the netfilter lists that can make
any statements on what the VRF expectations are.
next prev parent reply other threads:[~2021-10-07 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 15:19 In raw prerouting, `iif` matches different interfaces in different kernels when enslaved in a vrf Eugene Crosser
2021-10-02 18:50 ` Florian Westphal
2021-10-06 12:11 ` Eugene Crosser
2021-10-06 14:48 ` Eugene Crosser
2021-10-06 15:03 ` Florian Westphal
2021-10-06 15:09 ` Eugene Crosser
2021-10-07 9:31 ` Florian Westphal [this message]
2021-10-07 9:29 ` Florian Westphal
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=20211007093131.GC25730@breakpoint.cc \
--to=fw@strlen.de \
--cc=crosser@average.org \
--cc=jinpu.wang@ionos.com \
--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).