[GH-ISSUE #1671] Does netbird support tcp relay(coturn)? #2946

Open
opened 2026-08-05 00:49:47 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @xiaolei0125 on GitHub (Mar 6, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1671

Describe the problem

Does netbird support tcp relay?
if I set no-udp and no-udp-relay in coturn turnserver.conf, the netbird get error

netbird status -d
Relays: 
  [stun:stunserver.stunprotocol.org:3478] is Available
  [stun:stun.freeswitch.org:3478] is Available
  [turn:turn.xx.top:3478?transport=tcp] is Unavailable, reason: allocate: Allocate error response (error 442: UDP Transport is not allowed by the TURN Server configuration)

if I set no-udp, but unset no-udp-relay in coturn turnserver.conf, the netbird status no error, but It seem that netbird client use udp to connect coturn relay :

netbird status -d
Relays: 
  [stun:stunserver.stunprotocol.org:3478] is Available
  [stun:stun.freeswitch.org:3478] is Available
  [turn:turn.xx.top:3478?transport=tcp] is Available

NetBird version

Daemon version: 0.26.2
CLI version: 0.26.2
Management: Connected to https://nb.xx.top:8443
Signal: Connected to https://nb.xx.top:8443
Relays: 
  [stun:stunserver.stunprotocol.org:3478] is Available
  [stun:stun.freeswitch.org:3478] is Available
  [turn:turn.xx.top:3478?transport=tcp] is Available
FQDN: m1.nb.iot
NetBird IP: 100.64.0.3/16
Interface type: Kernel
Quantum resistance: false
Peers count: 3/6 Connected

Maybe Related issue:
#414

Originally created by @xiaolei0125 on GitHub (Mar 6, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1671 **Describe the problem** Does netbird support tcp relay? if I set no-udp and no-udp-relay in coturn turnserver.conf, the netbird get error ``` netbird status -d Relays: [stun:stunserver.stunprotocol.org:3478] is Available [stun:stun.freeswitch.org:3478] is Available [turn:turn.xx.top:3478?transport=tcp] is Unavailable, reason: allocate: Allocate error response (error 442: UDP Transport is not allowed by the TURN Server configuration) ``` if I set no-udp, but unset no-udp-relay in coturn turnserver.conf, the netbird status no error, but It seem that netbird client use udp to connect coturn relay : ``` netbird status -d Relays: [stun:stunserver.stunprotocol.org:3478] is Available [stun:stun.freeswitch.org:3478] is Available [turn:turn.xx.top:3478?transport=tcp] is Available ``` **NetBird version** ``` Daemon version: 0.26.2 CLI version: 0.26.2 Management: Connected to https://nb.xx.top:8443 Signal: Connected to https://nb.xx.top:8443 Relays: [stun:stunserver.stunprotocol.org:3478] is Available [stun:stun.freeswitch.org:3478] is Available [turn:turn.xx.top:3478?transport=tcp] is Available FQDN: m1.nb.iot NetBird IP: 100.64.0.3/16 Interface type: Kernel Quantum resistance: false Peers count: 3/6 Connected ``` Maybe Related issue: #414
saavagebueno added the questionself-hostingcoturn labels 2026-08-05 00:49:47 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#2946