From: Vladimir Oltean <olteanv@gmail.com>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Landen Chao <Landen.Chao@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
DENG Qingfang <dqfext@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Daniel Golle <daniel@makrotopia.org>
Subject: Re: [BUG] vlan-aware bridge breaks vlan on another port on same gmac
Date: Mon, 30 Jan 2023 15:01:19 +0200 [thread overview]
Message-ID: <20230130130119.a36qt3t27xqahiup@skbuf> (raw)
In-Reply-To: <trinity-fd23c4a0-a979-475e-a077-330577d7d632-1674311727972@3c-app-gmx-bap60>
On Sat, Jan 21, 2023 at 03:35:28PM +0100, Frank Wunderlich wrote:
> btw. why is my vlan software-only and not pushed to hardware?
Short story, because committing it to hardware is a useless complication.
A standalone port should be VLAN-unaware, or i.o.w. it should not drop
based on VLAN port membership, shouldn't add or strip any VLAN header,
and should forward as if the VLAN wasn't there.
So the behavior of a standalone port is absolutely sufficient as a basis
for an 8021q upper interface to see the traffic it needs, and for the
traffic it sends to reach the outside world as it intended.
prev parent reply other threads:[~2023-01-30 13:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 16:45 [BUG] vlan-aware bridge breaks vlan on another port on same gmac Frank Wunderlich
2023-01-20 17:21 ` Vladimir Oltean
2023-01-20 23:34 ` [PATCH] mt7530 don't make the CPU port a VLAN user port kernel test robot
2023-01-21 12:11 ` Aw: Re: [BUG] vlan-aware bridge breaks vlan on another port on same gmac Frank Wunderlich
2023-01-21 12:22 ` Vladimir Oltean
2023-01-21 12:32 ` Aw: " Frank Wunderlich
2023-01-21 13:35 ` Vladimir Oltean
2023-01-21 14:12 ` Aw: " Frank Wunderlich
2023-01-30 12:58 ` Vladimir Oltean
2023-01-31 16:23 ` Aw: " Frank Wunderlich
2023-02-05 13:48 ` Frank Wunderlich
2023-02-05 13:59 ` Vladimir Oltean
2023-01-21 14:35 ` Aw: " Frank Wunderlich
2023-01-30 13:01 ` Vladimir Oltean [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=20230130130119.a36qt3t27xqahiup@skbuf \
--to=olteanv@gmail.com \
--cc=Landen.Chao@mediatek.com \
--cc=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=frank-w@public-files.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sean.wang@mediatek.com \
/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