[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230130130119.a36qt3t27xqahiup@skbuf>
Date: Mon, 30 Jan 2023 15:01:19 +0200
From: Vladimir Oltean <olteanv@...il.com>
To: Frank Wunderlich <frank-w@...lic-files.de>
Cc: Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
Landen Chao <Landen.Chao@...iatek.com>,
Sean Wang <sean.wang@...iatek.com>,
DENG Qingfang <dqfext@...il.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Daniel Golle <daniel@...rotopia.org>
Subject: Re: [BUG] vlan-aware bridge breaks vlan on another port on same gmac
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.
Powered by blists - more mailing lists