My GL.iNet Mudi V2 (GL-E750V2C6) has an intermittent Repeater/Wi-Fi scanning failure that support logs suggest may be related to the wireless driver or radio interface state.
The router will sometimes scan and connect normally, but at other times Repeater scanning fails with “Operation Timed Out”, shows no networks, or the Repeater option disappears from the Internet page entirely.
I provided GL.iNet support with a diagnostic logread.tar file. Their technician said the logs contained repeated Wi-Fi errors including:
nl80211_recv_beacons ... failed: -5
and said this may indicate a Wi-Fi driver or wireless interface issue.
So far I have followed their troubleshooting instructions, including:
-
Normal router reboots
-
Restarting both Radio0 and Radio1 through LuCI
-
Attempting to restart networking through SSH
-
Repeating scans immediately after reboot
-
Capturing fresh logs while the fault was occurring
Restarting the radios did not solve the problem. At one point, after rebooting, the router’s own Wi-Fi eventually returned but the Repeater option was missing completely, so I could not even perform the requested scan.
The router is running firmware 4.3.28 / 0328release1. Support has suggested testing 4.8 Beta firmware with a clean configuration, but I am reluctant to rely on beta firmware to make a brand-new travel router perform one of its basic advertised functions.
I also enabled and configured GoodCloud so GL.iNet support can remotely inspect the router if necessary, but so far most troubleshooting has still been left for me to perform manually.
At this point I am considering returning the unit for a refund. I would be interested to know whether other Mudi V2 / E750V2 owners have experienced the same Repeater scanning or wireless-interface problem, and whether anyone has found a reliable permanent fix.
Hi,
We’re sorry for the inconvenience. Since you already have an open support ticket, we will continue following up on this case through the existing email thread rather than asking you to repeat further troubleshooting publicly.
Regarding GoodCloud, enabling it alone does not give us access to the router. We have not yet received the router’s MAC address and temporary Admin Panel password through the support ticket, so we cannot identify and remotely access the shared device.
If you would like us to check it through GoodCloud, please follow the remote-support guide, share the device with GL.iNet Technical Support , enable Auto Expire Sharing for 7 days, and send the MAC address and a temporary Admin Panel password only by replying to the existing support email. Please do not post this information publicly.
The latest log also shows that your management device was connected to the Mudi V2’s 5 GHz Wi-Fi while the Repeater was connecting to an upstream 5 GHz network on channel 157. During that Repeater reconnection, the Mudi V2 temporarily shut down its 5 GHz Wi-Fi interface. Your management device disconnected at 09:51:35 and reconnected at 09:51:59.
When this happens, the connection to the Admin Panel is interrupted. The page may therefore show an operation timeout or no network, and the Repeater section may temporarily fail to appear because the page cannot retrieve its status from the router.
For a more reliable test, please manage the Mudi V2 using either:
- The included USB-C Ethernet adapter; or
- The opposite Wi-Fi band—for example, connect your management device to the Mudi V2’s 2.4 GHz Wi-Fi while the Repeater connects to a 5 GHz upstream network. Using different SSIDs for the two bands will make it easier to select the correct one.
The Mudi V2 has relatively limited hardware resources, so scanning and reconfiguring its wireless interfaces can take some time. Please allow approximately 2–3 minutes for the operation to complete and avoid repeatedly starting another scan, disconnecting, or reconnecting during that period.
Please continue the follow-up through your existing support ticket.