GL-MT3000 unable to scan for Repeater network on FW 4.4.5

Hi everybody,

Today was my first day trying to connect to a new network with the new firmware 4.4.5 after updating from 4.2.3 this past week.
After my firmware update, using the same network that I had set up and was using before (and during) the update was working fine, however today I moved to a new hotel, and suddenly experienced problems with scanning for networks in the repeater.
The router would simply not find a single network to connect to, not even my phone hotspot, that it had previously been connected to, and was still in the list.

I ssh’d into the router and tried to manually scan for networks and got the following error messages:

Interface doesn’t accept private ioctl…
set (8BE2): Network is down
Scanning not possible

I tried to Reset the firmware, but had the exact same behavior afterwards.

Now I have rolled back to 4.2.3 and everything is working once again - though I need to set up everything once again, due to my previous reset.

Has anybody else experienced the same with firmware 4.4.5?

1 Like

Could you export log while not scan?

Hi Jerry,

I unfortunately don’t have the full log, and don’t have the possibility to recreate at the moment

But I can see from my search history that I had the following error in my logs:

bad argument #1 to ‘pairs’ (table expected/ got nil)

Hope that can help.

Could you reproduce the problem and export full log?

I have the same issue, even after downgrading and resetting. The logs are from version 4.4.5, but also tried every version down to 4.1.3. Also tried multiple browsers, and desktop + mobile. I sometimes also get an timeout error, but most of the times nothing.

See attached the log

Also gives this javascript error (firefox), but not sure if related:

Uncaught (in promise) Error: timeout of 10000ms exceeded
exports routerurl/js/app.7353d566.js:16
ontimeout routerurl/js/app.7353d566.js:61
exports routerurl/js/app.7353d566.js:61
exports routerurl/js/app.7353d566.js:61
exports routerurl/js/app.7353d566.js:24
promise callback0a06/l.prototype.request http:// routerurl/js/app.7353d566.js:10
t http:// routerurl/js/app.7353d566.js:10
exports http:// routerurl/js/app.7353d566.js:10
f http:// routerurl/js/app.7353d566.js:68
f http:// routerurl/js/app.7353d566.js:68
getSystemStatus routerurl/js/app.7353d566.js line 61 > eval:7
getSystemStatus routerurl/js/app.7353d566.js line 61 > eval:7
systemPollTimeId routerurl/js/app.7353d566.js line 61 > eval:7
setTimeout handler
getSystemStatusTimeout routerurl/js/app.7353d566.js line 61 > eval:7

I have exactly the same problem.
In repeater mode with the firmware 4.4.5 no network is found during the network search.
Back with firmware 4.2.3 it works immediately.
Same problem with the current beta 4.4.6 R1 and the current snapshot 4.5.
I have reset the settings after each firmware update.

1 Like

Same problem. Came here to see if this issue was unique.

Brand new GL-MT3000, upgraded firmware on 1st use but could not setup repeater (no SSID’s found). Assumed device was faulty but downgraded to firmware 4.2.3 and got it working. Tried various (newer) versions including Uboot without success.

LuCI does see SSIDs on newer firmware versions.

Have you checked in LuCI, to see if your Country Code is set correctly? Network > MTK WiFi. Sometimes it’s set to US, which can cause problems.

Hi JinOhChoi, sorry I meant to include that detail but yes i have. So far i’ve tried a few different (European) codes but same problem. In my example the correct country code (GB) does not work whereas I have tried FW 4.2.3 on both GB and DE with both working.

Have you tried forcing it to try either 2.4GHz or 5GHZ, rather than Auto? To see if any networks appear.

Testing against FW 4.4.6.
I can confirm forcing 2.4GHz does now show SSID’s but this is not the case for 5GHz.