From: Ido Schimmel <idosch@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
dsahern@kernel.org
Subject: Re: [PATCH net-next v2] ipv6: clean up routes when manually removing address with a lifetime
Date: Thu, 13 Nov 2025 14:18:38 +0200 [thread overview]
Message-ID: <aRXMnmTapb9VNbc4@shredder> (raw)
In-Reply-To: <20251113031700.3736285-1-kuba@kernel.org>
On Wed, Nov 12, 2025 at 07:17:00PM -0800, Jakub Kicinski wrote:
> When an IPv6 address with a finite lifetime (configured with valid_lft
> and preferred_lft) is manually deleted, the kernel does not clean up the
> associated prefix route. This results in orphaned routes (marked "proto
> kernel") remaining in the routing table even after their corresponding
> address has been deleted.
>
> This is particularly problematic on networks using combination of SLAAC
> and bridges.
>
> 1. Machine comes up and performs RA on eth0.
> 2. User creates a bridge
> - does an ip -6 addr flush dev eth0;
> - adds the eth0 under the bridge.
> 3. SLAAC happens on br0.
>
> Even tho the address has "moved" to br0 there will still be a route
> pointing to eth0, but eth0 is not usable for IP any more.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
next prev parent reply other threads:[~2025-11-13 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 3:17 [PATCH net-next v2] ipv6: clean up routes when manually removing address with a lifetime Jakub Kicinski
2025-11-13 5:11 ` David Ahern
2025-11-13 12:18 ` Ido Schimmel [this message]
2025-11-15 2:02 ` patchwork-bot+netdevbpf
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=aRXMnmTapb9VNbc4@shredder \
--to=idosch@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.