Re: roaming issues on a residential LAN with multiple APs

[James Prestwood <prestwoj@gmail.com>]

Hi Daniel,

On 11/26/23 21:00, Denis Kenzior wrote:
> Hi Daniel,
>
> On 11/25/23 18:32, Daniel Barter wrote:
>> here are my logs:
>> https://gist.github.com/danielbarter/65ddf6aee78546a0e8f9e2d3af65308c
>>
>> notice that this is a mix of iwd 2.4 (my distro default) and iwd 2.8.
>>
>> Default roaming thresholds are in the 70s right? I am getting down to
>> -90dBm without a roam happening.
>
> Default thresholds are -70 db for 2.4 Ghz and -76 for 5Ghz.
>
> I'm not seeing any CQM events in your log, except for this one:
>
> Nov 24 16:34:15 jasper iwd[768]: src/netdev.c:netdev_mlme_notify() 
> MLME notification Notify CQM(64)
> Nov 24 16:34:15 jasper iwd[768]: src/netdev.c:netdev_cqm_event() 
> Beacon lost event
> Nov 24 16:34:15 jasper iwd[768]: src/netdev.c:netdev_mlme_notify() 
> MLME notification Notify CQM(64)
> Nov 24 16:34:15 jasper iwd[768]: src/netdev.c:netdev_cqm_event() 
> Beacon lost event
> Nov 24 16:34:15 jasper iwd[768]: src/netdev.c:netdev_link_notify() 
> event 16 on ifindex 3
> Nov 24 16:34:15 jasper iwd[768]: src/netdev.c:netdev_mlme_notify() 
> MLME notification Del Station(20)
> Nov 24 16:34:15 jasper iwd[768]: src/netdev.c:netdev_mlme_notify() 
> MLME notification Deauthenticate(39)
> Nov 24 16:34:15 jasper iwd[768]: 
> src/netdev.c:netdev_deauthenticate_event()
> Nov 24 16:34:15 jasper iwd[768]: src/netdev.c:netdev_mlme_notify() 
> MLME notification Disconnect(48)
> Nov 24 16:34:15 jasper iwd[768]: src/netdev.c:netdev_disconnect_event()
> Nov 24 16:34:15 jasper iwd[768]: Received Deauthentication event, 
> reason: 4, from_ap: false
> Nov 24 16:34:15 jasper iwd[768]: 
> src/station.c:station_disconnect_event() 3
> Nov 24 16:34:15 jasper iwd[768]: src/station.c:station_disassociated() 3
> Nov 24 16:34:15 jasper iwd[768]: 
> src/station.c:station_reset_connection_state() 3
> Nov 24 16:34:15 jasper iwd[768]: 
> src/station.c:station_roam_state_clear() 3
> Nov 24 16:34:15 jasper iwd[768]: src/station.c:station_enter_state() 
> Old State: connected, new state: disconnected
>
> Basically a lost-beacon event comes in (twice for some reason) and 
> we're disconnected almost instantly after that.  There's no other CQM 
> events that would indicate low signal strength where iwd can actually 
> take some action.  Try setting a more aggressive roam threshold and 
> see if that helps?  man 5 iwd.config, RoamThreshold and RoamThreshold5G.
>
>>
>> kernel version is 6.6.0.
>>
>
> It could also be the kernel folks made some change that broke this. 
> For example, this looks to be touching the general area:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/commit/?id=37c20b2effe987b806c8de6d12978e4ffeff026f 
>
>
> Try reverting or using a version prior to that commit?

It does appear _something_ is wrong with QCM notifications in the 
kernel. There was an RFC fix with one user commenting that roaming in 
wpa_supplicant is broken as of 6.1. I am able to roam fine on ath11k 
with a stock 6.2 Ubuntu kernel so not sure if its only some drivers or what.

https://lore.kernel.org/linux-wireless/20231106231715.3a506ac2dadb.Ie774b85b9d4ff934a1236e77096cb9c6c9fe6561@changeid/

Thanks,

James