Skip to content

Update routing-traffic-to-private-networks.mdx #414

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 2 additions & 6 deletions src/pages/how-to/routing-traffic-to-private-networks.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -36,14 +36,10 @@ A network route describes the network you want to connect with your NetBird peer
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.
#### Routing peer
A routing peer is a peer that routes packets between your routed network and the other NetBird peers.
<Note>
Only Linux OS machines can be assigned as routing peers.
</Note>

#### Routing group
A routing group is a set of routing peers. Each will route packets between your routed network and the other NetBird peers.
<Note>
Only Linux OS machines can be assigned as routing peers.
</Note>

#### High availability routes
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.
Nodes connected to routing peers will choose one of them to route packets to external networks based on connection type and defined metrics.
Expand Down