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?
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?