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

Allow hiding specific peers from Netbird Status #314

New Issue
Closed
opened 2025-11-20 05:09:28 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 05:09:28 -05:00
Owner
Copy Link

Originally created by @Thunderbottom on GitHub (Apr 17, 2023).

Is your feature request related to a problem? Please describe.
Currently, Netbird ACLs creates a two-way connection, meaning the source and destination can both access each other. This also means that the devices in the destination groups can view the source devices as peers when netbird status -d is executed.

As an example, let's say we have a group of administrator peers with admin-access attached to it, and an ACL policy that defines the rule admin-access <-> All. So while all devices with admin-access should be able to see all devices as peers, this also means that All devices will be able to see admin-access devices as peers in netbird status -d.

Not only does this clutter the peers list with devices, this particularly is an issue in case where the admin-access peers are end-user devices, exposing the status of all administrators to all devices connected to Netbird.

Describe the solution you'd like
Allow hiding peer status from netbird status -d. Maybe a toggle called Hide Status, or a section that allows specific peer tags to not show up in peer status.

Originally created by @Thunderbottom on GitHub (Apr 17, 2023). **Is your feature request related to a problem? Please describe.** Currently, Netbird ACLs creates a two-way connection, meaning the source and destination can both access each other. This also means that the devices in the destination groups can view the source devices as `peers` when `netbird status -d` is executed. As an example, let's say we have a group of administrator peers with `admin-access` attached to it, and an ACL policy that defines the rule `admin-access <-> All`. So while all devices with `admin-access` should be able to see all devices as peers, this also means that `All` devices will be able to see `admin-access` devices as peers in `netbird status -d`. Not only does this clutter the peers list with devices, this particularly is an issue in case where the `admin-access` peers are end-user devices, exposing the status of all administrators to all devices connected to Netbird. **Describe the solution you'd like** Allow hiding peer status from `netbird status -d`. Maybe a toggle called `Hide Status`, or a section that allows specific peer tags to not show up in peer status.
saavagebueno added the feature-request label 2025-11-20 05:09:28 -05:00
saavagebueno commented 2025-11-20 05:09:29 -05:00
Author
Owner
Copy Link

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

I am closing this as "not planned" because this is inherent to how NetBird (and other mesh networks) operate: you cannot have a one-way connectivity without first... establishing a connectivity with the other Peer and then denying incoming packets on one end.

Especially considering netbird status -d is a primary diagnostics tool, I think this will be better handled by the other 2 linked feature requests.

@nazarewk commented on GitHub (Apr 17, 2025): I am closing this as "not planned" because this is inherent to how NetBird (and other mesh networks) operate: you cannot have a one-way connectivity without first... establishing a connectivity with the other Peer and then denying incoming packets on one end. Especially considering `netbird status -d` is a primary diagnostics tool, I think this will be better handled by the other 2 linked feature requests.
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#314
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?