Multiple Exit Nodes - Metric Not Honoured

[washcroft]

Describe the problem

In our deployment, we have multiple exit nodes, each assigned to a different user group, and one default exit node for the "All" group.

Everybody logging into Netbird will get the All group, and therefore the default exit node, but if you're also a member of more specially privileged group, you'll get access to more exit nodes which themselves can access more resources.

However it seems the metric isn't being honoured in this situation, even though the default exit node has the highest metric (9999), higher than all other exit nodes, traffic is still being routed through this exit node.

To Reproduce

See screenshots.

Expected behavior

As described above.

Are you using NetBird Cloud?

Self-hosted

NetBird version

0.47.1

Is any other VPN software installed?

No

Screenshots

Debug Upload Key: 6790e8695d8c5e42d2ca22af0f62b9d2ac51312c633b35f798432aa6a93c0263/2f79283e-c81a-484f-82d7-bbac92d72c3f

status output.txt

Additional context

None

Have you tried these troubleshooting steps?

• [X] Reviewed client troubleshooting (if applicable)
• [X] Checked for newer NetBird versions
• [X] Searched for similar issues on GitHub (including closed ones)
• [X] Restarted the NetBird client
• [X] Disabled other VPN software
• [X] Checked firewall settings

[nazarewk]

1. metric is in no way related to the operating system route metric
2. metric is considered only within the scope of a single Network Route object. Effectively when considering more than one routing peer grouped under the Network Route in the UI

[washcroft]

@nazarewk thank you, that makes sense - am I missing something in how I would achieve this, or is avoiding overlapping groups the only way?