From e318eefc86381b4b6ff072f2db673a241dd514c5 Mon Sep 17 00:00:00 2001 From: Viktor Liu <17948409+lixmal@users.noreply.github.com> Date: Fri, 7 Mar 2025 07:41:39 +0100 Subject: [PATCH] Remove Linux only note (#284) --- src/pages/how-to/networks.mdx | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/src/pages/how-to/networks.mdx b/src/pages/how-to/networks.mdx index 656d054a..0ee14e97 100644 --- a/src/pages/how-to/networks.mdx +++ b/src/pages/how-to/networks.mdx @@ -31,7 +31,7 @@ different environments, such as office networks, cloud VPCs, or on-premise LANs. ### Routing peers To access your internal resources, you need to route traffic from your NetBird peers to your internal networks. -Routing peers are Linux machines that connect your NetBird peers and your internal networks. +Routing peers are machines that connect your NetBird peers and your internal networks. You can add as many routing peers as you need using single peers or groups to ensure high availability and load balancing. You can define masquerading and priority for each routing peer. @@ -39,9 +39,6 @@ You can define masquerading and priority for each routing peer. high-level-dia

- - Only Linux OS machines can be assigned as routing peers. - ### Resources Resources are individual machines, services, or subnets within your internal network. You can define resources as single