policy/v2, state: elect primaries by oldest control session

A router that reconnects joins as a standby; one that kept its session
takes its routes back once available again, as on Tailscale. Both the
global and the via election use it, in place of anti-flap stickiness.
This commit is contained in:
Kristoffer Dalby committed 2026-10-28 19:06:05 +00:00
1 parent 5329b35d45
commit df86073f54
16 files changed
+441 -252

No files matched your search

+4
View File
@@ -345,6 +345,10 @@ availability](https://tailscale.com/docs/how-to/set-up-high-availability#subnet-
This feature is enabled by default when at least two nodes advertise the same prefix. See the configuration options
`node.routes.ha` in the [configuration file](configuration.md) for details.
Of the routers that are online, healthy and not expired, the one connected to Headscale the longest serves a route. A
router that reconnects becomes a standby, while a router that stays connected takes its routes back once it is approved,
healthy or unexpired again. When none is available, the route stays with the router that served it last.
## Troubleshooting
### Enable IP forwarding