I'm running PIA Vpn also and when I disable the one pc's vpn in VPN Director the kill switch does not prevent the pc from accessing the internet. before upgrading to 386.3 if the tunnel went down I could not go to any internet site until I restarted the VPN service. Minor issue and certain it relates to a setting on my end as Merlin Rocks.Thanks again for your hard work RMerlin,
Not sure this is the place for this questions but,
I noticed a small problem with VPN Director with the kill switch. I have PIA VPN, I route a single local IP via that VPN. With VPN Director, if i kill the OpenVPN client the kill switch works as expected, however upon reboot I see kill switch does not work. Traffic goes through my Public IP until the VPN client is connected.
Is there a log file which i can check out for further troubleshooting?
I currenty have 3 active VPN clients set up and YazFi in use - is there anything I need to do / save before upgrading?
Will YazFi still be required with VPN Director?
I have never had a bad experience yet with Merlin FW but my knowledge on policy based routing etc. is very poor, am a bit reluctant witht this upgrade!
Jul 25 01:07:04 ovpn-client1[3455]: --cipher is not set. Previous OpenVPN version defaulted to BF-CBC as fallback when cipher negotiation failed in this case. If you need this fallback please add '--data-ciphers-fallback BF-CBC' to your configuration and/or add BF-CBC to --data-ciphers.
Jul 25 01:07:04 ovpn-client1[3455]: Options error: You must define CA file (--ca) or CA path (--capath)
Jul 25 01:07:04 ovpn-client1[3455]: Use --help for more information.
Jul 25 01:07:04 openvpn: Starting OpenVPN client 1 failed!
Jul 25 01:07:04 openvpn-routing: Clearing routing table for VPN client 1
Jul 25 01:07:05 kernel: EMF_ERROR: Interface tap11 doesn't exist
Jul 25 01:07:05 kernel: EMF_ERROR: Interface tun11 doesn't exist
Sure are sir. Apparently you have not uploaded the CA (or a valid CA file) file and its also complaining about no encryption (cipher) too.I may be doing something wrong but VPN won't start for me
Same problem here on my RT-AX88U. When Killswitch is active and the VPN goes down, my PC still has access to the internet.I'm running PIA Vpn also and when I disable the one pc's vpn in VPN Director the kill switch does not prevent the pc from accessing the internet. before upgrading to 386.3 if the tunnel went down I could not go to any internet site until I restarted the VPN service. Minor issue and certain it relates to a setting on my end as Merlin Rocks.
If you come across a solution please share it. Thanks
Only if you do it manually and that is by design.Same problem here on my RT-AX88U. When Killswitch is active and the VPN goes down, my PC still has access to the internet.
Here is my rule that works before 386.3 for killswitch :
View attachment 35213
Thanks for your help
Thanks for your answer. Yes, in fact the test I did is to disable the VPN manually with this button and the Killswitch did not work :Only if you do it manually and that is by design.
You can test with "killall vpnclient1" and killswitch should working. Start with "service start_vpnclient1"Thanks for your answer. Yes, in fact the test I did is to disable the VPN manually with this button and the Killswitch did not work :
View attachment 35215
I hope that in case of real cut the connection will be cut because on the previous version, the manual deactivation of the VPN cut the connection well. So my rule is correct in VPN Director ?
thank you for your help. I just did the test and indeed the killswitch works perfectly with my ruler !You can test with "killall vpnclient1" and killswitch should working. Start with "service start_vpnclient1"
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!