Maybe using ipv6 address to create tunnel is a good choice. The local ipv4 network disconnection will not disconnect the IPv6 tunnel connection, and it should not affect the communication through VPN.
I need an email address to send the firmware to you.
Any updates on this fix? When I activate the wireguard client, I want to use some devices without VPN, I do this filter via mac address but I have ipv4 (without vpn) and ipv6 (with vpn) on these devices that should be without VPN, I can only use the IPV6 of my provider if I disable the wireguard client.
Good Morning. Is there any update on this? I have been able to get IPV6 over wire Guard only partially working. I am able to ping the IPV6 IP address from the outside inside. I am able to ping the wireguard IPV6 IP; however, no Traffic IPV6 Routes out via the Wireguard, only IPv4 traffic.
There is a new firmware that makes VPN fully support IPV6 and includes the new VPN features that GL.iNet will launch later.
However, it is not a stable firmware and there are many issues such as leaks. And you may lose the previous configuration after upgrading.
Is anyone interested?
Of course, if you encounter any troubles during use, we will do our best to solve it.