Flint 4 / GL-BE14000 Wifi reconnect issues

Router
1

Hello,

I have this router since a few days and have a problem with MLO reconnects.

I’m able to connect to the MLO enabled Router with several clients without any issue. But the clients (here i a laptop) are disconnecting after a few minutes for powersaving. This works reliable for a while. But later on this does not work anymore.

So after a while reconnecting to MLO SSID (done automatically if laptop resumes) does not work anymore resp. sometimes after x retries by the NetworkManager it reconnects. But just to one band out of the three. I have to reboot the router to make it work again. After reboot it works again and client connects to all three bands again.

Error Log:

kern.err kernel: [18477.663258] WiFi@ERROR.MLME,PeerAssocReqCmmSanity() 1661: [frag] Jump to next IE: 321, (defrag=319)
kern.warn kernel: [18477.672304] 7990@WARN.MLME,BN2,PeerAssocReqCmmSanity() 1634: IE_WLAN_EXTENSION: no handler for extension_id:108
kern.debug kernel: [18477.682388] [ap_cmm_peer_assoc_req_action - 2023] assoc case set to zero
kern.notice kernel: [18477.682393] 7990@NOTICE.MLME,BN2,ap_cmm_peer_assoc_req_action() 2064: received assoc req: DA=e2:6f:e4:08:09:a0, SA=xx:xx:xx:xx:xx:xx, (wcid=1),ifname=rax2...
kern.notice kernel: [18477.696566] WiFi@NOTICE.MLO,bss_mngr_event_mld_sta_add_link() 378: pEntry(00000000e5326a8f): wcid(1) mac=xx:xx:xx:xx:xx:xx, mld(sta_idx=0,addr=xx:xx:xx:xx:xx:xx) allocated!!
kern.warn kernel: [18477.712034] WiFi@WARN.MLO,mld_entry_add_link() 4180: mld_sta_idx=0, mld_addr=xx:xx:xx:xx:xx:xx, link_id=2 insert the same pEntry=00000000e5326a8f
kern.notice kernel: [18477.725062] WiFi@NOTICE.MLO,bss_mngr_event_mld_sta_add_link() 378: pEntry(0000000000e104b7): wcid(2) mac=xx:xx:xx:xx:xx:xx, mld(sta_idx=0,addr=xx:xx:xx:xx:xx:xx) allocated!!
kern.warn kernel: [18477.740516] WiFi@WARN.MLO,mld_entry_add_link() 4180: mld_sta_idx=0, mld_addr=xx:xx:xx:xx:xx:xx, link_id=0 insert the same pEntry=0000000000e104b7
kern.notice kernel: [18477.753542] WiFi@NOTICE.MLO,bss_mngr_event_mld_sta_add_link() 378: pEntry(00000000a9ac353c): wcid(3) mac=xx:xx:xx:xx:xx:xx, mld(sta_idx=0,addr=xx:xx:xx:xx:xx:xx) allocated!!
kern.warn kernel: [18477.768997] WiFi@WARN.MLO,mld_entry_add_link() 4180: mld_sta_idx=0, mld_addr=xx:xx:xx:xx:xx:xx, link_id=1 insert the same pEntry=00000000a9ac353c
kern.notice kernel: [18477.782024] WiFi@NOTICE.MLO,bss_mngr_con_mld_conn_req() 5224: frm(0),idx(0),mld(xx:xx:xx:xx:xx:xx),link(xx:xx:xx:xx:xx:xx)
kern.notice kernel: [18477.793075] WiFi@NOTICE.MLME,ap_cmm_peer_assoc_req_action() 2548: PMKID NULL auth_mode=3, STA=xx:xx:xx:xx:xx:xx, AP=e2:6f:e4:08:09:a0,ifname=rax2
kern.notice kernel: [18477.806198] WiFi@NOTICE.MLME,record_connect_info() 12781: (caller:PeerAssocReqMloCapSanity+0x1f0c/0x4f58 [mt_wifi]): WLAN station connection establishment to 6Ghz Wifi radio failed: association error. StatusCode: 30, MAC-address: xx:xx:xx:xx:xx:xx
kern.notice kernel: [18477.828122] WiFi@NOTICE.MLO,eht_ap_mlo_peer_non_setup_links_assoc_req() 5364: [setup link=2]
kern.notice kernel: [18477.828122] ----- Start the non-setup link association -----
kern.warn kernel: [18477.842388] 7990@WARN.MLME,BN0,PeerAssocReqCmmSanity() 1634: IE_WLAN_EXTENSION: no handler for extension_id:137
kern.warn kernel: [18477.852469] 7990@WARN.MLME,BN0,PeerAssocReqCmmSanity() 1634: IE_WLAN_EXTENSION: no handler for extension_id:108
kern.debug kernel: [18477.862543] [ap_cmm_peer_assoc_req_action - 2023] assoc case set to zero
kern.notice kernel: [18477.862549] 7990@NOTICE.MLME,BN0,ap_cmm_peer_assoc_req_action() 2064: received assoc req: DA=xx:xx:xx:xx:xx:xx, SA=xx:xx:xx:xx:xx:xx, (NS) (wcid=2),ifname=ra2...
kern.notice kernel: [18477.876967] WiFi@NOTICE.MLME,ap_cmm_peer_assoc_req_action() 2548: PMKID NULL auth_mode=0, STA=xx:xx:xx:xx:xx:xx, AP=xx:xx:xx:xx:xx:xx,ifname=ra2
kern.notice kernel: [18477.889990] WiFi@NOTICE.MLME,record_connect_info() 12781: (caller:PeerAssocReqMloCapSanity+0x1f0c/0x4f58 [mt_wifi]): WLAN station connection establishment to 2.4Ghz Wifi radio failed: association error. StatusCode: 30, MAC-address: xx:xx:xx:xx:xx:xx
kern.warn kernel: [18477.912095] WiFi@WARN.MLO,eht_ap_mlo_postprocess_non_setup_link_assoc_rsp() 5258: Warn: non-setup link assoc fail, status code is 0x1e
daemon.notice wappd[21454]: [MISC][wdev_sta_cnnct_rej_handle.3745]: assoc_status_code = 30: 0
daemon.notice wappd[21454]: [MISC][wdev_sta_cnnct_rej_handle.3747]: report_unsuccessful_association = 0
daemon.notice wappd[21454]: [MISC][wdev_sta_cnnct_rej_handle.3748]: max_supporting_rate = 0
daemon.notice wappd[21454]: [MISC][wdev_sta_cnnct_rej_handle.3756]: send_failed_assoc_frame = 0
kern.warn kernel: [18477.924183] 7990@WARN.MLME,BN1,PeerAssocReqCmmSanity() 1634: IE_WLAN_EXTENSION: no handler for extension_id:137
kern.warn kernel: [18477.934263] 7990@WARN.MLME,BN1,PeerAssocReqCmmSanity() 1634: IE_WLAN_EXTENSION: no handler for extension_id:108
kern.debug kernel: [18477.944337] [ap_cmm_peer_assoc_req_action - 2023] assoc case set to zero
kern.notice kernel: [18477.944343] 7990@NOTICE.MLME,BN1,ap_cmm_peer_assoc_req_action() 2064: received assoc req: DA=xx:xx:xx:xx:xx:xx, SA=xx:xx:xx:xx:xx:xx, (NS) (wcid=3),ifname=rai2...
kern.notice kernel: [18477.958852] WiFi@NOTICE.MLME,ap_cmm_peer_assoc_req_action() 2548: PMKID NULL auth_mode=0, STA=xx:xx:xx:xx:xx:xx, AP=xx:xx:xx:xx:xx:xx,ifname=rai2
kern.notice kernel: [18477.971978] WiFi@NOTICE.MLME,record_connect_info() 12781: (caller:PeerAssocReqMloCapSanity+0x1f0c/0x4f58 [mt_wifi]): WLAN station connection establishment to 5Ghz Wifi radio failed: association error. StatusCode: 30, MAC-address: xx:xx:xx:xx:xx:xx
daemon.notice wappd[21454]: [MISC][wdev_sta_cnnct_rej_handle.3745]: assoc_status_code = 30: 0
daemon.notice wappd[21454]: [MISC][wdev_sta_cnnct_rej_handle.3747]: report_unsuccessful_association = 0
daemon.notice wappd[21454]: [MISC][wdev_sta_cnnct_rej_handle.3748]: max_supporting_rate = 0
daemon.notice wappd[21454]: [MISC][wdev_sta_cnnct_rej_handle.3756]: send_failed_assoc_frame = 0
kern.warn kernel: [18477.993911] WiFi@WARN.MLO,eht_ap_mlo_postprocess_non_setup_link_assoc_rsp() 5258: Warn: non-setup link assoc fail, status code is 0x1e

I saw a similar issue/error log here but for the Slate 7: https://www.reddit.com/r/GlInet/comments/1udiij2/slate_7_pro_5ghz_disconnects/

I didn’t test much yet. So if this issue would arise with single band too.

What can I do to fix this? I didn’t configure anything special yet. Everything is set to default beside enabling MLO for my Wifi7 clients.

Kind regards.

2

can you try disabling randomised BSSID?

4

Hi,

From the logs, the failure appears to occur during the Wi-Fi/MLO association process when the laptop tries to reconnect after sleep or power saving.
It show that StatusCode: 30 during the association attempts on the MLO links, followed by non-setup link assoc fail , which indicates that the router is temporarily rejecting the association request at that point.

If convenient, could you please also use the same laptop to connect to both the MLO and a regular single-band SSID (such as a separate 5 GHz or 6 GHz) and repeat the sleep/wake test several times to confirm whether the reconnection issue only occurs under MLO.

If the issue happens again, could you please do not reboot the router immediately. If another MLO-capable device is available, please also check whether it can still connect normally at that time.
After that, you may also try disabling and re-enabling MLO/Wi-Fi and let us know whether this restores the connection without rebooting the whole router.

If the issue can be reproduced again, please export the system log and send it to us via private message.

image
image498×184 14.2 KB

Thank you for your understanding and support.

5

pwned reports the problem and even logs.

What's the problem with GL.Inet starting to investigate on its own? Don't You have Flint4? Don't you have devices to connect using MLO?
You have a beautifully explained problem by user Flint4 … :wink:

6

Hi,

thx for reply.

Where do I do set this? I need the correct syntax for this and which file I have to edit. Within LuCI i can only change SSID.

O.K. I dont use the router regulary yet. So I’ll try to use it more to reproduce the failure.

7

In the Admin Panel, navigate to Wireless, as illustrated below:

image
image1304×775 41 KB

image
image760×498 13.3 KB

8

Thx, I’ll try if I don’t need to collect further data. For now I have reproduced the behaviour already. I’ll now try same without MLO.

EDIT: So I’ve tested a while with single band only. I had no reconnect fail. But over time it seems to take longer to get reconnected. Maybe it is related. I sent this log to @charles2 as the MLO log.

The BSSID approach I will test tomorrow.

2 Likes
9

Hi,

Thank you for providing the additional logs and test results.

We have received the information. Based on the current logs and test results, the issue appears to be related to the MLO Wi-Fi reconnection process, so we will forward the logs to the relevant team for further investigation.

In the meantime, you can also try disabling Randomized BSSID and see whether it makes any difference to the reconnection behavior.
Could you also let us know the laptop model and the exact Wi-Fi adapter model it is using?

Since the single-band connection appears to be more stable in your current testing, you may continue using a regular 5 GHz or 6 GHz Wi-Fi connection.
Thank you again for your patience and for helping us.

10

Hi,

thx for forwarding the issue and hopefully there will be a solution for it.

Indeed initially I thought it could be an issue how fast my laptop is connecting to wifi. But on other routers I get connected instantly. So it shouldn’t be an issue for modern routers.

The laptop is one of those Intel EVO certified ones with instant on/wake up (ASUS VivoBook S5606; wifi is identifyed as Intel BE201). So its basically lid up, screen on, wifi connected already after authentication. Very snappy. On my other routers this works reliable (amongst others a Flint2). While 6G on Flint4 worked without connection fail I had the feeling that connecting to it is slowing over time or at least it was sometimes slower resp. not the connection speed was not consistent.

Given this oberservation it could be that there is an issue with band selection (so router offers unsupported bands to client card)? But that’s just a guess from the logs. I don’t really know how the router is actually configured with standard settings yet (regarding channel selection, channel width, etc.).

I could not test as much as I wanted bc. I’m time constrained atm. On Weekend I’ll try the BSSID approach. I don’t have time to migrate my network to Flint4 yet. So I cannot test extensively.

Kind regards

11

Hi,

Thank you for the information and testing.

The logs and your observations have already given us useful information about the MLO reconnection behavior, and we will continue following this up with the relevant team.

Since the regular single-band Wi-Fi connection appears to be more stable, you may continue using a normal 5 GHz or 6 GHz Wi-Fi connection for now while we investigate the MLO behavior further.

Thank you for your patience and for helping us investigate this issue.

12

I tested on weekend disabling random BSSID. I didn’t change the outcome.

1.) It does not matter which OS I use either Windows or Linux.

2.) I would also say that the Intel BE201 Wifi (card/drivers/firmware) is not the best after my testing. Or maybe the Intel card does not play so nice with Mediatek SoC. Meanwhile I made a BIOS/UEFI update. But that didn’t change anything.

I hope you’ll find a solution. If you want me to test things just tell me.

Kind regards.

13

Hi,

Thank you for the additional testing and update.

At this point, the issue still appears to be related to the MLO reconnection/compatibility behavior, possibly involving the interaction between the Intel BE201 and the MediaTek Wi-Fi platform.
We will pass these latest results to the relevant team and continue the investigation.

Thank you again for your patience and for all the detailed testing you have done.

14

I activated my onboard wifi card of my PC.

Network controller [0280]: MEDIATEK Corp. MT7925 802.11be 160MHz 2x2 PCIe Wireless Network Adapter [Filogic 360] [14c3:7925]

I was able to reproduce the exact same behavior/error with it. So at least this is not an Intel wifi card issue per-se as I thought/feared already. But it lets open a bunch of other things causing this issue. Maybe this observation helps to narrow things a bit more.

EDIT: Made a typo the “not” was wrong! I was able to reproduce it!

15

Edit: I have resolved my MLO issue it was an issue with client device. However my other issue with WireGuard speeds still remains:

In addition to this I get half throughput from all WiFi clients going out through WireGuard client tunnel but Ethernet clients get full throughput / speed. I actually have worse network than I did on Flint 2 at present

18

Hi,

Thank you for the update.

Since the same MLO reconnection issue occurs with this adapter, it does not appear to be specific to the Intel BE201. We have added this result to the ongoing investigation.

Could you please let us know how you reproduced the issue with the MT7925—for example, how long the router had been running, how many sleep/wake cycles it took, and whether reconnection failed completely or connected on only one band?

Thank you for your support and understanding.