From: Andrew Lunn <andrew@lunn.ch>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Tobias Waldekranz <tobias@waldekranz.com>,
netdev <netdev@vger.kernel.org>,
"emeric.dupont@zii.aero" <emeric.dupont@zii.aero>
Subject: Re: Regression with improved multi chip isolation
Date: Sun, 6 Mar 2022 21:27:13 +0100 [thread overview]
Message-ID: <YiUZIZL8goU/3rPI@lunn.ch> (raw)
In-Reply-To: <20220306194926.hx7kcivrrssnq7qz@skbuf>
> This example of injecting traffic through br0.11 is interesting because
> I think that Tobias' patch merely exposes a shortcoming of tag_dsa.c.
> The tagger should inject packets into the switch in VLAN 4095
> (MV88E6XXX_VID_BRIDGED), because the ports offload a VLAN-unaware bridge.
> Yet my guess is that it probably does so in VID 11 - this can be seen
> using tcpdump and analyzing the DSA header.
20:25:42.239330 5a:e0:ae:a2:f6:db (oui Unknown) > Broadcast, ethertype MEDSA (0xdada), length 50: Forward, tagged, dev.port:vlan 3.0:11, pri 0: ethertype ARP (0x0806) Request who-has 10.42.11.2 tell 10.42.11.1, length 28
20:25:43.279670 5a:e0:ae:a2:f6:db (oui Unknown) > Broadcast, ethertype MEDSA (0xdada), length 50: Forward, tagged, dev.port:vlan 3.0:11, pri 0: ethertype ARP (0x0806) Request who-has 10.42.11.2 tell 10.42.11.1, length 28
20:25:44.319299 5a:e0:ae:a2:f6:db (oui Unknown) > Broadcast, ethertype MEDSA (0xdada), length 50: Forward, tagged, dev.port:vlan 3.0:11, pri 0: ethertype ARP (0x0806) Request who-has 10.42.11.2 tell 10.42.11.1, length 28
20:25:45.359288 5a:e0:ae:a2:f6:db (oui Unknown) > Broadcast, ethertype MEDSA (0xdada), length 50: Forward, tagged, dev.port:vlan 3.0:11, pri 0: ethertype ARP (0x0806) Request who-has 10.42.11.2 tell 10.42.11.1, length 28
Andrew
next prev parent reply other threads:[~2022-03-06 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 19:15 Regression with improved multi chip isolation Andrew Lunn
2022-03-06 19:49 ` Vladimir Oltean
2022-03-06 20:27 ` Andrew Lunn [this message]
2022-03-07 9:21 ` Tobias Waldekranz
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=YiUZIZL8goU/3rPI@lunn.ch \
--to=andrew@lunn.ch \
--cc=emeric.dupont@zii.aero \
--cc=netdev@vger.kernel.org \
--cc=tobias@waldekranz.com \
--cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).