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

UDP 49152-65535 #131

New Issue
Closed
opened 2025-11-20 05:06:40 -05:00 by saavagebueno · 7 comments
saavagebueno commented 2025-11-20 05:06:40 -05:00
Owner
Copy Link

Originally created by @chmis8000 on GitHub (Mar 21, 2022).

UDP 49152-65535
Any suggestions on the configuration of the server and client?

Originally created by @chmis8000 on GitHub (Mar 21, 2022). UDP 49152-65535 Any suggestions on the configuration of the server and client?
saavagebueno commented 2025-11-20 05:06:41 -05:00
Author
Owner
Copy Link

@shatoboar commented on GitHub (Mar 21, 2022):

Hey @chmis8000, thanks for taking the time to create the issue. Could you specify your problem a little bit more?

@shatoboar commented on GitHub (Mar 21, 2022): Hey @chmis8000, thanks for taking the time to create the issue. Could you specify your problem a little bit more?
saavagebueno commented 2025-11-20 05:06:41 -05:00
Author
Owner
Copy Link

@chmis8000 commented on GitHub (Mar 21, 2022):

@shatoboar
This documentation https://github.com/wiretrustee/wiretrustee/blob/main/docs/self-hosting.md mentions it.
"Coturn is used for relay using the STUN/TURN protocols. It requires a listening port, UDP 3478, and range of ports,UDP 49152-65535, for dynamic relay connections."

@chmis8000 commented on GitHub (Mar 21, 2022): @shatoboar This documentation https://github.com/wiretrustee/wiretrustee/blob/main/docs/self-hosting.md mentions it. "Coturn is used for relay using the STUN/TURN protocols. It requires a listening port, UDP 3478, and range of ports,UDP 49152-65535, for dynamic relay connections."
saavagebueno commented 2025-11-20 05:06:41 -05:00
Author
Owner
Copy Link

@shatoboar commented on GitHub (Mar 21, 2022):

Hey @chmis8000 ,
If you are using the hosted version, there is no need to configure anything on the client side. If you are trying to host Wiretrustee yourself, you will need to configure the port ranges 76db9afa11/infrastructure_files/setup.env (L34) which default to 49152-65535.
You probably will need to also set some rules in your firewall to allow connections through these ranges.
We will update the Docs to make this more clearer :)

@shatoboar commented on GitHub (Mar 21, 2022): Hey @chmis8000 , If you are using the hosted version, there is no need to configure anything on the client side. If you are trying to host Wiretrustee yourself, you will need to configure the port ranges https://github.com/wiretrustee/wiretrustee/blob/76db9afa11853ddc7a9500019d402a685468a8f9/infrastructure_files/setup.env#L34 which default to 49152-65535. You probably will need to also set some rules in your firewall to allow connections through these ranges. We will update the Docs to make this more clearer :)
saavagebueno commented 2025-11-20 05:06:41 -05:00
Author
Owner
Copy Link

@chmis8000 commented on GitHub (Mar 23, 2022):

I think two clients cannot p2p,
but one machine can be configured with port mapping. Is it possible to increase the configuration so as to try to p2p as much as possible?

@chmis8000 commented on GitHub (Mar 23, 2022): I think two clients cannot p2p, but one machine can be configured with port mapping. Is it possible to increase the configuration so as to try to p2p as much as possible?
saavagebueno commented 2025-11-20 05:06:41 -05:00
Author
Owner
Copy Link

@shatoboar commented on GitHub (Mar 24, 2022):

Hi sorry for the delayed answer.
I am not exactly sure what you mean, but peers continuously try to establish a peer-to-peer connection. You don't need to increase the configuration in order for this to happen.
Why is it that you think that the two clients are unable to connect p2p?

@shatoboar commented on GitHub (Mar 24, 2022): Hi sorry for the delayed answer. I am not exactly sure what you mean, but peers continuously try to establish a peer-to-peer connection. You don't need to increase the configuration in order for this to happen. Why is it that you think that the two clients are unable to connect p2p?
saavagebueno commented 2025-11-20 05:06:42 -05:00
Author
Owner
Copy Link

@chmis8000 commented on GitHub (Mar 24, 2022):

Using this tool, detect the NAT type:
https://github.com/HMBSbige/NatTypeTester/releases/
1 peer： Symmetric
2 peer： PortRestrictedCone
I think Symmetric should be the reason why P2P is not possible.

@chmis8000 commented on GitHub (Mar 24, 2022): Using this tool, detect the NAT type: https://github.com/HMBSbige/NatTypeTester/releases/ 1 peer： Symmetric 2 peer： PortRestrictedCone I think Symmetric should be the reason why P2P is not possible.
saavagebueno commented 2025-11-20 05:06:42 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Apr 4, 2022):

Hello @chmis8000, you are correct, the peer with Symmetric NAT is causing this issue.

we rely on ICE protocol for NAT discovery, it evaluates all types of connections and only uses the relay server in case no direct connection is possible. Also, you may be facing some performance issues due to the distance to our relay servers, currently, they are hosted in Finland, but we have an estimate to expand their deployment around the globe in May.

@mlsmaycon commented on GitHub (Apr 4, 2022): Hello @chmis8000, you are correct, the peer with Symmetric NAT is causing this issue. we rely on [ICE protocol](https://datatracker.ietf.org/doc/html/rfc8445) for NAT discovery, it evaluates all types of connections and only uses the relay server in case no direct connection is possible. Also, you may be facing some performance issues due to the distance to our relay servers, currently, they are hosted in Finland, but we have an estimate to expand their deployment around the globe in May.
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#131
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?