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

Allow grouping relay servers in the dashboard #2435

New Issue
Open
opened 2025-11-20 07:09:47 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 07:09:47 -05:00
Owner
Copy Link

Originally created by @jakeslee on GitHub (Nov 3, 2025).

Is your feature request related to a problem? Please describe.

P2P/UDP in my network was be limited, so some peers must to be communicated via TCP relay and turning on NB_FORCE_RELAY, otherwise bandwidth limited to 1Mbps.

For this case, I deployed some relay nodes in more than one region. For example, a peer deployed in Japen with a local relay server, some peers deployed with local relay server in mainland China.

As I know, when peers starts, managemant server pushes the configured relay server list to the peers. The peer concurrently connects to the relay server, and takes the first connected relay server as peer relay server.

The workflow works fine in most situations, but when network delays the peers in China may take Japen relay server. It causes that another peers in China connect to the peer with huge latency.

Describe the solution you'd like

If dashboard supports configuring, grouping and peers visible controlling relay servers, I can limit the peers whiches can only take local region relay server(only announced relay server, not affect cross-region connection).

Describe alternatives you've considered

I modified netbird client codes, add NB_FORCE_RELAY_ADDR env to overwrite the relay servers from management server.

The solution is tricky and hard to maintain, so hope that netbird supports more powerful features to maintain relay servers(such as registering, grouping, access controlling, priority, etc.).

Originally created by @jakeslee on GitHub (Nov 3, 2025). **Is your feature request related to a problem? Please describe.** P2P/UDP in my network was be limited, so some peers must to be communicated via TCP relay and turning on `NB_FORCE_RELAY`, otherwise bandwidth limited to 1Mbps. For this case, I deployed some relay nodes in more than one region. For example, a peer deployed in Japen with a local relay server, some peers deployed with local relay server in mainland China. As I know, when peers starts, managemant server pushes the configured relay server list to the peers. The peer concurrently connects to the relay server, and takes the first connected relay server as peer relay server. The workflow works fine in most situations, but when network delays the peers in China may take Japen relay server. It causes that another peers in China connect to the peer with huge latency. **Describe the solution you'd like** If dashboard supports configuring, grouping and peers visible controlling relay servers, I can limit the peers whiches can only take local region relay server(only announced relay server, not affect cross-region connection). **Describe alternatives you've considered** I modified netbird client codes, add `NB_FORCE_RELAY_ADDR` env to overwrite the relay servers from management server. The solution is tricky and hard to maintain, so hope that netbird supports more powerful features to maintain relay servers(such as registering, grouping, access controlling, priority, etc.).
saavagebueno added the feature-request label 2025-11-20 07:09:47 -05:00
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#2435
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?