First things first, a big thanks for a great firmware (any help help provided below)!
I have the custom Asuswrt-Merlin installed on my ASUS VPN router. I have it configured with my OpenVPN, and the killswitch setting active (with the intent that if anything happens with the VPN, it immediately kills the connection to any attached devices). It's always worked great, until a few months ago. I always check my IP address at first boot, to make sure it's the one assigned by the VPN before browsing. This router is only connected when needed, and is stored when not in use (which can be a few weeks to a month between uses). On last boot, I was surprised to find my home IP was reading on my connected device, instead of the usual IP provided by my VPN (and I checked the killswitch setting, which was still on).
I've been reading through the forums, and this seems to be a know issue, so was just wondering if a fix in the more recent updates have been implemented. I'm not sure which version I'm running, but it's at least a year old (based on when I know I set it up, and haven't touched it since). I've always relied with 100% certainty that the killswitch will shield my real IP, but this recent "leak" has me re-evaluating my setup. I'm not seeing in any recent forums posts that this has been fixed to a certainty, so would love to know more (if possible).
Thanks!
I have the custom Asuswrt-Merlin installed on my ASUS VPN router. I have it configured with my OpenVPN, and the killswitch setting active (with the intent that if anything happens with the VPN, it immediately kills the connection to any attached devices). It's always worked great, until a few months ago. I always check my IP address at first boot, to make sure it's the one assigned by the VPN before browsing. This router is only connected when needed, and is stored when not in use (which can be a few weeks to a month between uses). On last boot, I was surprised to find my home IP was reading on my connected device, instead of the usual IP provided by my VPN (and I checked the killswitch setting, which was still on).
I've been reading through the forums, and this seems to be a know issue, so was just wondering if a fix in the more recent updates have been implemented. I'm not sure which version I'm running, but it's at least a year old (based on when I know I set it up, and haven't touched it since). I've always relied with 100% certainty that the killswitch will shield my real IP, but this recent "leak" has me re-evaluating my setup. I'm not seeing in any recent forums posts that this has been fixed to a certainty, so would love to know more (if possible).
Thanks!