Skip to content

Commit e318eef

Browse files
authored
Remove Linux only note (#284)
1 parent 2a00ffe commit e318eef

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

src/pages/how-to/networks.mdx

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -31,17 +31,14 @@ different environments, such as office networks, cloud VPCs, or on-premise LANs.
3131

3232
### Routing peers
3333
To access your internal resources, you need to route traffic from your NetBird peers to your internal networks.
34-
Routing peers are Linux machines that connect your NetBird peers and your internal networks.
34+
Routing peers are machines that connect your NetBird peers and your internal networks.
3535
You can add as many routing peers as you need using single peers or groups to ensure high availability and load balancing.
3636
You can define masquerading and priority for each routing peer.
3737

3838
<p>
3939
<img src="/docs-static/img/how-to-guides/networks/add-routing-peer-1.png" alt="high-level-dia" className="imagewrapper"/>
4040
</p>
4141

42-
<Note>
43-
Only Linux OS machines can be assigned as routing peers.
44-
</Note>
4542

4643
### Resources
4744
Resources are individual machines, services, or subnets within your internal network. You can define resources as single

0 commit comments

Comments
 (0)