From: Andrew Lunn <andrew@lunn.ch>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Colin Foster <colin.foster@in-advantage.com>,
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:31:37 +0100 [thread overview]
Message-ID: <Yc8iWYHLS5XQ9TLd@lunn.ch> (raw)
In-Reply-To: <Yc8fGODCp2BmvszE@piout.net>
> > > 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.
> >
Hi Alexandre
>
> 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.
Does this also stop the interface getting a link local IPv6 address
based on its MAC address?
e.g. my wifi interface has MAC address b8:ae:ed:78:ef:9d and gets an
IPv6 address
inet6 fe80::baae:edff:fe78:ef9d/64 scope link
It will also perform duplicate address detection, DAD, when the
interface is brought up. That is probably hard to see with tcpdump on
the host, since it happens very quickly, but a link peer should see
the packets.
Andrew
next prev parent reply other threads:[~2021-12-31 15:31 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
2021-12-31 15:31 ` Andrew Lunn [this message]
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=Yc8iWYHLS5XQ9TLd@lunn.ch \
--to=andrew@lunn.ch \
--cc=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).