upstream/opnsense-docs
1
0
Fork 0
mirror of https://github.com/opnsense/docs.git synced 2026-05-28 04:02:12 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

WG selective routing: clarify why Step 9 (#457)

Browse source
This commit is contained in:
Paride Legovini 2024-12-12 19:12:58 +01:00 committed by GitHub
parent 65e0f10463
commit 79c7c3cea7
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 6 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
source/manual/how-tos/wireguard-selective-routing.rst
View file

@ -196,11 +196,13 @@ The step has two parts - first creating a second Alias for all local (private) n
- **Save** the rule, and then click **Apply Changes**
- Then make sure that the new rule is **above** any other rule on the interface that would otherwise interfere with its operation. For example, you want your new rule to be above the “Default allow LAN to any rule”
--------------------------
Step 9 - Configure routing
--------------------------
--------------------------------------------------------------
Step 9 - Configure routing for traffic generated by the router
--------------------------------------------------------------
- Then go to :menuselection:`Firewall --> Rules --> Floating`
Services running on the router and configured to use the VPN interface must have their traffic routed to the VPN gateway in order to use the VPN. Note that locally generated traffic is not affected by NAT or by the firewall rule created in Step 8.
- Go to :menuselection:`Firewall --> Rules --> Floating`
- Click **Add** to add a new rule
- Configure the rule as follows (if an option is not mentioned below, leave it as the default). You need to click the **Show/Hide** button next to "Advanced Options" to reveal the last setting: