Skip to content

Commit 24c1217

Browse files
committed
Explain lazy connection enable-disable logic
1 parent ce4151c commit 24c1217

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

src/pages/how-to/lazy-connection.mdx

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ In other words, the inactivity timer only triggers a disconnect if the peer is b
4141

4242
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.
4343

44-
## Enabling Lazy Connections
44+
## Enabling Lazy Connections on agent
4545

4646
Lazy connections are disabled by default. To enable them:
4747

@@ -67,6 +67,15 @@ For platform-specific examples of how to configure this:
6767
- [See Linux with systemd example](/how-to/troubleshooting-client#on-linux-with-systemd)
6868

6969

70+
## Enabling Lazy Connections on Dashboard
71+
72+
The lazy connection feature is configurable via the NetBird Dashboard as well. Here's how it behaves based on the setting:
73+
74+
- **When enabled:**
75+
The lazy connection manager is started and all peers are added to the manager in an **active** state. If a remote peer becomes unavailable, the local peer will **wait 1 hour** (by default) before transitioning to an **idle** state, at which point the connection will be dropped if still unreachable.
76+
77+
- **When disabled:**
78+
The lazy connection manager is stopped, and the agent will **immediately establish connections** to all peers listed in the store, creating a persistent full-mesh network.
7079

7180

7281
## Get started

0 commit comments

Comments
 (0)