diff --git a/docs/how-to-guides/network-routes.md b/docs/how-to-guides/network-routes.md index fe55763e..74d478fb 100644 --- a/docs/how-to-guides/network-routes.md +++ b/docs/how-to-guides/network-routes.md @@ -95,7 +95,13 @@ This way, nodes connected to both peer `aws-nb-europe-router-az-a` and peer `aws 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. ::: -### Routes without masquerade -If you want more transparency and can 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. +### 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. -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. \ No newline at end of file +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. + +

+ high-level-dia +

\ No newline at end of file