sendnrw/netbird-docs
2
0
Fork 0
mirror of https://github.com/netbirdio/docs.git synced 2026-10-19 20:19:06 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merged WireGuard page into VPN comparison, added Self-Hosted tile (#788)

Browse Source
This commit is contained in:
Brandon Hopkins
2026-06-11 04:08:49 -07:00
committed by GitHub
parent abb000575d
commit 3d4f037c89
6 changed files with 48 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/pages/manage/networks/index.mdx
+1 -1
View File
@@ -6,7 +6,7 @@ export const description = "Learn how NetBird Networks work: the four building b
# Networks
Every device that runs the NetBird client joins a single private **overlay network**, encrypted end to end with [WireGuard](/about-netbird/why-wireguard-with-netbird). Nothing is exposed to the public internet, and you never open an inbound port. Peers connect outbound and negotiate connectivity using ICE/STUN for NAT traversal. See [Ports & Firewalls](/about-netbird/ports-and-firewalls) for details.
Every device that runs the NetBird client joins a single private **overlay network**, encrypted end to end with [WireGuard](/about-netbird/netbird-vs-traditional-vpn#why-wireguard-with-netbird). Nothing is exposed to the public internet, and you never open an inbound port. Peers connect outbound and negotiate connectivity using ICE/STUN for NAT traversal. See [Ports & Firewalls](/about-netbird/ports-and-firewalls) for details.
But you can't run the client everywhere. Some devices can't run it at all, like printers, IoT sensors, and appliances you can't install software on. And installing it on every database and server is more overhead than most teams want. A **Network** fills that gap: a few clients become routing peers that open whole subnets, single hosts, and internal domains to your overlay network, with nothing reachable until a policy allows it.