Brendan Creane ce19ee0b47 net/routemanager: keep the coarse CGNAT and ULA routes when a peer advertises them (#21901) ...

A peer can advertise 100.64.0.0/10 or fd7a:115c:a1e0::/48 as a subnet
route. Those prefixes are also the coarse routes that stand in for peers'
individual addresses, so one OS route entry has two reasons to exist.
applyDirty set that entry from one reason at a time, so removing the
advertising peer deleted the /10 while coarsening still wanted it, and
turning coarsening off deleted the /10 while a peer still advertised it.
Set each coarse prefix once, from both inputs, as rebuildAll already does.

Fixes #21890

Signed-off-by: Brendan Creane <bcreane@gmail.com>

2026-10-27 08:04:50 -07:00

..

fortest.go

net/routemanager: add incremental route manager

2026-07-10 16:57:09 -07:00

routemanager_test.go

net/routemanager: keep the coarse CGNAT and ULA routes when a peer advertises them (#21901)

2026-10-27 08:04:50 -07:00

routemanager.go

net/routemanager: keep the coarse CGNAT and ULA routes when a peer advertises them (#21901)

2026-10-27 08:04:50 -07:00