Thread (8 messages) 8 messages, 4 authors, 2022-01-01

Re: packets trickling out of STP-blocked ports

From: Colin Foster <colin.foster@in-advantage.com>
Date: 2021-12-31 15:53:32

On Fri, Dec 31, 2021 at 04:17:44PM +0100, Alexandre Belloni wrote:
On 31/12/2021 07:06:51-0800, Colin Foster wrote:
quoted
Hi Alexandre

On Fri, Dec 31, 2021 at 11:27:16AM +0100, Alexandre Belloni wrote:
quoted
Hi,

On 30/12/2021 15:07:40-0800, Colin Foster wrote:
quoted
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" ;)
quoted
quoted
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.
Just gave it a shot. No luck.

But poking around sysctl there's
net.ipv6.conf.swp3.router_solicitation{s,_delay,_interval,_max_interval}

As Andrew hints at, there might be some unintended consequences. It
seems that writing -1 to net.ipv6.conf.swp3.router_solicitation_delay
"fixed it." I don't know how that'll affect an IPv6 network in
production.

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help