diff --git a/public/docs-static/img/how-to-guides/netbird-network-routes-add-button.png b/public/docs-static/img/how-to-guides/netbird-network-routes-add-button.png
index 4604f5c7..49602ace 100644
Binary files a/public/docs-static/img/how-to-guides/netbird-network-routes-add-button.png and b/public/docs-static/img/how-to-guides/netbird-network-routes-add-button.png differ
diff --git a/public/docs-static/img/how-to-guides/netbird-network-routes-create-ha.png b/public/docs-static/img/how-to-guides/netbird-network-routes-create-ha.png
index 0a25c099..14090076 100644
Binary files a/public/docs-static/img/how-to-guides/netbird-network-routes-create-ha.png and b/public/docs-static/img/how-to-guides/netbird-network-routes-create-ha.png differ
diff --git a/public/docs-static/img/how-to-guides/netbird-network-routes-create.png b/public/docs-static/img/how-to-guides/netbird-network-routes-create.png
index 8c7a1483..17eb3599 100644
Binary files a/public/docs-static/img/how-to-guides/netbird-network-routes-create.png and b/public/docs-static/img/how-to-guides/netbird-network-routes-create.png differ
diff --git a/public/docs-static/img/how-to-guides/netbird-network-routes-groups-attribution.png b/public/docs-static/img/how-to-guides/netbird-network-routes-groups-attribution.png
new file mode 100644
index 00000000..98dd0939
Binary files /dev/null and b/public/docs-static/img/how-to-guides/netbird-network-routes-groups-attribution.png differ
diff --git a/public/docs-static/img/how-to-guides/netbird-network-routes-saved-new-ha.png b/public/docs-static/img/how-to-guides/netbird-network-routes-saved-new-ha.png
index 94956a6e..9c82e714 100644
Binary files a/public/docs-static/img/how-to-guides/netbird-network-routes-saved-new-ha.png and b/public/docs-static/img/how-to-guides/netbird-network-routes-saved-new-ha.png differ
diff --git a/public/docs-static/img/how-to-guides/netbird-network-routes-saved-new.png b/public/docs-static/img/how-to-guides/netbird-network-routes-saved-new.png
index 4cc6b66e..887ecdc0 100644
Binary files a/public/docs-static/img/how-to-guides/netbird-network-routes-saved-new.png and b/public/docs-static/img/how-to-guides/netbird-network-routes-saved-new.png differ
diff --git a/src/pages/how-to/routing-traffic-to-private-networks.mdx b/src/pages/how-to/routing-traffic-to-private-networks.mdx
index bbdd2bd8..d8f9f147 100644
--- a/src/pages/how-to/routing-traffic-to-private-networks.mdx
+++ b/src/pages/how-to/routing-traffic-to-private-networks.mdx
@@ -15,7 +15,7 @@ NetBird provides fast and reliable end-to-end encryption between peers in your n
In these cases, you can configure network routes assigning routing peers to connect existing infrastructure. Routing peers will forward packets between your NetBird peers and your other networks; they can masquerade traffic going to your data centers or embedded devices, reducing the need for external route configuration and agent installation.
-
+
@@ -73,7 +73,7 @@ In the example below, we are creating a route with the following information:
- Distribution Groups: `All`
-
+
Once you fill in the route information, you can click on the `Save` button to save your new route.
@@ -88,29 +88,42 @@ However, you still want to ensure a reliable connection to your private network
NetBird Network Routes feature has a High Availability (HA) mode,
allowing one or more NetBird peers to serve as routing peers for the same private network.
-To enable high-available mode, you can click on `Configure` and select a new peer in the `Add additional routing peer` field, then select the distribution groups and click on `Save`.
+To enable high-available mode, click on `Configure` in the table and select a new peer in the `Routing Peer` field, then select the distribution groups and click on `Add Route`.
-In the following screenshot, we are adding the peer `aws-nb-europe-router-az-b` to the `aws-eu-central-1-vpc` route:
+In the following example, we are adding the peer `aws-nb-europe-router-az-b` to the `aws-eu-central-1-vpc` route:
-
+
-This way, nodes connected to both peer `aws-nb-europe-router-az-a` and peer `aws-nb-europe-router-az-b` would have a highly available connection with the network `172.31.0.0/16`.
+This way, peers connected to `aws-nb-europe-router-az-a` and `aws-nb-europe-router-az-b` will have highly available access to the `172.31.0.0/16` network.
- Currently, there is no limitation in the number of routes that form a highly available route. Each connected peer will pick one routing peer to use as the router for a network; this decision is based on metric prioritization and connection attributes like direct or relayed connections.
+ The number of routes that form a highly available route is unlimited.
+ Each connected peer will pick one routing peer to use as the router for a network.
+ NetBird agent bases this decision on metric prioritization (lower the metric, higher the priority) and connection attributes like direct or relayed connections.
-### Filtering routes distribution with groups
-You can select as many distribution groups as you want for your network route. You can update them at the routing peer or high-availability group level. Keep in mind to link them to peers and, if required, to add access control rules ensuring connectivity between these peers and the routing peers of your route
+### Apply different routes to peers with group attribution
+You can select as many distribution groups as you want for your network route.
+Peers that belong to the specified group will use the route automatically to connect to the underlying network.
+
+Remember to link groups to peers that need to access the route and, if required,
+add access control rules ensuring connectivity between these peers and the routing peers.
+
+In the following example (see column `Groups`), peers that belong to group `berlin-office` will use `aws-nb-europe-router-az-a` routing peer to access the `aws-eu-central-1-vpc` network. While peers that belong to group `london-office` will use `aws-nb-europe-router-az-b` routing peer.
+
+
+
+
+
### Routes without masquerading
If you want more transparency and would like to manage your external network routers, you may choose to disable masquerade for your network routes.
-In this case, the routing peer won't hide any NetBird peer IP and will forward the packets to the target network transparently.
+In this case, the routing peer won't hide any NetBird peer IP and will forward the packets to the target network transparently.
That will require a routing configuration on your external network router pointing your NetBird network back to your routing peer.
This way, devices that don't have the agent installed can communicate with your NetBird peers.