From b65544d4c793958e6e825d752926e41a09570687 Mon Sep 17 00:00:00 2001 From: Jack Carter <128555021+SunsetDrifter@users.noreply.github.com> Date: Wed, 15 Apr 2026 13:46:16 +0200 Subject: [PATCH] docs: add minimum access policy note for exit nodes --- .../network-routes/use-cases/by-scenario/exit-nodes.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/pages/manage/network-routes/use-cases/by-scenario/exit-nodes.mdx b/src/pages/manage/network-routes/use-cases/by-scenario/exit-nodes.mdx index 237b9681e..a07026453 100644 --- a/src/pages/manage/network-routes/use-cases/by-scenario/exit-nodes.mdx +++ b/src/pages/manage/network-routes/use-cases/by-scenario/exit-nodes.mdx @@ -24,6 +24,10 @@ The routing peer acts as the exit node for internet traffic. It applies masquera Peers in the distribution groups send their internet traffic through the routing peer once it connects. + + The minimum access policy required for peers to use an exit node is **Users** (source) → **Routing Peer** (destination) over **ICMP**. Ensure a policy with this configuration exists for the distribution groups assigned to the exit node route. + + ### Exit Node Selection and Auto Apply Administrators configure exit nodes from the dashboard and can enable **Auto Apply** to have clients automatically use the exit node.