Recent content by bassoonsun

So just to clarify your response as I was unaware of this, assuming you have both VPN clients enabled / connected at the same time, with both set to automatic start at boot with overlapping rules. It will start with OVPN 1 and if it is disabled it will immediately attempt to go to OVPN 2...

I understand I'll try to find a work around, the current implementation with 388/3006 built-in Merlin killswitch only functions when the VPN is enabled, so if you disable the VPN to switch to another VPN the killswitch is not active during that time and you connect directly through the WAN. Also...

So just thought I'd give some input here on the current implementation with 3004/3006 built-in Merlin killswitch. The built-in killswitch only functions when the VPN is enabled so if you disable the VPN to switch to another VPN the killswitch is not active during that time and you connect...

Appreciate the release. This is kind of a wishlist but is it at all possible to provide an option for the previous killswitch implementation that was active even if the user manually stopped a client. The old 3006.102.1 release I find the killswitch was perfect for preventing leaks and actually...

Question regarding the Killswitch with the most recent 3004 versions trying to get a proper understanding of how it functions. With 3004 on the old Jun-2024 release, the killswitch rules were created before WAN goes up, “to reduce the risks of leaks between WAN going up and VPN connecting” The...