Hello guys,
Found an issue on the new 4.8.0 beta . The wireguard is not working . Error msg is :
Unknown error occurred. Please check the network environment or reboot the device.
Reboot and reset didnt fix.
Please fix,
On GL-MT3000, when I turn the VPN ON, the internet stops to work and I can see this on the log:
Fri Jul 25 17:31:09 2025 daemon.notice netifd: Interface 'wgclient1' is setting up now
Fri Jul 25 17:31:09 2025 daemon.info dnsmasq[1]: exiting on receipt of SIGTERM
Fri Jul 25 17:31:12 2025 daemon.notice netifd: Interface 'wgclient1' is now up
Fri Jul 25 17:31:12 2025 daemon.notice netifd: Network device 'wgclient1' link is up
Fri Jul 25 17:31:12 2025 user.notice firewall: Reloading firewall due to ifup of wgclient1 (wgclient1)
Fri Jul 25 17:31:16 2025 daemon.crit dnsmasq[1]: bad option at line 1 of /tmp/dnsmasq.d.wgclient1/mark
Fri Jul 25 17:31:16 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Jul 25 17:31:21 2025 daemon.crit dnsmasq[1]: bad option at line 1 of /tmp/dnsmasq.d.wgclient1/mark
Fri Jul 25 17:31:21 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Jul 25 17:31:26 2025 daemon.crit dnsmasq[1]: bad option at line 1 of /tmp/dnsmasq.d.wgclient1/mark
Fri Jul 25 17:31:26 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Jul 25 17:31:31 2025 daemon.crit dnsmasq[1]: bad option at line 1 of /tmp/dnsmasq.d.wgclient1/mark
Fri Jul 25 17:31:31 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Jul 25 17:31:36 2025 daemon.crit dnsmasq[1]: bad option at line 1 of /tmp/dnsmasq.d.wgclient1/mark
Fri Jul 25 17:31:36 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Jul 25 17:31:36 2025 daemon.info procd: Instance dnsmasq::wgclient1 s in a crash loop 6 crashes, 0 seconds since last crash
1 Like
@bruce or one of the staff guys can please update the colleagues who created the firmware about this issue? Thanks
1 Like
I also have problems with wireguard client and VPN Dashboard, I receive message "Unknown error occurred. Please check the network environment or reboot the device."
1 Like
As @Renato post i think is a dnsmasq issue. The staff will verify and fix it.
3 Likes
I also found alot of issues with the repeater function which isn't a issue on 4.8 MTK SDK, 4.8 op24 has issues especially on the 5ghz band, I think it tries to connect to fast maybe double tries to authenticate where the AP blacklist it 2.4ghz works better, but it seems i also managed to get myself blacklisted for to many authentication attemps.
Tested on MT3000.
Edit:
Also it seems to appear on Slate7 firmware 4.7.3 but I think it is a different error, it's getting stuck on the channel saying the channel already exists and then proceeds scan looping.
The AP i connect to is using multi psk with wifi-station and wifi-vlan sections (radius) with 802.11r I made fixes to make sure the free roaming incompatibility doesn't impact much with the 4 way handshake by tweaking the reassociation deadline, but maybe these specific settings break alot of gl routers for connecting on my ap, other devices just connect fine.
My config as uci-default is here for a gl dev to test what could potentially break it, both aps use channel 100 and 108 on 5ghz.
2 Likes
Does anyone have 4.7.5-op24 for Beryl AX. Seems it was removed from the download page
Yes, of course, hold on.
2 Likes
Thanks.
For the beta release, basic functionality, including Wi-Fi, DNS, and VPN, should work without issues. .
2 Likes
Same but for Flint2?
Yes i posted about Flint2
Do you have also fw for flint2?
GL.iNet download center --- Download links are on that page. DONT INSTALL OP24 BETA because has issues. Will be fixed in the next days i hope
1 Like
Looking for 4.7.5-op24, was taken down...
Ill look at my downloads. Maybe i can find it.
You are lucky 
search in 4 laptops and 2 tablets. But found it
1 Like
I have exactly the same issue on my Beryl AX running 4.8.0op24.
Without Wireguard everything works fine.
With Wireguard i get no DNS via VPN clients
Logs show a dnsmasq error:
n Jul 27 15:59:59 2025 daemon.info dnsmasq[1]: DNS service limited to local subnets
Sun Jul 27 15:59:59 2025 daemon.info dnsmasq[1]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset nftset auth cryptohash DNSSEC no-ID loop-detect inotify dumpfile
Sun Jul 27 15:59:59 2025 daemon.info dnsmasq[1]: UBus support enabled: connected to system bus
Sun Jul 27 15:59:59 2025 daemon.info dnsmasq-dhcp[1]: DHCP, IP range 172.17.3.100 -- 172.17.3.249, lease time 12h
Sun Jul 27 15:59:59 2025 daemon.info dnsmasq-dhcp[1]: IPv6 router advertisement enabled
Sun Jul 27 15:59:59 2025 daemon.info dnsmasq[1]: using nameserver 127.0.0.1#3053
Sun Jul 27 15:59:59 2025 daemon.info dnsmasq[1]: using only locally-known addresses for test
Sun Jul 27 15:59:59 2025 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Sun Jul 27 15:59:59 2025 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Sun Jul 27 15:59:59 2025 daemon.info dnsmasq[1]: using only locally-known addresses for local
Sun Jul 27 15:59:59 2025 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Sun Jul 27 15:59:59 2025 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Sun Jul 27 15:59:59 2025 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Sun Jul 27 15:59:59 2025 daemon.info dnsmasq[1]: read /etc/hosts - 12 names
Sun Jul 27 15:59:59 2025 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 4 names
Sun Jul 27 15:59:59 2025 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.wgclient1 - 4 names
Sun Jul 27 15:59:59 2025 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Sun Jul 27 16:00:01 2025 daemon.info dnsmasq[1]: exiting on receipt of SIGTERM
Sun Jul 27 16:00:02 2025 daemon.crit dnsmasq[1]: bad option at line 1 of /tmp/dnsmasq.d.wgclient1/mark
Sun Jul 27 16:00:02 2025 daemon.crit dnsmasq[1]: FAILED to start up
The setup and client files work perfectly on the wrt21 4.8.0 firmware. It just fails totally on op24 4.8.0 beta.
1 Like
4.75 was removed
someone have 4.75op24 for glinet flint2?
thx
Exciting! This is the version I've been waiting for.... OP24 with 4.8. I'll wait for the next beta release before installing it on my Flint2.
1 Like
If anyone needs firmware 4.7.5 for MT3000 and MT6000
1 Like