From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Colin Foster <colin.foster@in-advantage.com>
Cc: netdev@vger.kernel.org, Vladimir Oltean <olteanv@gmail.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: Re: packets trickling out of STP-blocked ports
Date: Fri, 31 Dec 2021 11:27:16 +0100 [thread overview]
Message-ID: <Yc7bBLupVUQC9b3X@piout.net> (raw)
In-Reply-To: <20211230230740.GA1510894@euler>
Hi,
On 30/12/2021 15:07:40-0800, Colin Foster wrote:
> Hi all,
>
> I'm not sure who all to include in this email, but I'm starting with
> this list to start.
>
> Probably obvious to those in this email list, I'm testing a VSC7512 dev
> board controlled via SPI. The patches are still out-of-tree, but I
> figured I'll report these findings, since they seem real.
>
> My setup is port 0 of the 7512 is tied to a Beaglebone Black. Port 1 is
> tied to my development PC. Ports 2 and 3 are tied together to test STP.
>
> I run the commands:
>
> ip link set eth0 up
> ip link set swp[1-3] up
> ip link add name br0 type bridge stp_state 1
> ip link set dev swp[1-3] master br0
> ip addr add 10.100.3.1/16 dev br0
> ip link set dev br0 up
>
> After running this, the STP blocks swp3, and swp1/2 are forwarding.
>
> Periodically I see messages saying that swp2 is receiving packets with
> own address as source address.
>
> I can confirm that via ethtool that TX packets are increasing on swp3. I
> believe I captured the event via tshark. A 4 minute capture showed three
> non-STP packets on swp2. All three of these packets are ICMPv6 Router
> Solicitation packets.
>
> I would expect no packets at all to egress swp3. Is this an issue that
> is unique to me and my in-development configuration? Or is this an issue
> with all Ocelot / Felix devices?
>
> If this is an Ocelot thing, I can try to come up with a different test
> setup to capture more data... printing the packet when it is received,
> capturing the traffic externally, capturing eth0 traffic to see if it is
> coming from the kernel or being hardware-forwarded...
>
> (side note - if there's a place where a parser for Ocelot NPI traffic is
> hidden, that might eventually save me a lot of debugging in Lua)
>
>
> An idea of how frequently this happens - my system has been currently up
> for 3700 seconds. Eight "own address as source address" events have
> happened at 66, 96, 156, 279, 509, 996, 1897, and 3699 seconds.
>
This is something I solved back in 2017. I can exactly remember how, you
can try:
sysctl -w net.ipv6.conf.swp3.autoconf=0
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-12-31 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 23:07 packets trickling out of STP-blocked ports Colin Foster
2021-12-31 0:28 ` Vladimir Oltean
2022-01-01 16:04 ` Vladimir Oltean
2021-12-31 10:27 ` Alexandre Belloni [this message]
2021-12-31 15:06 ` Colin Foster
2021-12-31 15:17 ` Alexandre Belloni
2021-12-31 15:31 ` Andrew Lunn
2021-12-31 15:53 ` Colin Foster
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=Yc7bBLupVUQC9b3X@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=colin.foster@in-advantage.com \
--cc=horatiu.vultur@microchip.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.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).