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 16:17:44 +0100 [thread overview]
Message-ID: <Yc8fGODCp2BmvszE@piout.net> (raw)
In-Reply-To: <20211231150651.GA1657469@euler>
On 31/12/2021 07:06:51-0800, Colin Foster wrote:
> Hi Alexandre
>
> On Fri, Dec 31, 2021 at 11:27:16AM +0100, Alexandre Belloni wrote:
> > Hi,
> >
> > On 30/12/2021 15:07:40-0800, Colin Foster wrote:
> > > Hi all,
> > >
> > > 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
Sorry, I meant "I can't exactly" ;)
> > can try:
> >
> > sysctl -w net.ipv6.conf.swp3.autoconf=0
>
> That sounds very promising! Sorry you had to fix my system config, but
> glad that this all makes perfect sense.
>
Let me know if this works ;) The bottom line being that you should
probably disable ipv6 autoconf on individual interfaces and then enable
it on the bridge.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-12-31 15:17 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
2021-12-31 15:06 ` Colin Foster
2021-12-31 15:17 ` Alexandre Belloni [this message]
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=Yc8fGODCp2BmvszE@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.