[GH-ISSUE #4768] When the exit node is active, the default route is not fully effective #9809

Closed
opened 2026-08-05 01:23:33 -04:00 by saavagebueno · 3 comments
Owner

Originally created by @mertcangokgoz on GitHub (Nov 9, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4768

Describe the problem

I'm trying to replace the VPN with Netbird, but I encountered a very strange situation noticed that when trying to access some routes, the traffic is not going through the VPN. I haven't made any settings yet, I added the networks and added 2 exit nodes.

I configured one only for Netbird admins to use, the other one will be used by users.

To Reproduce

Steps to reproduce the behavior:

  1. Go to netbird client and click connect
  2. login with sso
  3. Trace tests are performed on some routes.

Expected behavior

I expect all traffic to go through the VPN, especially if an exit node is set.

Are you using NetBird Cloud?

im using self hosted netbird

NetBird version

0.59.12

Is any other VPN software installed?

Yes, WireGuard is installed on my computer (but I completely shut it down while doing these tests).

Debug output

NA

Screenshots

As you can see in the screenshots, the default route is not completely overridden by the VPN - the old gateway is still active. Normally we should see both of them in the default route.

The image below was taken when no VPN was active.

Image

The image below was taken when the VPN was active.

Image

This image was taken when only WireGuard Client was active.

Image

When VPN is actively used through the Netbird client, shouldn't there be an output similar to WireGuard client output? Why is it routing to my home router's gateway IP address?

Have you tried these troubleshooting steps?

  • Reviewed client troubleshooting (if applicable)
  • Checked for newer NetBird versions
  • Searched for similar issues on GitHub (including closed ones)
  • Restarted the NetBird client
  • Disabled other VPN software
  • Checked firewall settings
Originally created by @mertcangokgoz on GitHub (Nov 9, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4768 **Describe the problem** I'm trying to replace the VPN with Netbird, but I encountered a very strange situation noticed that when trying to access some routes, the traffic is not going through the VPN. I haven't made any settings yet, I added the networks and added 2 exit nodes. I configured one only for Netbird admins to use, the other one will be used by users. **To Reproduce** Steps to reproduce the behavior: 1. Go to netbird client and click connect 2. login with sso 3. Trace tests are performed on some routes. **Expected behavior** I expect all traffic to go through the VPN, especially if an exit node is set. **Are you using NetBird Cloud?** im using self hosted netbird **NetBird version** 0.59.12 **Is any other VPN software installed?** Yes, WireGuard is installed on my computer (but I completely shut it down while doing these tests). **Debug output** NA **Screenshots** As you can see in the screenshots, the default route is not completely overridden by the VPN - the old gateway is still active. Normally we should see both of them in the default route. The image below was taken when no VPN was active. <img width="625" height="376" alt="Image" src="https://github.com/user-attachments/assets/bcf5534d-f140-4cc0-a9cf-32d7ac9a55ce" /> The image below was taken when the VPN was active. <img width="656" height="827" alt="Image" src="https://github.com/user-attachments/assets/68997a37-4b08-4c6c-b7c1-9618b814ca6d" /> This image was taken when only WireGuard Client was active. <img width="594" height="664" alt="Image" src="https://github.com/user-attachments/assets/cce09de4-47c6-4d5c-8cc3-3e5b1a30bcfd" /> When VPN is actively used through the Netbird client, shouldn't there be an output similar to WireGuard client output? Why is it routing to my home router's gateway IP address? **Have you tried these troubleshooting steps?** - [x] Reviewed [client troubleshooting](https://docs.netbird.io/how-to/troubleshooting-client) (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
saavagebueno added the triage-needed label 2026-08-05 01:23:33 -04:00
Author
Owner

@mertcangokgoz commented on GitHub (Nov 14, 2025):

Isn’t there anyone about this issue?

<!-- gh-comment-id:3531833837 --> @mertcangokgoz commented on GitHub (Nov 14, 2025): Isn’t there anyone about this issue?
Author
Owner

@amirhmoradi commented on GitHub (Feb 6, 2026):

I also face the same issue.
Installed netbird on mac, chose an exit node, added the route in netbird. Then connected the mac to netbrid via official client app, the proper exit node is shown and selected, but the public ip of my mac is no the one of the exit node.

<!-- gh-comment-id:3862854445 --> @amirhmoradi commented on GitHub (Feb 6, 2026): I also face the same issue. Installed netbird on mac, chose an exit node, added the route in netbird. Then connected the mac to netbrid via official client app, the proper exit node is shown and selected, but the public ip of my mac is no the one of the exit node.
Author
Owner

@mertcangokgoz commented on GitHub (May 16, 2026):

if the Netbird version is >0.70, this issue doesn't happen anymore.

<!-- gh-comment-id:4466509896 --> @mertcangokgoz commented on GitHub (May 16, 2026): if the Netbird version is >0.70, this issue doesn't happen anymore.
Sign in to join this conversation.
No Label triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#9809