eponymous
New Around Here
Since upgrading to 386.3, I have been having a strange issue with VPN Director. I'm probably not understanding something correctly, so hopefully someone can clear this up.
I am running my OpenVPN client with the setting:
Redirect Internet traffic through tunnel: VPN Director mode + killswitch rather than Yes (all). T
Incidentally, the Redirect Internet traffic through tunnel: Yes (all) results in my x3mRouting configuration (to bypass the tunnel for specific domains) not work anymore, in case this is useful to anyone. If I try to visit the bypassed domains with Yes (all) turned on, the browser just hangs forever. Using VPN Director with policy rules does allow x3mRouting settings to work as before, while still directing the remaining traffic through the tunnel.
However, the issue I am having is that the policy rule I add to VPN Director (to route all traffic through the tunnel) disappears after each router reboot.
My rules just before reboot:
My rules just after reboot:
This is not just cosmetic, indeed the traffic no longer passes through the tunnel until I add the rule back in using the console. Once I do, all traffic goes through the tunnel once more.
I was using policy rules in earlier versions of the firmware with just these rules, so the configuration does work as-is. The rules did not disappear at each reboot in the past.
You can see there is a rule that does not disappear - which passes traffic from my VPN Server 1 to the VPN Client 1. This never disappears, and was also configured using x3mRouting.
While poking around in the file system, I checked the file
Thanks for any suggestions you can offer. I wonder if there is some weird interaction with x3mRouting going on, and perhaps I should delete/uninstall it and reinstall to fix this issue.
I am running my OpenVPN client with the setting:
Redirect Internet traffic through tunnel: VPN Director mode + killswitch rather than Yes (all). T
Incidentally, the Redirect Internet traffic through tunnel: Yes (all) results in my x3mRouting configuration (to bypass the tunnel for specific domains) not work anymore, in case this is useful to anyone. If I try to visit the bypassed domains with Yes (all) turned on, the browser just hangs forever. Using VPN Director with policy rules does allow x3mRouting settings to work as before, while still directing the remaining traffic through the tunnel.
However, the issue I am having is that the policy rule I add to VPN Director (to route all traffic through the tunnel) disappears after each router reboot.
My rules just before reboot:
My rules just after reboot:
This is not just cosmetic, indeed the traffic no longer passes through the tunnel until I add the rule back in using the console. Once I do, all traffic goes through the tunnel once more.
I was using policy rules in earlier versions of the firmware with just these rules, so the configuration does work as-is. The rules did not disappear at each reboot in the past.
You can see there is a rule that does not disappear - which passes traffic from my VPN Server 1 to the VPN Client 1. This never disappears, and was also configured using x3mRouting.
While poking around in the file system, I checked the file
/jffs/openvpn/vpndirector_rulelist
and I see the rule is present after adding it manually via the console, so something is being written to the jffs file system:<1>VPN Server 1>10.8.0.0/24>>OVPN1<1>Route traffic through tunnel>192.168.50.0/24>>OVPN1
Thanks for any suggestions you can offer. I wonder if there is some weird interaction with x3mRouting going on, and perhaps I should delete/uninstall it and reinstall to fix this issue.