Unable to connect Beryl 7 overnight

Greetings,

I recently got a Beryl 7 and it has been running at least for a week. Today I woke up and all my devices were unable to connect to the router via wifi. It only worked after the router was restarted.

Relevant Information:

Router: Beryl 7 GL-MT3600BE

Firmware: v4.8.5

Internet: WLAN (192.168.100.0/24)

DNS: mullvad-doh configured from the router interface, adguard home is not enabled

DHCP: Yes

Other relevant information: Only 5ghz wifi is enabled. Wireguard client and server is enabled. Around 8 devices are connected via wifi, no LAN connections. No plug-ins installed, everything else should be default.

Please let me know if I need to provide more information.

Sounds similar to the original post in this thread maybe:

Bare in mind updating to 4.8.6 Beta won’t fix the situation , i have similar issues ( see SSID post).

Will be updating my original post with the findings today when i get home.

1 Like

SSID was still visible, but connection was not possible.

Worth noting the device did not restart itself, I had to unplug it.

Yeah,i had same issues ,updating firmware to 4.8.6 beta made it slightly more stable but issues are still there ,only difference is it does seem to restart automatically.

1 Like

Thanks for the clarification.

I wouldn’t say 4.8.6 beta has a fix for it then, instead of gl-inet devs having the device restart, they should be able to find a root cause for the behavior and fix it.

If you upgrading to the stable version 4.8.6 doesn't solve the problem?

If that's the case, when WiFi problems occur, could you connect to the router's LAN port, access the GUI, export the router logs, and send them to us for inspection?

Just updated to stable 4.8.6 today. Since the issue takes a while to show, I’ll have to wait for it to happen again.

Will post here any findings.

I started experiencing jitter during calls today, took the opportunity to update to 4.8.7 and restart the device. I’m not sure the jitter was introduced by router or VPN.

Device had been running for 11 days and the issue hasn’t happened again. Will continue to monitor.

1 Like