mirror of
https://github.com/netbirdio/docs.git
synced 2026-04-15 23:16:36 +00:00
Remove Linux only note (#284)
This commit is contained in:
@@ -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.
|
||||
<img src="/docs-static/img/how-to-guides/networks/add-routing-peer-1.png" alt="high-level-dia" className="imagewrapper"/>
|
||||
</p>
|
||||
|
||||
<Note>
|
||||
Only Linux OS machines can be assigned as routing peers.
|
||||
</Note>
|
||||
|
||||
### Resources
|
||||
Resources are individual machines, services, or subnets within your internal network. You can define resources as single
|
||||
|
||||
Reference in New Issue
Block a user