From f3c5c47d83a664a1db8e5ba4e18b5c5aa06fd482 Mon Sep 17 00:00:00 2001 From: Jack Carter <128555021+SunsetDrifter@users.noreply.github.com> Date: Wed, 13 May 2026 12:35:57 +0200 Subject: [PATCH] docs(site-to-vpn): drop the inline Network Routes equivalent note The guide is Networks-only now. Pointing readers at Network Routes mid-flow just creates two paths to maintain without serving the reader who's following the steps in front of them. --- .../network-routes/use-cases/by-scenario/site-to-vpn.mdx | 7 ------- 1 file changed, 7 deletions(-) diff --git a/src/pages/manage/network-routes/use-cases/by-scenario/site-to-vpn.mdx b/src/pages/manage/network-routes/use-cases/by-scenario/site-to-vpn.mdx index 2245a57a..e26cd5c8 100644 --- a/src/pages/manage/network-routes/use-cases/by-scenario/site-to-vpn.mdx +++ b/src/pages/manage/network-routes/use-cases/by-scenario/site-to-vpn.mdx @@ -152,13 +152,6 @@ Attach the routing peer: userspace mode 4. Click **Save** - -If you prefer Network Routes, the equivalent is **Network Routes → Add -Route** with: network range `192.168.50.0/24`, routing peer `site-router`, -distribution group `backup-collectors`, masquerade enabled. The rest of this -guide applies unchanged. - - ## Step 5: Create the Access Policy The routing peer needs to be allowed to reach the target peer over the