After upgrading from 4.7.4 to 4.8.0, VPN no longer works. Previously, everything (configuration: two clients running permanently via an OpenVPN connection) had been working perfectly since I started using the router. It does not work in global mode or in policy mode. I have also deleted all VPN settings and reconfigured them, and I have also reinstalled the configuration files for the VPNs, but the VPN still does not work—a connection is established as normal, data packets are sent, but not a single bit is received. No matter what I set – and I think I've read every discussion here and elsewhere about 4.8.0 by now. And as I mentioned, everything worked fine and reliably for almost two years before that.
So my question is, what the hell happened to the VPN?
Many thanks in advance for any advice and help.
Yep. I’m experiencing the same thing when using AdGuard and the VPN. Even in Global mode (forget policies). My IP is leaking. Moreover, the memory being used is super high. Before, with the VPN and AdGuard enabled (v4.7.4), my memory usage hovered around 65 to 68%, with HaGeZi’s Pro++ and TIF medium. Now it is over 80% without any filters or blocklists. Frustrating as v4.7.4 worked really well for me. I’m waiting for a solution from the team, failing which I’ll just go back to v4.7.4.
For me, VPN still seems to work (OpenVPN TAP-S2S), but annoyingly, the physical toggle button does not work when configured for switching the VPN on/off. I have both the OpenVPN TAP-S2S config on there as well as a Wireguard one - at first, the Wireguard config was set as the default VPN that would toggle with the button, and even trying to switch it by selecting the OpenVPN config from the menu would switch it on, but would not save it as the default config after disconnecting. I tried deleting the Wireguard config and then it would stay blank. Selecting the OpenVPN config again would once again activate the OpenVPN connection but would not set it as the default VPN. I added back the Wireguard config, and the default still remains blank - now I can select and activate either one, but neither gets set as the default, which means it cannot be activated/deactivated with the toggle button.
not sure if is related with vpn and dns resolution i made a post that is still active and we have some workarounds is a bug confirmed. I used DNS resolvers like Pihole, Windows Server DNS, AdguarHome, etc. So there is a vpn connection but the thing is the dns cannot appoint the right direction unless you apply a work around.
But I didn't have any problems with my VPN or PiHole configuration with version 4.7.4 and earlier versions.
However, with version 4.8.0, neither of them work anymore.
yes, this is correct the bug is in 4.8.0 stable version , i've 4.8.0 beta version 7 and is working but something happened in between. just test the work around on the other thread.
I also only use PiHole as a DNS resolver, and until version 4.8.0, my setup worked perfectly and without any problems for almost two years. The 4.8.0 version is completely screwed up!
You can also customize the DNS server as Pi hole IP directly on the client's network card settings. Of course, if client's network card settings not changes, let the DNS server as the router IP (i.e., gateway). DNS requests of client will be sent to router, and the router sent to the Pi hole (but there is only one gateway for the Pi hole client.)
Regardless of any of the above methods, when router VPN client is enabled, through the Pi-hole log, all LAN clients can resolve normally through Pi-hole DNS server:
I have the same issue... after upgrading to 4.8.0 my VPN does not work.... very frustrating, can someone confirm that the current Beta 4.8.x solved the problem?
I downgraded back to 4.7.4, but my VPN still isn’t working. I reinstalled the WireGuard config file, but no luck. Any suggestions to get my Beryl AX back to working condition?
Installing 4.8.1 (GL.iNet download center) solved the problem, my VPN (WireGuard) is working now. I’ll definitely wait to install the next official stable release, but for the moment it’s good to know these guys are on the right path!
I am also having this problem on an MT6000 Flint 2 using an OpenVPN client that splits traffic. i tried on 4.8.2 and also 4.8.3. My VPN handles all traffic for an AWS VPC, and the rest goes straight to the internet (with AdGuard as the DNS server). When I am not connected to the OpenVPN server, all traffic works. I can also use the OpenVPN client on my MacBook just fine. But when the OpenVPN client is connected on the MT6000 then only the VPN traffic works
