From ee9c73ae9573fea091827c270685d81292dc532b Mon Sep 17 00:00:00 2001 From: Zoltan Papp Date: Sun, 6 Jul 2025 15:34:43 +0200 Subject: [PATCH 1/2] Update lazy connection description --- src/pages/how-to/lazy-connection.mdx | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/src/pages/how-to/lazy-connection.mdx b/src/pages/how-to/lazy-connection.mdx index be8efa47..445abdcd 100644 --- a/src/pages/how-to/lazy-connection.mdx +++ b/src/pages/how-to/lazy-connection.mdx @@ -6,13 +6,13 @@ NetBird now includes an experimental lazy connection feature designed to improve This guide walks you through enabling and configuring this feature in your NetBird client. - Minimum supported agent version: v0.45.0. + Minimum supported agent version: v0.50.1. This or higher version must also be installed on the peers you are trying to access for lazy connections to function. This feature also requires an upgraded NetBird Management server. - If you're self-hosting NetBird, ensure your server is updated to version v0.45.0, which adds support for lazy connections. + If you're self-hosting NetBird, ensure your server is updated to version v0.50.1, which adds support for lazy connections. @@ -25,7 +25,7 @@ When enabled, lazy connections allow the NetBird agent to: - Establish peer-to-peer connections **only when needed** (e.g., when pinging a remote peer). - Monitor peer activity and **automatically disconnect peers** that remain inactive **and unreachable** for a specified time. -- Keep critical peers (such as routers or excluded peers) **always connected** to ensure uninterrupted communication. +- Keep critical peers (such as excluded peers) **always connected** to ensure uninterrupted communication. This feature is especially useful in **large-scale deployments** or **resource-constrained environments**, where maintaining full-mesh, permanent connections to all peers is unnecessary and inefficient. @@ -36,15 +36,12 @@ This feature is especially useful in **large-scale deployments** or **resource-c ### How Automatic Disconnection Works -Once a connection between two peers is established, it will remain open **as long as the remote peer is reachable**. The connection is **not** closed just because there is no data transfer. - -In other words, the inactivity timer only triggers a disconnect if the peer is both inactive and unreachable for the full duration of the threshold. +Once a connection between two peers is established, it will remain open only if there is ongoing traffic from the remote peer. If no traffic is received for 15 minutes, the connection will be closed — even if the remote peer is still reachable. - The default inactivity threshold is 60 minutes, and can be configured via the NB_LAZY_CONN_INACTIVITY_THRESHOLD environment variable. + The default inactivity threshold is 15 minutes, and can be configured via the NB_LAZY_CONN_INACTIVITY_THRESHOLD environment variable. -Additionally, the disconnection logic is being improved and will be enhanced in future releases to better support mobile devices—providing more intelligent reconnection behavior and improved handling of intermittent connectivity. ## Enabling Lazy Connections on agent From 0e933083bc6d795c84ad43f11c3c9863a08823cb Mon Sep 17 00:00:00 2001 From: Zoltan Papp Date: Sun, 6 Jul 2025 15:35:48 +0200 Subject: [PATCH 2/2] Add Signal server too --- src/pages/how-to/lazy-connection.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/how-to/lazy-connection.mdx b/src/pages/how-to/lazy-connection.mdx index 445abdcd..1a32cdf0 100644 --- a/src/pages/how-to/lazy-connection.mdx +++ b/src/pages/how-to/lazy-connection.mdx @@ -11,7 +11,7 @@ This guide walks you through enabling and configuring this feature in your NetBi - This feature also requires an upgraded NetBird Management server. + This feature also requires an upgraded NetBird Management and Signal server. If you're self-hosting NetBird, ensure your server is updated to version v0.50.1, which adds support for lazy connections.