SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-07-03 04:32:27 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Exit Nodes are enabled by default #991

New Issue
Open
opened 2025-11-20 05:21:16 -05:00 by saavagebueno · 7 comments
saavagebueno commented 2025-11-20 05:21:16 -05:00
Owner
Copy Link

Originally created by @W1BTR on GitHub (Jun 19, 2024).

Describe the problem

If exit nodes are available, upon restarting the netbird client on PC, it automatically enables it.

To Reproduce

Steps to reproduce the behavior:

  1. Sign into netbird on Windows
  2. Check "Network Routes"

Expected behavior

Ideally, it saves whatever status it had on last run.

Are you using NetBird Cloud?

I self-host NetBird's control plane.

NetBird version

0.27.10

Originally created by @W1BTR on GitHub (Jun 19, 2024). **Describe the problem** If exit nodes are available, upon restarting the netbird client on PC, it automatically enables it. **To Reproduce** Steps to reproduce the behavior: 1. Sign into netbird on Windows 2. Check "Network Routes" **Expected behavior** Ideally, it saves whatever status it had on last run. **Are you using NetBird Cloud?** I self-host NetBird's control plane. **NetBird version** `0.27.10`
saavagebueno added the feature-requestroutes labels 2025-11-20 05:21:16 -05:00
saavagebueno commented 2025-11-20 05:21:16 -05:00
Author
Owner
Copy Link

@W1BTR commented on GitHub (Jun 19, 2024):

Seems like exit nodes are also applying by default to devices in an exit node group on linux. There is an exit node given to the "All" group. When installing netbird on a server, all the services went down as it was forced to use the exit node by default.

Ideally this is something we can enable and disable on the fly. I'd like a handful of exit nodes available to users, without being enabled by defaults

@W1BTR commented on GitHub (Jun 19, 2024): Seems like exit nodes are also applying by default to devices in an exit node group on linux. There is an exit node given to the "All" group. When installing netbird on a server, all the services went down as it was forced to use the exit node by default. Ideally this is something we can enable and disable on the fly. I'd like a handful of exit nodes available to users, without being enabled by defaults
saavagebueno commented 2025-11-20 05:21:17 -05:00
Author
Owner
Copy Link

@pascal-fischer commented on GitHub (Jun 20, 2024):

Hi @W1BTR,
the first version of exit nodes is fully managed from the admin dashboard. We already planned on making the client remember if a route was disabled by a user or not. With that we will evaluate if and how to maybe mark them already on management to not be assigned by default.

@pascal-fischer commented on GitHub (Jun 20, 2024): Hi @W1BTR, the first version of exit nodes is fully managed from the admin dashboard. We already planned on making the client remember if a route was disabled by a user or not. With that we will evaluate if and how to maybe mark them already on management to not be assigned by default.
saavagebueno commented 2025-11-20 05:21:17 -05:00
Author
Owner
Copy Link

@W1BTR commented on GitHub (Jun 21, 2024):

Hi @W1BTR, the first version of exit nodes is fully managed from the admin dashboard. We already planned on making the client remember if a route was disabled by a user or not. With that we will evaluate if and how to maybe mark them already on management to not be assigned by default.

Makes sense. The client remembering is definitely a big thing, glad it's being taken care of. Having an option to override this on the dashboard does sound powerful, allowing the admin to move servers and devices between virtual networks! Super cool!

@W1BTR commented on GitHub (Jun 21, 2024): > Hi @W1BTR, the first version of exit nodes is fully managed from the admin dashboard. We already planned on making the client remember if a route was disabled by a user or not. With that we will evaluate if and how to maybe mark them already on management to not be assigned by default. Makes sense. The client remembering is definitely a big thing, glad it's being taken care of. Having an option to override this on the dashboard does sound powerful, allowing the admin to move servers and devices between virtual networks! Super cool!
saavagebueno commented 2025-11-20 05:21:17 -05:00
Author
Owner
Copy Link

@W1BTR commented on GitHub (Jun 27, 2024):

The amount of times I think my networking is broken or there's a lot of lag in the network at work before I realize netbird is just running is quite often 🤣

Although Im not sure why the connection drops every 20 seconds when using one of my exit nodes. I need to test if it always has this issue or just with this node.

@W1BTR commented on GitHub (Jun 27, 2024): The amount of times I think my networking is broken or there's a lot of lag in the network at work before I realize netbird is just running is quite often 🤣 Although Im not sure why the connection drops every 20 seconds when using one of my exit nodes. I need to test if it always has this issue or just with this node.
saavagebueno commented 2025-11-20 05:21:17 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jun 27, 2024):

Hey @W1BTR , can you leave your comments here: https://github.com/netbirdio/netbird/issues/2193

We will be updating the behavior and would be great to collect all in one place.

@mlsmaycon commented on GitHub (Jun 27, 2024): Hey @W1BTR , can you leave your comments here: https://github.com/netbirdio/netbird/issues/2193 We will be updating the behavior and would be great to collect all in one place.
saavagebueno commented 2025-11-20 05:21:17 -05:00
Author
Owner
Copy Link

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

is it still relevant after introduction of Exit Node selection mechanism?

@nazarewk commented on GitHub (Apr 23, 2025): is it still relevant after introduction of Exit Node selection mechanism?
saavagebueno commented 2025-11-20 05:21:17 -05:00
Author
Owner
Copy Link

@anarh1st47 commented on GitHub (Aug 17, 2025):

This is still works the same

@anarh1st47 commented on GitHub (Aug 17, 2025): This is still works the same
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 feature-request 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#991
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?