Exactly. To recap for everybody, if you are experiencing a situation where:
1. You are running a WireGuard VPN (let's say wgc4)
2. You cannot connect to the internet from the router local interface via wgc4 (e.g. via a script or if you ssh into your local router)
3. The problem may be due to the setting of your /proc/sys/net/ipv4/conf/wgc4/rp_filter
4. you can read the filter value with a
5. If the filter value is 1 it means that Wireguard is blocking an external connection from reaching your internal router interface.
6. You have two main ways of fixing this.
a. set the filter value to 2.
(this will reset after a boot)
b. set a rule on VPNdirector, like this:
7. Your WireGuard local IP address can be found with:
or in your router's WireGuard config interface, it should start with 10.
Credits and many thanks to: @ZebMcKayhan
1. You are running a WireGuard VPN (let's say wgc4)
2. You cannot connect to the internet from the router local interface via wgc4 (e.g. via a script or if you ssh into your local router)
3. The problem may be due to the setting of your /proc/sys/net/ipv4/conf/wgc4/rp_filter
4. you can read the filter value with a
Code:
cat /proc/sys/net/ipv4/conf/wgc4/rp_filter6. You have two main ways of fixing this.
a. set the filter value to 2.
Code:
echo 2 > /proc/sys/net/ipv4/conf/wgc4/rp_filter(this will reset after a boot)
b. set a rule on VPNdirector, like this:
Code:
Interface: WGC4
Description Whatever you want
Local IP <your WireGuard local IP address>
Remote IP <leave blank>7. Your WireGuard local IP address can be found with:
Code:
Ifconfig wgc4or in your router's WireGuard config interface, it should start with 10.
Credits and many thanks to: @ZebMcKayhan
