What's new

VPN "killswitch" problem when more than one client configured

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

ZakM

Occasional Visitor
I have landed onto a weird issue, maybe a bug, when configuring two (Probably applies to more) VPN clients on my Merlin setup.

I have loaded two ovpn config files, one as client 1 and the other as client 2. The only difference between the two is the server they connect to.

Both have Policy Rules. Both have "Block routed clients if tunnel goes down" activated.

If I disconnect one of the clients and connect the other, the "Block routed clients if tunnel goes down" setting from the disconnected client affects the other, so even if the VPN is connected, because the other Client config one is not, all clients are being blocked from accessing the WAN.

So my only workaround is go to the disabled client and disable that option.

Could this be fixed?
 
This is how it's intended to work. The router cannot determine if a tunnel goes down because of a connectivity problem or by the end-user, so the killswitch will always be active if it's configured on a client.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top