Client doesn't remember the last selected routes / exit nodes & detect if route is accessible directly

[florian-obradovic]

Slack: https://netbirdio.slack.com/archives/C02KHAE8VLZ/p1716836567943349

To Reproduce

• Connect
• Disable a route, for example an exit node
• Disconnect & Connect again
• All routes are selected again ![Uploading CleanShot 2024-05-27 at 21.00.34.gif…]()

Expected behaviour

• Remember the last selected (enabled or disabled) routes. I don't want to disable the exit node every time I connect.
• In other words: I only want to select the exit node, if I really need it :slightly_smiling_face:
• published routes shouldn't be used, if accessible locally / directly !

Are you using NetBird Cloud? No, self-host NetBird's control plane

NetBird version

• 0.27.10 (darwin/arm64)

[bcmmbaga]

Hello @florian-obradovic, This is the current behavior, but we will be adding persistence for route selections in one of the upcoming 0.28 versions, so your last selected routes (enabled or disabled) will be remembered.

[florian-obradovic]

@bcmmbaga thanks a lot !

[jan-schnurpfeil-gcx]

This would be a huge gain in convenience, thanks a lot!

Perhaps it would also be possible to toggle the default route directly in the systray menu of the UI client without having to go to the full route selection window?

In my use case, I usually don't need the default route, but sometimes I want to route everything through the exit node.

[flotpg]

Hey @bcmmbaga any news on this?

This causes significant issues if the exit node and the client are at same subnet.

[maxcerny]

+1 on this

every time my system boots up and netbird autostarts, i have 3 exit nodes enabled, along with subnet routes for subnets that are reachable without netbird. Causes all kinds of havoc. Either being able to set what routes get auto-applied to which client, if the route get's auto-applied at all, or having the client remember the routes selected, should be a top priority.

[jmezinko]

I'd like to +1 this request