[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZVSVq0fQ9qO9qTL3@Laptop-X1>
Date: Wed, 15 Nov 2023 17:55:55 +0800
From: Hangbin Liu <liuhangbin@...il.com>
To: Nikolay Aleksandrov <razor@...ckwall.org>
Cc: netdev@...r.kernel.org, "David S . Miller" <davem@...emloft.net>,
David Ahern <dsahern@...nel.org>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Ido Schimmel <idosch@...sch.org>, Roopa Prabhu <roopa@...dia.com>,
Stephen Hemminger <stephen@...workplumber.org>,
Florian Westphal <fw@...len.de>, Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>, Jiri Pirko <jiri@...nulli.us>
Subject: Re: [RFC PATCHv3 net-next 06/10] docs: bridge: add VLAN doc
On Wed, Nov 15, 2023 at 11:47:02AM +0200, Nikolay Aleksandrov wrote:
> > > But here it sounds a bit misleading, as if vlan-tagged frames are not
> > > handled otherwise. They are, just vlan tags are not considered when
> > > making forwarding decisions (e.g. FDB lookup).
> >
> > How about:
> >
> > VLAN filtering on a bridge is disabled by default. After enabling VLAN filtering
> > on a bridge, it will start forwarding frames to appropriate destinations based
> > on their VLAN tag.
>
> How about a little tweak like: ... it will start forwarding frames to
> appropriate destinations based on their destination MAC address and VLAN
> tag (both must match).
Sure, thanks for your modification.
Hangbin
Powered by blists - more mailing lists