Skip to content

Commit 78d0dfc

Browse files
Drop OS limitation regarding routers on routing-traffic-to-private-networks.mdx (#414)
1 parent 69280e1 commit 78d0dfc

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

src/pages/how-to/routing-traffic-to-private-networks.mdx

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -36,14 +36,10 @@ A network route describes the network you want to connect with your NetBird peer
3636
Network identifiers are names for each network you want to route traffic from your peers, and ranges are IP ranges declared in CIDR notation which refers to an external network. The combination of identifiers and these ranges makes a single network.
3737
#### Routing peer
3838
A routing peer is a peer that routes packets between your routed network and the other NetBird peers.
39-
<Note>
40-
Only Linux OS machines can be assigned as routing peers.
41-
</Note>
39+
4240
#### Routing group
4341
A routing group is a set of routing peers. Each will route packets between your routed network and the other NetBird peers.
44-
<Note>
45-
Only Linux OS machines can be assigned as routing peers.
46-
</Note>
42+
4743
#### High availability routes
4844
A highly available route is a combination of multiple routes with the same network identifier and ranges. They have different routing peers or routing peer groups offering highly available paths for communication between your peers and external networks.
4945
Nodes connected to routing peers will choose one of them to route packets to external networks based on connection type and defined metrics.

0 commit comments

Comments
 (0)