From: KeithG <ys3al35l@gmail.com>
To: brcm80211@lists.linux.dev
Subject: brcmfmac disconnects AP mode while scanning
Date: Tue, 20 Feb 2024 18:26:34 -0600 [thread overview]
Message-ID: <CAG17S_NgSOPg72_oNOvGsNr_nt5xmbNu4MGPDuVtb2UWjUnnJg@mail.gmail.com> (raw)
I posted this over on the linux-wireless board as well but did not
learn much towards a fix.
We are using iwd to manage the wireless on RPis. We discovered that
when the brcmfmac in the Pi is set to be in AP mode and then iwd
initiates a scan on the interface, all clients on the AP are
disconnected. This is unexpected and does not happen when
wpa_supplicant is used then scans.
I have been discussing this with one of the IWD devs and he pinpointed
it to the fact that when iwd scans, it is using 'passive scan' to scan
for ssids and when it does it shuts down the AP. We do not witness
this behavior with intel cards and it also does not happen when
wpa_supplicant is used instead of iwd and then it scans for ssids. The
dev determined that wpa_suplicant uses 'active scan' and when it scans
for ssids whereas iwd uses 'passive scan'. Our Pis are stable with
wpa_supplicant/Hostapd, but not with iwd. We prefer using iwd.
He passed on some patches that change the behavior of iwd to only use
'active scans'. With iwd built with these patches (only to use active
scan) the AP is stable when iwd scans for ssids.
This behavior/modification is not consistent with other cards, though.
The question is: why are we seeing this behavior on brcmfmac? Is
wpa_suplicant doing it properly and iwd not? If so, why? Could the
brcmfmac driver be patched so that iwd will work properly with a
passive scan and not disconnect all AP connected clients?
Keith
reply other threads:[~2024-02-21 0:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAG17S_NgSOPg72_oNOvGsNr_nt5xmbNu4MGPDuVtb2UWjUnnJg@mail.gmail.com \
--to=ys3al35l@gmail.com \
--cc=brcm80211@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;
as well as URLs for NNTP newsgroup(s).