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

Peer metadata #208

New Issue
Closed
opened 2025-11-20 05:08:02 -05:00 by saavagebueno · 5 comments
saavagebueno commented 2025-11-20 05:08:02 -05:00
Owner
Copy Link

Originally created by @rgl on GitHub (Oct 21, 2022).

Does it make sense to be able to set/attach metadata (e.g. an ad-hoc json document) to a peer?

That could be used to set description/labels/tags and other ad-hoc data to aid other humans/systems.

Originally created by @rgl on GitHub (Oct 21, 2022). Does it make sense to be able to set/attach metadata (e.g. an ad-hoc json document) to a peer? That could be used to set description/labels/tags and other ad-hoc data to aid other humans/systems.
saavagebueno commented 2025-11-20 05:08:03 -05:00
Author
Owner
Copy Link

@braginini commented on GitHub (Oct 21, 2022):

hey @rgl

What is the use case you have in mind for that?
What do you think would be the best way to set the metadata - on startup or via cmd?

@braginini commented on GitHub (Oct 21, 2022): hey @rgl What is the use case you have in mind for that? What do you think would be the best way to set the metadata - on startup or via cmd?
saavagebueno commented 2025-11-20 05:08:03 -05:00
Author
Owner
Copy Link

@rgl commented on GitHub (Oct 21, 2022):

I do not have a use-case. Just had a feeling that somehow having peer metadata might help the administrator/user/other-system identify the peers. Mainly, because I've created several test VMs, but did not change their hostname, so I ended up with a bunch of peers that appeared to be the same from a glance at the UI, and wondered whether a metadata/description would have helped; but unfortunately, I didn't apply much though into it and I'm now realizing that this is not be a good enough reason to have metadata.

In retrospect, sorry for wasting your time...

@rgl commented on GitHub (Oct 21, 2022): I do not have a use-case. Just had a feeling that somehow having peer metadata might help the administrator/user/other-system identify the peers. Mainly, because I've created several test VMs, but did not change their hostname, so I ended up with a bunch of peers that appeared to be the same from a glance at the UI, and wondered whether a metadata/description would have helped; but unfortunately, I didn't apply much though into it and I'm now realizing that this is not be a good enough reason to have metadata. In retrospect, sorry for wasting your time...
saavagebueno commented 2025-11-20 05:08:03 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Oct 21, 2022):

Thanks @rgl for the suggestion.

According to your use case, it seems like you had a common issue, but there is an option to update a peer's name in the UI, see screenshot below:
image

We also push the system hostname if it is ever changed locally, you can see that expanding the peers system info:
image

Let us know if that would help you identify your peers.

@mlsmaycon commented on GitHub (Oct 21, 2022): Thanks @rgl for the suggestion. According to your use case, it seems like you had a common issue, but there is an option to update a peer's name in the UI, see screenshot below: <img width="169" alt="image" src="https://user-images.githubusercontent.com/7747744/197283500-73b51f88-d199-41f5-80bb-c0d2fa3dfbbf.png"> We also push the system hostname if it is ever changed locally, you can see that expanding the peers system info: <img width="340" alt="image" src="https://user-images.githubusercontent.com/7747744/197283621-166c35b2-97a1-4b76-9805-3433be8b5337.png"> Let us know if that would help you identify your peers.
saavagebueno commented 2025-11-20 05:08:03 -05:00
Author
Owner
Copy Link

@braginini commented on GitHub (Oct 22, 2022):

@rgl
You might also use setup keys or user tagging system. You could tag a setup key and use it to enroll machines. The tag will automatically apply to these machines.
https://netbird.io/docs/overview/setup-keys#peer-auto-grouping

@braginini commented on GitHub (Oct 22, 2022): @rgl You might also use setup keys or user tagging system. You could tag a setup key and use it to enroll machines. The tag will automatically apply to these machines. https://netbird.io/docs/overview/setup-keys#peer-auto-grouping
saavagebueno commented 2025-11-20 05:08:03 -05:00
Author
Owner
Copy Link

@rgl commented on GitHub (Oct 22, 2022):

Thank you for the pointers! I think using a unique setup key per peer will allow me to uniquely identity the peer. But maybe what I'm missing is a way to manage the peer IP address(es) (akin to DHCP, where we can configure static IP addresses for specific MACs, and let the system dynamically assign addresses to unknown MACs).

@rgl commented on GitHub (Oct 22, 2022): Thank you for the pointers! I think using a unique setup key per peer will allow me to uniquely identity the peer. But maybe what I'm missing is a way to manage the peer IP address(es) (akin to DHCP, where we can configure static IP addresses for specific MACs, and let the system dynamically assign addresses to unknown MACs).
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
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#208
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?