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

Difference between relay and coturn? #2256

New Issue
Open
opened 2025-11-20 07:06:36 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 07:06:36 -05:00
Owner
Copy Link

Originally created by @qiangxinglin on GitHub (Sep 9, 2025).

Hi team,

I have following config on my spare server (not the one hosted netbird dashboard and api).

services:
  coturn:
    image: coturn/coturn:latest
    volumes:
      - ./turnserver.conf:/etc/turnserver.conf:ro
    network_mode: host
    command:
      - -c /etc/turnserver.conf

  relay:
    image: netbirdio/relay:latest
    environment:
      - NB_LOG_LEVEL=info
      - NB_LISTEN_ADDRESS=:33080
      - NB_EXPOSED_ADDRESS=rel://SPARE_IP:33080
      - NB_AUTH_SECRET=Wl......
    ports:
      - 33080:33080

I'm wondering which service should I deploy based on the geolocation of the spare server.
Based on September newsletter, it seems that coturn is outdated and only the relay service rels://DOMAIN:PORT should be use.

Also, when I set multiple Relay.Addresses entries in main server's management.json

    "Relay": {
        "Addresses": [
            "rels://netbird.MAIN.com:443/relay",
            "rel://SPARE_IP:33080"
        ],
        "CredentialsTTL": "24h0m0s",
        "Secret": "Wl......"
    },

The netbird status -d only show one relay:

Relays:
  [stun:netbird.MAIN.com:3478] is Available
  [turn:netbird.MAIN.com:3478?transport=udp] is Available
  [rel://SPARE_IP:33080] is Available            # <-- Only the second entry listed here
Originally created by @qiangxinglin on GitHub (Sep 9, 2025). Hi team, I have following config on my spare server (not the one hosted netbird dashboard and api). ``` services: coturn: image: coturn/coturn:latest volumes: - ./turnserver.conf:/etc/turnserver.conf:ro network_mode: host command: - -c /etc/turnserver.conf relay: image: netbirdio/relay:latest environment: - NB_LOG_LEVEL=info - NB_LISTEN_ADDRESS=:33080 - NB_EXPOSED_ADDRESS=rel://SPARE_IP:33080 - NB_AUTH_SECRET=Wl...... ports: - 33080:33080 ``` I'm wondering which service should I deploy based on the geolocation of the spare server. Based on [September newsletter](https://netbird.io/knowledge-hub/september-newsletter), it seems that `coturn` is outdated and only the `relay` service `rels://DOMAIN:PORT` should be use. Also, when I set multiple `Relay.Addresses` entries in main server's `management.json` ``` "Relay": { "Addresses": [ "rels://netbird.MAIN.com:443/relay", "rel://SPARE_IP:33080" ], "CredentialsTTL": "24h0m0s", "Secret": "Wl......" }, ``` The `netbird status -d` only show one relay: ``` Relays: [stun:netbird.MAIN.com:3478] is Available [turn:netbird.MAIN.com:3478?transport=udp] is Available [rel://SPARE_IP:33080] is Available # <-- Only the second entry listed here ```
saavagebueno commented 2025-11-20 07:06:37 -05:00
Author
Owner
Copy Link

@1nerdyguy commented on GitHub (Sep 9, 2025):

I'm curious on this as well. To my understanding, the long-term goal is to have the Relay do all the work, but at the moment CoTurn is still required for...some reason.

As for the single listing, I believe that's because it's showing which one is responding fastest. If you were to, for example, shut down the spare_ip one, I bet status -d would change

@1nerdyguy commented on GitHub (Sep 9, 2025): I'm curious on this as well. To my understanding, the long-term goal is to have the Relay do all the work, but at the moment CoTurn is still required for...some reason. As for the single listing, I believe that's because it's showing which one is responding fastest. If you were to, for example, shut down the spare_ip one, I bet status -d would change
saavagebueno commented 2025-11-20 07:06:37 -05:00
Author
Owner
Copy Link

@saule1508 commented on GitHub (Sep 11, 2025):

I think coturn is still needed for the STUN functionality, which is a very lightweight functionality that can be done via public stun servers, google for example (there is no authentication for stun as the cost of authentification is higher than the cost of providing the service).
We have two netbird networks, one with relay and one with coturn, both work fine

@saule1508 commented on GitHub (Sep 11, 2025): I think coturn is still needed for the STUN functionality, which is a very lightweight functionality that can be done via public stun servers, google for example (there is no authentication for stun as the cost of authentification is higher than the cost of providing the service). We have two netbird networks, one with relay and one with coturn, both work fine
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#2256
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?