From: Denis Kenzior <denkenz@gmail.com>
To: Daniel Barter <danielbarter@gmail.com>
Cc: iwd@lists.linux.dev
Subject: Re: roaming issues on a residential LAN with multiple APs
Date: Sun, 26 Nov 2023 23:00:44 -0600 [thread overview]
Message-ID: <8212f44e-d7f1-4b5c-9ffb-043a01b4d16b@gmail.com> (raw)
In-Reply-To: <CAJODeCDu-85P54m16FanJftz2mC-fVGN-PXrwk4q+yS8n6mwFQ@mail.gmail.com>
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?
Regards,
-Denis
next prev parent reply other threads:[~2023-11-27 5:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 19:46 roaming issues on a residential LAN with multiple APs Daniel Barter
2023-11-25 23:28 ` Denis Kenzior
2023-11-26 0:32 ` Daniel Barter
2023-11-27 5:00 ` Denis Kenzior [this message]
2023-11-29 12:49 ` James Prestwood
2023-11-29 17:47 ` Daniel Barter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8212f44e-d7f1-4b5c-9ffb-043a01b4d16b@gmail.com \
--to=denkenz@gmail.com \
--cc=danielbarter@gmail.com \
--cc=iwd@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox