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

Option to Mark Peers as Ineligible for Routing #973

New Issue
Closed
opened 2025-11-20 05:20:52 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 05:20:52 -05:00
Owner
Copy Link

Originally created by @marcportabellaclotet-mt on GitHub (Jun 13, 2024).

Description:

I would like to request an enhancement that allows marking a peer as ineligible to be used as a routing peer. This feature would improve security by ensuring that certain peers cannot be used to route traffic, thereby preventing unauthorized network exploration.

Use Case:
Currently, all peers connected to NetBird can potentially be used as routing peers. This poses a security risk where an administrator might intentionally add a route to connect and explore another peer's network, which may not be desirable for some users.

Proposed Solution:
Introduce an option in the peer configuration settings that allows administrators to mark a peer as "ineligible for routing". When this option is enabled for a peer:

  • The peer cannot be used as an intermediary to route traffic for other peers.
  • This setting should be configurable at the time of peer creation and not adjustable later by administrators.

Benefits:

  • Enhances security by providing control over which peers can be used for routing.
  • Protects sensitive networks from unauthorized access and exploration.
Originally created by @marcportabellaclotet-mt on GitHub (Jun 13, 2024). **Description:** I would like to request an enhancement that allows marking a peer as ineligible to be used as a routing peer. This feature would improve security by ensuring that certain peers cannot be used to route traffic, thereby preventing unauthorized network exploration. **Use Case:** Currently, all peers connected to NetBird can potentially be used as routing peers. This poses a security risk where an administrator might intentionally add a route to connect and explore another peer's network, which may not be desirable for some users. **Proposed Solution:** Introduce an option in the peer configuration settings that allows administrators to mark a peer as "ineligible for routing". When this option is enabled for a peer: - The peer cannot be used as an intermediary to route traffic for other peers. - This setting should be configurable at the time of peer creation and not adjustable later by administrators. **Benefits:** - Enhances security by providing control over which peers can be used for routing. - Protects sensitive networks from unauthorized access and exploration.
saavagebueno added the feature-request label 2025-11-20 05:20:52 -05:00
saavagebueno commented 2025-11-20 05:20:52 -05:00
Author
Owner
Copy Link

@marcportabellaclotet-mt commented on GitHub (Jul 1, 2024):

Alternatively, instead of marking peers as ineligible for routing, it would be beneficial to use the same approach as for allowing SSH connections. To make a peer eligible for routing, the user should enable this feature in the client. This would help generate trust when third parties use the Netbird client, as some may be concerned that their network could be accessed if the Netbird admin configures routing through their peers.

@marcportabellaclotet-mt commented on GitHub (Jul 1, 2024): Alternatively, instead of marking peers as ineligible for routing, it would be beneficial to use the same approach as for allowing SSH connections. To make a peer eligible for routing, the user should enable this feature in the client. This would help generate trust when third parties use the Netbird client, as some may be concerned that their network could be accessed if the Netbird admin configures routing through their peers.
saavagebueno commented 2025-11-20 05:20:53 -05:00
Author
Owner
Copy Link

@marcportabellaclotet-mt commented on GitHub (Jan 21, 2025):

Closing and this feature introduces with version 0.36.0.
Thanks team

@marcportabellaclotet-mt commented on GitHub (Jan 21, 2025): Closing and this feature introduces with version 0.36.0. Thanks team
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
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#973
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?