From: Florian Westphal <fw@strlen.de>
To: "Antoine C." <acalando@free.fr>
Cc: netfilter-devel@vger.kernel.org,
Pablo Neira Ayuso <pablo@netfilter.org>,
Eric Woudstra <ericwouds@gmail.com>
Subject: Re: bug report: MAC src + protocol optiomization failing with 802.1Q frames
Date: Mon, 27 Oct 2025 19:37:42 +0100 [thread overview]
Message-ID: <aP-76gB9axgCebpL@strlen.de> (raw)
In-Reply-To: <1676410308.11476569.1761589612512.JavaMail.root@zimbra62-e11.priv.proxad.net>
Antoine C. <acalando@free.fr> wrote:
>
> This bug does not seem to get a lot of attention but may be it
> deserves at least to be filed ?
Its a design bug and so far not a single solution was
presented.
And no one answered any of the questions that I asked.
So, whats YOUR opinion?
> > Should "ip saddr 1.2.3.4" match:
> >
> > Only in classic ethernet case?
> > In VLAN?
> > In QinQ?
> >
> > What about IP packet in a PPPOE frame?
> > What about other L2 protocols?
As long as nobody defines how any of this is supposed to work
in the first place nothing will happen here.
What you encounter is the 'historic random behaviour' where outcome
depends on the hidden dependencies that nft (userspace) inserts and
if vlan offload was disabled.
next prev parent reply other threads:[~2025-10-27 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-12 20:59 bug report: MAC src + protocol optiomization failing with 802.1Q frames Antoine C.
2025-10-12 21:44 ` Florian Westphal
2025-10-27 18:26 ` Antoine C.
2025-10-27 18:37 ` Florian Westphal [this message]
2025-10-27 22:40 ` Antoine C.
2025-11-06 23:46 ` 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=aP-76gB9axgCebpL@strlen.de \
--to=fw@strlen.de \
--cc=acalando@free.fr \
--cc=ericwouds@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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.