SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-08-01 18:38:42 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Ability to specify port used by peer #1218

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

Originally created by @t3cneo on GitHub (Sep 5, 2024).

Is your feature request related to a problem? Please describe.
When using netbird behind a gateway which also have a wireguard server set up on default 51820 port, netbird peer connexions are difficult if possible at all.

At home I have my router set up as a Wireguard server (not netbird, plain wireguard) to be able to remote in or remote exit from home.
I noticed I randomly couldn't reach some netbird peers on my laptop when at home and the command netbird status -d helped me remember peers are trying to handshake my pubic_ip:51820 which probably makes my gateway confused about it is supposed to handle the handshake or pass it to my laptop.
I just changed my gateway's wireguard server to listen to 51821 and I can now quickly connect to every availble peers.

I happened to visit a company the other day that probably also have a wireguard server listening on the default port 51820, I couldn't reach any netbird peers from this location and obviously could not ask those guys to change their wireguard setup...

Describe the solution you'd like
It'd be great if we could specify the port used by a peer from the UI, or have some kind of port range that a peer would try after some kind of connect timeout.

Describe alternatives you've considered
Changing the gateway wireguard server listening port is a workaround but not always under my will...

Originally created by @t3cneo on GitHub (Sep 5, 2024). **Is your feature request related to a problem? Please describe.** When using netbird behind a gateway which also have a wireguard server set up on default 51820 port, netbird peer connexions are difficult if possible at all. At home I have my router set up as a Wireguard server (not netbird, plain wireguard) to be able to remote in or remote exit from home. I noticed I randomly couldn't reach some netbird peers on my laptop when at home and the command `netbird status -d` helped me remember peers are trying to handshake my pubic_ip:51820 which probably makes my gateway confused about it is supposed to handle the handshake or pass it to my laptop. I just changed my gateway's wireguard server to listen to 51821 and I can now quickly connect to every availble peers. I happened to visit a company the other day that probably also have a wireguard server listening on the default port 51820, I couldn't reach any netbird peers from this location and obviously could not ask those guys to change their wireguard setup... **Describe the solution you'd like** It'd be great if we could specify the port used by a peer from the UI, or have some kind of port range that a peer would try after some kind of connect timeout. **Describe alternatives you've considered** Changing the gateway wireguard server listening port is a workaround but not always under my will...
saavagebueno added the feature-request label 2025-11-20 05:26:11 -05:00
saavagebueno commented 2025-11-20 05:26:12 -05:00
Author
Owner
Copy Link

@micmejia commented on GitHub (Sep 12, 2024):

The netbird cli has a wireguard-port, example:

netbird down && netbird up --allow-server-ssh --wireguard-port 51821
@micmejia commented on GitHub (Sep 12, 2024): The netbird cli has a `wireguard-port`, example: ``` netbird down && netbird up --allow-server-ssh --wireguard-port 51821 ```
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#1218
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?