Sascha Hauer <s.hauer@xxxxxxxxxxxxxx> writes: >> > There still is a problem with the RTL8822cu chipset I have here. When >> > using NetworkManager I immediately lose the connection to the AP after >> > it has been connected: >> > >> > [ 376.213846] wlan0: authenticate with 76:83:c2:ce:81:b1 >> > [ 380.085463] wlan0: send auth to 76:83:c2:ce:81:b1 (try 1/3) >> > [ 380.091446] wlan0: authenticated >> > [ 380.108864] wlan0: associate with 76:83:c2:ce:81:b1 (try 1/3) >> > [ 380.136448] wlan0: RX AssocResp from 76:83:c2:ce:81:b1 >> > (capab=0x1411 status=0 aid=2) >> > [ 380.202955] wlan0: associated >> > [ 380.268140] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready >> > [ 380.275328] wlan0: Connection to AP 76:83:c2:ce:81:b1 lost >> > >> > That doesn't happen when using plain wpa_supplicant. This seems to go >> > down to cd96e22bc1da ("rtw88: add beacon filter support"). After being >> > connected I get a BCN_FILTER_CONNECTION_LOSS beacon. Plain >> > wpa_supplicant seems to go another code patch and doesn't activate >> > connection quality monitoring. >> > >> > The connection to the AP works fluently also with NetworkManager though >> > when I just ignore the BCN_FILTER_CONNECTION_LOSS beacon. >> > >> > Any idea what may be wrong here? >> > >> >> Please reference to below patch to see if it can work to you. >> >> https://lore.kernel.org/linux-wireless/20221124064442.28042-1-pkshih@xxxxxxxxxxx/T/#u > > Great! That solves this issue \o/ Awesome, great work Ping and Ji-Pin! -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches