Clarify that lazy connections don't require self-hosting (#1061)

This commit is contained in:
Bruno Mercier Costa
2026-10-22 19:29:30 +02:00
committed by GitHub
parent 56abf59cb3
commit ff6170673e
+1 -1
View File
@@ -5,7 +5,7 @@ import {Note} from "@/components/mdx";
Lazy connections reduce resource use in large NetBird networks by opening peer connections only when traffic needs them, rather than maintaining every possible full-mesh connection continuously. Lazy connections reduce resource use in large NetBird networks by opening peer connections only when traffic needs them, rather than maintaining every possible full-mesh connection continuously.
<Note> <Note>
Lazy connections require NetBird v0.50.1 or later on the client, the peers it communicates with, and self-hosted Management and Signal servers. Lazy connections require NetBird v0.50.1 or later on the client and on the peers it communicates with. If you self-host NetBird, your Management and Signal servers must also run v0.50.1 or later. NetBird Cloud already meets this requirement.
</Note> </Note>
## How Lazy Connections Work ## How Lazy Connections Work