SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-06-13 10:51:52 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

New network route logic has lower priority in route table #895

New Issue
Open
opened 2025-11-20 05:19:30 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:19:30 -05:00
Owner
Copy Link

Originally created by @Thunderbottom on GitHub (May 16, 2024).

Describe the problem

Recently, on upgrading to the latest netbird versions (> 0.27.0), new networking route logic is being used, which creates a separate route table for netbird with a priority number higher than the main route table (lower priority overall). This causes netbird to fail to route to subnet network routes that collide with the user's local subnet. On connecting to netbird, the netbird routes should have a higher priority than the main table routes (lower priority number).

For example, on connecting to tailscale, the tailscale route network creates a routing table with priority 50, and the main table has a priority of 100. In case of netbird, it creates a route table with priority 110 and sets the main table's priority to 100. See the code here:

a5811a2d7d/client/internal/routemanager/systemops_linux.go (L76-L83)

Currently to fix this, we need to revert to the old routing logic:

$ sudo mkdir -p /etc/sysconfig
$ echo 'NB_USE_LEGACY_ROUTING=true'  | sudo tee -a /etc/sysconfig/netbird
$ sudo systemctl restart netbird

To Reproduce

Steps to reproduce the behavior:

  1. Upgrade to a newer version of Netbird.
  2. Check ip route show. It won't show the Netbird routes in the main table.
  3. Check ip route show table all. See Netbird table with ID 7120.
  4. Check ip rule show. See that the main table has a higher lookup priority than the Netbird table.
  5. Netbird network route fails in case the network route's subnet (eg. 192.168.0.0/16), overlaps with the local network subnet (eg. 192.168.0.0/24).

Expected behavior

On connecting to Netbird, the Netbird routes should have a higher lookup priority than the local subnet.

Are you using NetBird Cloud?

Self-hosted NetBird's control plane.

NetBird version

netbird version: 0.27.7

Originally created by @Thunderbottom on GitHub (May 16, 2024). **Describe the problem** Recently, on upgrading to the latest netbird versions (> `0.27.0`), new networking route logic is being used, which creates a separate route table for netbird with a priority number higher than the main route table (lower priority overall). This causes netbird to fail to route to subnet network routes that collide with the user's local subnet. On connecting to netbird, the netbird routes should have a higher priority than the main table routes (lower priority number). For example, on connecting to tailscale, the tailscale route network creates a routing table with priority `50`, and the main table has a priority of `100`. In case of netbird, it creates a route table with priority `110` and sets the main table's priority to `100`. See the code here: https://github.com/netbirdio/netbird/blob/a5811a2d7dfd33eee331bf204201f081bbb411c9/client/internal/routemanager/systemops_linux.go#L76-L83 Currently to fix this, we need to revert to the old routing logic: ```shell $ sudo mkdir -p /etc/sysconfig $ echo 'NB_USE_LEGACY_ROUTING=true' | sudo tee -a /etc/sysconfig/netbird $ sudo systemctl restart netbird ``` **To Reproduce** Steps to reproduce the behavior: 1. Upgrade to a newer version of Netbird. 2. Check `ip route show`. It won't show the Netbird routes in the main table. 3. Check `ip route show table all`. See Netbird table with ID `7120`. 4. Check `ip rule show`. See that the main table has a higher lookup priority than the Netbird table. 5. Netbird network route fails in case the network route's subnet (eg. `192.168.0.0/16`), overlaps with the local network subnet (eg. `192.168.0.0/24`). **Expected behavior** On connecting to Netbird, the Netbird routes should have a higher lookup priority than the local subnet. **Are you using NetBird Cloud?** Self-hosted NetBird's control plane. **NetBird version** `netbird version`: `0.27.7`
saavagebueno added the bugclientroutes labels 2025-11-20 05:19:30 -05:00
saavagebueno commented 2025-11-20 05:19:31 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (May 17, 2024):

Thanks for opening this bug report. We will look into the best solution for this case and fix in the next releases.

@mlsmaycon commented on GitHub (May 17, 2024): Thanks for opening this bug report. We will look into the best solution for this case and fix in the next releases.
saavagebueno commented 2025-11-20 05:19:31 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 23, 2025):

@mlsmaycon @Thunderbottom is it still relevant or was addressed already?

@nazarewk commented on GitHub (Apr 23, 2025): @mlsmaycon @Thunderbottom is it still relevant or was addressed already?
saavagebueno commented 2025-11-20 05:19:31 -05:00
Author
Owner
Copy Link

@Thunderbottom commented on GitHub (Apr 23, 2025):

This is still relevant and needs to be addressed

@Thunderbottom commented on GitHub (Apr 23, 2025): This is still relevant and needs to be addressed
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label bug client routes
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#895
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?