SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-08-04 19:55:09 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Client Issue - Routes now apply immediately, not only on peer connection. #3907 causing Exit Node Traffic Failure #1973

New Issue
Open
opened 2025-11-20 06:10:31 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 06:10:31 -05:00
Owner
Copy Link

Originally created by @laserguy2020 on GitHub (Jun 17, 2025).

Describe the problem

When instituting Exit Nodes on Mac OS since 0.46.0 client we now see Netbird connect but then all traffic stops if the Exit Node is configured. It looks like even netbird client traffic is being attempted to be passed over the Netbird Exit Node. This is even worse when multiple exit nodes are configured.

To Reproduce

Steps to reproduce the behavior:

  1. Configure Netbird Exit Node with 0.0.0.0/0 and weight 9999
  2. Connect MacOS Client
  3. Connects
  4. All Traffic Stops because netbird cannot talk to the Exit Node because of a cyclical route issue

Expected behavior

Traffic outside Netbird Communication to 0.0.0.0/0 should pass through the exit node.

Are you using NetBird Cloud?

Self Hosted and Cloud

NetBird version

0.47.0 - Management
0.47.2 - Client

Is any other VPN software installed?

No

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 @laserguy2020 on GitHub (Jun 17, 2025). **Describe the problem** When instituting Exit Nodes on Mac OS since 0.46.0 client we now see Netbird connect but then all traffic stops if the Exit Node is configured. It looks like even netbird client traffic is being attempted to be passed over the Netbird Exit Node. This is even worse when multiple exit nodes are configured. **To Reproduce** Steps to reproduce the behavior: 1. Configure Netbird Exit Node with 0.0.0.0/0 and weight 9999 2. Connect MacOS Client 3. Connects 4. All Traffic Stops because netbird cannot talk to the Exit Node because of a cyclical route issue **Expected behavior** Traffic outside Netbird Communication to 0.0.0.0/0 should pass through the exit node. **Are you using NetBird Cloud?** Self Hosted and Cloud **NetBird version** `0.47.0` - Management `0.47.2` - Client **Is any other VPN software installed?** No **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 2025-11-20 06:10:31 -05:00
saavagebueno commented 2025-11-20 06:10:32 -05:00
Author
Owner
Copy Link

@lixmal commented on GitHub (Jun 17, 2025):

Can you provide a debug bundle please? I'm unable to reproduce the issue

@lixmal commented on GitHub (Jun 17, 2025): Can you provide a debug bundle please? I'm unable to reproduce the issue
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 triage-needed
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#1973
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?