From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Etienne Champetier <champetier.etienne@gmail.com>
Cc: Tobias Waldekranz <tobias@waldekranz.com>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: mv88e6xxx / MV88E6176 + VLAN-aware unusable in 5.15.98 (ok in 5.10.168) (resend)
Date: Tue, 14 Mar 2023 00:30:49 +0200 [thread overview]
Message-ID: <20230313223049.sjlxagsmbpjwwyqj@skbuf> (raw)
In-Reply-To: <cd306c78-14a6-bebb-e174-2917734b4799@gmail.com>
Hi Etienne,
On Sun, Mar 12, 2023 at 12:41:32AM -0500, Etienne Champetier wrote:
> I get tagged frame with VID 3 on lan4 (at least some multicast & broadcast), but lan4 is not a member of VLAN 3
> Also unicast frames from wifi to lan4 exit tagged with VID 2, broadcast frames are fine (verifed with scapy)
> Reverting
> 5bded8259ee3 "net: dsa: mv88e6xxx: isolate the ATU databases of standalone and bridged ports" from Vladimir
> and
> b80dc51b72e2 "net: dsa: mv88e6xxx: Only allow LAG offload on supported hardware"
> 57e661aae6a8 "net: dsa: mv88e6xxx: Link aggregation support"
> from Tobias allow me to get back to 5.10 behavior / working system.
>
> On the OpenWrt side, 5.15 is the latest supported kernel, so I was not able to try more recent for now.
I don't know and I am not able to reproduce this on Turris MOX with a linux-5.15.y
kernel from https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git.
Could we approach this from the other end? I would like to try and
reproduce the issue with the kernel you are using. But I have no idea
how to use OpenWRT or to navigate through its build system. Could you
help me figure out which source code is built for the Omnia board (plus
additional OpenWRT patches, if any)?
I might also ask you to provide a reproducer for the issue using regular
iproute2 tools starting from an unconfigured system (bridge, ip, etc, as
opposed to the network manager from OpenWRT and its /etc/config/network
configuration file), if this wouldn't be too much effort.
Also, not clear which interface exactly you mean by "wifi" ("unicast
frames from wifi to lan4 exit tagged with VID 2").
Thanks.
next prev parent reply other threads:[~2023-03-13 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 5:41 mv88e6xxx / MV88E6176 + VLAN-aware unusable in 5.15.98 (ok in 5.10.168) (resend) Etienne Champetier
2023-03-12 12:11 ` Tobias Waldekranz
2023-03-13 3:13 ` Etienne Champetier
2023-03-13 22:30 ` Vladimir Oltean [this message]
2023-03-15 2:35 ` Etienne Champetier
2023-03-15 9:23 ` Vladimir Oltean
2023-03-16 15:40 ` Marek Behún
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=20230313223049.sjlxagsmbpjwwyqj@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=champetier.etienne@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tobias@waldekranz.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