From a3e88705304c1a9b40df762509cdd00e39f5d77e Mon Sep 17 00:00:00 2001 From: YapWC <34093361+YapWC@users.noreply.github.com> Date: Fri, 25 Apr 2025 03:02:58 +0800 Subject: [PATCH] Update how-netbird-works.mdx (#303) Added New Relay Service with Websocket --- src/pages/about-netbird/how-netbird-works.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/pages/about-netbird/how-netbird-works.mdx b/src/pages/about-netbird/how-netbird-works.mdx index e1d22f33..b5079b11 100644 --- a/src/pages/about-netbird/how-netbird-works.mdx +++ b/src/pages/about-netbird/how-netbird-works.mdx @@ -113,8 +113,7 @@ It runs in the cloud NetBird-managed and can be self-hosted. The Relay service is a [TURN server](https://webrtc.org/getting-started/turn-server) in WebRTC terminology. In fact, we use an open-source implementation called [Coturn](https://github.com/coturn/coturn). -The purpose of this service is to be a "plan B" and relay traffic between peers in case a point-to-point connection isn't possible. - +The purpose of this service is to be a "plan B" and relay traffic between peers in case a point-to-point connection isn't possible. However starting with v0.29.0 a new relay based on WebSocket is implemented, moving away from TURN relay (coturn). [More info](https://netbird.io/knowledge-hub/september-newsletter).

relay-dia