The change notes of the Merlin 384.9 Beta 1 release mentioned that the DNS leak was fixed. It did not mention how or any thing more about it. I spent much of yesterday trying to plug my DNS leak in my configuration. I am skipping hours of failed attempts. I use ExpressVPN and simply imported the downloaded .ovpn config file adjusted check boxes a little as required.
First of all the easy solution when configuring OpenVPN.
Set the Redirect Internet Traffic to "All" and the leak vanished.
However my requirement is to allow some traffic to avoid the tunnel show up on my ISP's address space. Services like sending email (SMTP) and their streaming only work if my host is located there.
A partial example. Redirect Internet Traffic (Policy Rules)
Old config example which leaks DNS.
smtp.cox 192.168.1.0/24 68.1.17.4 wan
home theater 192.168.1.83 0.0.0.0 wan
all hosts 192.168.1.0/24 0.0.0.0 vpn
Example config which does not leak DNS
smtp.cox 0.0.0.0 68.1.17.4 wan
home theter 192.168.1.83 0.0.0.0 wan
all hosts 192.168.1.0/24 0.0.0.0 vpn
The limitation is that there must be 0.0.0.0 as the source or the destination in the entire policy rules set.
If I wanted to use (Policy Rules Strict), I needed to include the gateway in the wan exceptions.
router 192.168.1.1 0.0.0.0 wan
I use ExpressVPN and simply imported the .ovpn config file adjusted a little as required.
AsusWRT-Merlin is a little weird. Play with it to much and the VPN breaks completely until the router is rebooted. Once I plugged the leak, I did several repeat tests, some of the tests showed the VPN DNS and a configured DNS server (1.1.1.1) but once the router was cold booted that anomaly vanished.
First of all the easy solution when configuring OpenVPN.
Set the Redirect Internet Traffic to "All" and the leak vanished.
However my requirement is to allow some traffic to avoid the tunnel show up on my ISP's address space. Services like sending email (SMTP) and their streaming only work if my host is located there.
A partial example. Redirect Internet Traffic (Policy Rules)
Old config example which leaks DNS.
smtp.cox 192.168.1.0/24 68.1.17.4 wan
home theater 192.168.1.83 0.0.0.0 wan
all hosts 192.168.1.0/24 0.0.0.0 vpn
Example config which does not leak DNS
smtp.cox 0.0.0.0 68.1.17.4 wan
home theter 192.168.1.83 0.0.0.0 wan
all hosts 192.168.1.0/24 0.0.0.0 vpn
The limitation is that there must be 0.0.0.0 as the source or the destination in the entire policy rules set.
If I wanted to use (Policy Rules Strict), I needed to include the gateway in the wan exceptions.
router 192.168.1.1 0.0.0.0 wan
I use ExpressVPN and simply imported the .ovpn config file adjusted a little as required.
AsusWRT-Merlin is a little weird. Play with it to much and the VPN breaks completely until the router is rebooted. Once I plugged the leak, I did several repeat tests, some of the tests showed the VPN DNS and a configured DNS server (1.1.1.1) but once the router was cold booted that anomaly vanished.