Brand new MT3000. Just updated to 4.2.0. It will not connect to some wifi networks.
I have access to two wireless networks, which I do not control.
I cannot connect to either of them. Passwords are correct…I’m posting this connected directly to one of the networks on my laptop. I tried the mac clone, it’s my simple apartment wifi using netgear routers. There is probably no ACL or mac filter.
“Connection failed, will retry later…”
I started the wifi hotspot on my phone, and it connected just fine…
How do we investigate?
smiths
March 29, 2023, 10:11am
2
If laptop and router both connecting, probably avoid MAC cloning, to avoid tearing your hair out late at night some months ahead. As your phone connects, it would suggest not needed, but good “try” as a diagnostic attempt.
Reboot the router and let it settle.
I am guessing it is not remembering your wifi settings.
So go into Internet, let the scan complete. Do you see the wifi in the list? Do you see 5Ghz or 2.4Ghz or both?
I would try connecting to the 2.4Ghz first, gonna be lousy bandwidth in a shared aprartment, but proves the credntials etc.
If you get the fail to connect, then pull the logs from the logs menu option, it should show the router trying to connect, and hopefully what is going wrong.
Also pop into Upgrade and note the software version running.
Rinse and repeat n the 5GHz channel.
That should allow the really clever people on the forumsee what is happening.
Simon
The 4.2.1 Beta firmware did fix a number of issues, maybe try that, Do not Keep Setting to avoid issues.
There is an SSID-Regular (but does not say Regular) and SSID-5G. I’ve tried both. I’ve tried turning off my 2.4ghz and 5ghz radios in various configurations.
Already updated to 4.2.0. I’ll try the beta.
Which log would be useful?
See below for what might be relevant from the System log
Wed Mar 29 10:36:05 2023 daemon.info repeater: (/usr/sbin/repeater:1122) prepare connect ‘MYSSID(MAC)’, WPA2PSK/AES channel 10
Wed Mar 29 10:36:05 2023 daemon.info repeater: (/usr/sbin/repeater:311) mtk: Set DFS CAC false
Wed Mar 29 10:36:05 2023 daemon.info repeater: (/usr/sbin/repeater:1222) connecting ‘MYSSID MAC’…
Wed Mar 29 10:36:05 2023 daemon.notice netifd: Wireless device ‘mt798111’ is now down
Wed Mar 29 10:36:05 2023 kern.info kernel: [ 8319.449781] device ra0 left promiscuous mode
Wed Mar 29 10:36:05 2023 kern.info kernel: [ 8319.454220] br-lan: port 2(ra0) entered disabled state
Wed Mar 29 10:36:05 2023 kern.warn kernel: [ 8319.490035] 7981@C13L2,Set_DisConnectAllSta_Proc() 22360: Send DeAuth (Reason=2) to 64:bc:58:b4:d4:80
Wed Mar 29 10:36:05 2023 kern.warn kernel: [ 8319.504386] 7981@C01L2,wifi_sys_disconn_act() 1002: wdev_idx=0
Wed Mar 29 10:36:05 2023 kern.notice kernel: [ 8319.510676] 7981@C08L3,hw_ctrl_flow_v2_disconnt_act() 172: wdev_idx=0
Wed Mar 29 10:36:05 2023 kern.warn kernel: [ 8319.517969] 7981@C13L2,MacTableDeleteEntry() 1793: Del Sta:64:bc:58:b4:d4:80
Wed Mar 29 10:36:05 2023 kern.warn kernel: [ 8319.597464] 7981@C01L2,RTMP_COM_IoctlHandle() 1511: → CMD_RTPRIV_IOCTL_VIRTUAL_INF_INIT
Wed Mar 29 10:36:05 2023 kern.warn kernel: [ 8319.605572] 7981@C01L2,RTMP_COM_IoctlHandle() 1488: → CMD_RTPRIV_IOCTL_VIRTUAL_INF_UP
Wed Mar 29 10:36:05 2023 kern.notice kernel: [ 8319.613606] WiFi@C01L3,wifi_sys_open() 856: wdev idx = 4
Wed Mar 29 10:36:05 2023 kern.notice kernel: [ 8319.619218] 7981@C18L3,BuildChannelList() 484:
Wed Mar 29 10:36:05 2023 kern.notice kernel: [ 8319.623792] 7981@C23L3,operate_loader_phy() 394: oper_cfg: prim_ch(10), ht_bw(0), extcha(0), vht_bw(0), cen_ch_2(0), PhyMode=78!
Wed Mar 29 10:36:05 2023 kern.notice kernel: [ 8319.635391] 7981@C23L3,operate_loader_phy() 408: oper_dev after adjust: bw(0), prim_ch(10), cen_ch_1(10), cen_ch_2(0),ext_cha(0)!
Wed Mar 29 10:36:05 2023 kern.notice kernel: [ 8319.647062] 7981@C23L3,operate_loader_phy() 428: oper_radio after decision: bw(0), prim_ch(10), cen_ch_1(10), cen_ch_2(0)!
Wed Mar 29 10:36:05 2023 kern.warn kernel: [ 8319.658359] WiFi@C00L2,dump_ht_cap() 29: Caller: wlan_operate_init+0xbc/0x160 [mt_wifi]
Wed Mar 29 10:36:05 2023 kern.debug kernel: [ 8319.666386] wdev_attr_update(): wdevId4 = 92:83:c4:27:86:d8
Wed Mar 29 10:36:05 2023 kern.notice kernel: [ 8319.671984] 7981@C08L3,hw_ctrl_flow_v2_open() 13: wdev_idx=4
Wed Mar 29 10:36:05 2023 kern.warn kernel: [ 8319.678072] WiFi@C00L2,dump_ht_cap() 29: Caller: dump_ht_cap+0x10/0x20 [mt_wifi]
Wed Mar 29 10:36:05 2023 kern.info kernel: [ 8319.685548] extif_set_dev(apcli0)
Wed Mar 29 10:36:05 2023 kern.info kernel: [ 8319.688865] mtk_ppe_dev_register_hook : ineterface apcli0 register (3)
Wed Mar 29 10:36:05 2023 kern.err kernel: [ 8319.696646] 7981@C12L1,Set_ApCliPMFMFPC_Proc() 2003: [PMF]: MFPC=1, MFPR=0, SHA256=0
Wed Mar 29 10:36:05 2023 daemon.notice netifd: Interface ‘wwan’ is enabled
Wed Mar 29 10:36:05 2023 kern.debug kernel: [ 8319.708593] SetApCliEnableByWdev: I/F(apcli0) (enable = 1)
Wed Mar 29 10:36:05 2023 kern.info kernel: [ 8319.721040] br-lan: port 2(ra0) entered blocking state
Wed Mar 29 10:36:05 2023 kern.info kernel: [ 8319.726219] br-lan: port 2(ra0) entered disabled state
Wed Mar 29 10:36:05 2023 kern.info kernel: [ 8319.731764] device ra0 entered promiscuous mode
Wed Mar 29 10:36:05 2023 kern.info kernel: [ 8319.736540] br-lan: port 2(ra0) entered blocking state
Wed Mar 29 10:36:05 2023 kern.info kernel: [ 8319.741693] br-lan: port 2(ra0) entered forwarding state
Wed Mar 29 10:36:05 2023 kern.notice kernel: [ 8320.001505] 7981@C08L3,ap_peer_auth_req_at_idle_action() 717: AUTH - MBSS(0), Rcv AUTH seq#1, Alg=0, Status=0 from [wcid=1023]64:bc:58:b4:d4:80
Wed Mar 29 10:36:05 2023 kern.debug kernel: [ 8320.014416] entrytb_aid_aquire(): found non-occupied aid:4, allocated from:4
Wed Mar 29 10:36:05 2023 kern.warn kernel: [ 8320.021478] 7981@C13L2,MacTableInsertEntry() 1537: New Sta:64:bc:58:b4:d4:80
Wed Mar 29 10:36:05 2023 kern.notice kernel: [ 8320.038813] 7981@C08L3,ap_cmm_peer_assoc_req_action() 1647: Recv Assoc from STA - 64:bc:58:b4:d4:80
Wed Mar 29 10:36:05 2023 kern.notice kernel: [ 8320.048080] 7981@C08L3,ap_cmm_peer_assoc_req_action() 2170: ASSOC Send ASSOC response (Status=0)…
Wed Mar 29 10:36:05 2023 kern.notice kernel: [ 8320.057164] 7981@C01L3,wifi_sys_conn_act() 1115: wdev idx = 0
Wed Mar 29 10:36:05 2023 kern.notice kernel: [ 8320.063189] 7981@C08L3,hw_ctrl_flow_v2_connt_act() 215: wdev_idx=0
Wed Mar 29 10:36:06 2023 kern.notice kernel: [ 8320.184501] 7981@C15L3,WPABuildPairMsg1() 5278: <=== send Msg1 of 4-way
Wed Mar 29 10:36:06 2023 kern.notice kernel: [ 8320.207281] 7981@C15L3,PeerPairMsg2Action() 6197: ===>Receive msg 2
Wed Mar 29 10:36:06 2023 kern.notice kernel: [ 8320.214006] 7981@C15L3,WPABuildPairMsg3() 5555: <=== send Msg3 of 4-way
Wed Mar 29 10:36:06 2023 kern.notice kernel: [ 8320.220630] 7981@C15L3,PeerPairMsg4Action() 6627: ===>Receive msg 4
Wed Mar 29 10:36:06 2023 kern.warn kernel: [ 8320.232181] 7981@C15L2,PeerPairMsg4Action() 6989: AP SETKEYS DONE(ra0) - AKMMap=WPA2PSK, PairwiseCipher=AES, GroupCipher=AES, wcid=1 from 64:bc:58:b4:d4:80
Wed Mar 29 10:36:06 2023 kern.warn kernel: [ 8320.232181]
Wed Mar 29 10:36:06 2023 kern.debug kernel: [ 8320.323777] BcnCheck start after 200 ms (ra0)
Wed Mar 29 10:36:06 2023 daemon.notice netifd: Wireless device ‘mt798111’ is now up
Wed Mar 29 10:36:06 2023 daemon.notice netifd: Network device ‘ra0’ link is up
Beta firmware update solved it! I can connect now.
danull
March 29, 2023, 8:57pm
6
Sounds an awful lot like the issues I posted about recently. Unfortunately the wifi was not stable on the 4.2.1 beta code, but I see it is a release 2 so maybe it is better.
alans
March 29, 2023, 9:25pm
7
I’ve just tried v4.2.1 Beta release 2, as well as 4.2.1 snapshot 28 Mar 2023 on my Beryl AX and DFS channels aren’t working (140 is the last channel visible ). I’ve tested with DE and UK country codes.
Can’t recall correctly, but was this mentioned as already fixed? If so, any suggestions to try?
1 Like
I’ve been using it all day with no issues!
I’m doing some research…
I have VPN on my guest network only. Can I block internet on the guest network with the VPN is down? It could go down and I’d guests would never notice…
alans
March 30, 2023, 6:49am
11
This is super useful @Aulinho !
Do you mind sharing the source link so we can see the full list?
alans
April 6, 2023, 6:31am
13
@danull @mysticle31
Glinet staff has just confirmed there’s a bug connecting the Repeater to 5G networks when using MAC clone/random.
Turning that off did seem to fix the issue here, how about on your side?
1 Like
Any more info on this? I’ve just upgraded my MT3000 to 4.2.2. 5G repeater works on one of my APs, but not on the other. 2.4G works on both.
Dipin
June 1, 2023, 6:26am
15
Hi, Can you share more information?
1.What is the AP model that does not work?
2.Does it work before upgrading to 4.2.2 firmware?
The AP model that does not work on 5G is the Technicolor CGM4331 provided by Shaw in Canada:
Shaw's Fibre+ Gateway 2.0 comes with the latest WiFi technology and features, including support for WiFi 6 and 2.5 Gbps Ethernet. This article covers the key features, available connections and hardware specifications of the Fibre+ Gateway 2.0. ...
Unfortunately, I did not try to connect before I upgraded.
Are there error messages in the System Log when trying to connect over 5GHz?
On the XB7 Gateway, what channel is the 5GHz wifi broadcasting on? Is the GL-MT3000 able to scan and see the SSID?
I do not work for and I am not directly associated with GL.iNet
1 Like
Are there error messages in the System Log when trying to connect over 5GHz?
Here’s is what I can see from the System Log:
On the XB7 Gateway, what channel is the 5GHz wifi broadcasting on? Is the GL-MT3000 able to scan and see the SSID?
Both the XB7 and the MT3000 are broadcasting on 44. Here’s a scan from Wireless Diagnostics on my Mac:
Yes, the MT3000 sees and connects to the XB7 on 5G, then a few seconds later complains that there is no internet access. With 2.4G this does not happen.
(Apologies for the multiple posts. As a new user I can only do one screenshot per post)