ANSWERED Ip Leak through Client on Asus Router [SOLVED]

[pavlf 0]

Hello everyone, I'm having a bit of an issue with the VPN client on my asus ax86u pro router which is running the most recent version of the Merlin firmware. 

I run the Wireguard client on the router and direct a remote machine through that tunnel using the router's VPN director. Everything was fine until I changed ISP to Youfibre (in the UK). First off, both my VPN servers on the router stopped working. I found out this was because I needed a static IP (which cost more money). Anyway, I got a static IP and that fixed the VPN server issue.

Recently I realised I'd not checked to see if the VPN client was still ok on the remote machine - doh! I looked at ipleak.net and saw two IP addresses, the Airvpn server and the Youfibre server. Also, under VPN details the Airvpn box shows red and says no. If I run a torrent client, the same thing happens, both IP addresses show. This happens with both Wireguard and Openvpn clients.

If I run Wireguard on the remote machine rather than the router everything is fine, Airvpn works like a charm as it always has until now. But this is no good as I can't remotely access some of the webguis I need, for this the vpn client needs to work. As far I know anyway.

I read somewhere that turning off IPv6 could be the key, but when I turn that off I get 'error check configuration' in openvpn. 

This isn't really an Airvpn problem, it might be an Asus/Merlin issue (there have been some big updates lately that seemed to have affected VPNs), in which case I can post in their forum. It may also be a Youfibre issue. I don't really know enough to know what might be going on. 

Is anyone able to offer any advice - bearing in mind I'm not a networking expert by any means! Thanks.

[pavlf 0]

Quick update, with IPv6 disabled Wireguard works, but ipleak.net now shows only one IP (youfibre). So with IPv6 disabled the VPN doesn't work at all

 

[pavlf 0]

I've solved the problem, I just needed to block IPv6 in the local machine's firewall, perhaps delete the thread?