From: Florian Westphal <fw@strlen.de>
To: Eugene Crosser <crosser@average.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: In raw prerouting, `iif` matches different interfaces in different kernels when enslaved in a vrf
Date: Sat, 2 Oct 2021 20:50:36 +0200 [thread overview]
Message-ID: <20211002185036.GJ2935@breakpoint.cc> (raw)
In-Reply-To: <17326577-1ab7-aaaa-0911-13ee131bdee0@average.org>
Eugene Crosser <crosser@average.org> wrote:
> Is this a known situation? Which behavior is "correct"?
No idea, your reproducer gives this on my laptop:
unshare -n bash repro.sh
net.ipv4.conf.veout.accept_local = 1
5.14.9-200.fc34.x86_64
conntrack v1.4.5 (conntrack-tools): connection tracking table has been emptied.
PING 172.30.30.2 (172.30.30.2) from 172.30.30.1 vein: 56(84) bytes of data.
--- 172.30.30.2 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
conntrack v1.4.5 (conntrack-tools): 0 flow entries have been shown.
A bisection is needed to figure out what introduced a change.
However, if this is already changeed for a few releases then we can't
revert it again.
next prev parent reply other threads:[~2021-10-02 18:50 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 [this message]
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
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=20211002185036.GJ2935@breakpoint.cc \
--to=fw@strlen.de \
--cc=crosser@average.org \
--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).