[brcmfmac] Pi 5 host-requested 2.4→5 GHz roam emits firmware status 19, then drops the old connection

Aperta
#7,758 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c, linux

Direzione di ricerca

Start with the brcmfmac roam handler and the firmware-event decoding under drivers/net/wireless/broadcom/brcm80211/brcmfmac/, since the report states the handler notifies cfg80211 only on success. Reproduce the failing wpa_cli roam on the Pi 5 with join_event_debug=Y and compare against the stock-module control the reporter plans. Done means an answer on what ROAM status 19/reason 0 means for FWID 01-b677b91b, whether the join iovar is valid while associated, and a decision on reporting a failed roam so the old association survives.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Describe the bug

A Raspberry Pi 5 can connect from a disconnected state to the 5 GHz radio of a Zyxel EX5601-T1, but a host-requested roam from the same AP’s 2.4 GHz radio to its 5 GHz radio stalls. The behaviour was observed on channels 36 and 100.

On channel 36, an independent capture showed five probes from the Pi and replies from the AP, but no authentication, association, or reassociation frames between them. The fresh-join control on the same channel showed successful authentication, association, and a four-way handshake.

During the roam, the firmware emitted a non-success ROAM event approximately 108 ms after accepting the join command. The old association was still reported shortly before wpa_supplicant timed out and disconnected locally at about 10 seconds. Whether the old link still carried IP traffic was not measured.

Expected behaviour is either a successful roam or, if the target cannot be joined and the old link is still usable, a failed roam that leaves the old connection intact.

Steps to reproduce the behaviour
  1. Configure a dual-band Zyxel EX5601-T1 with the same SSID and security on both radios. The main test used channel 1 and channel 36, with WPA2-PSK-SHA256, CCMP, and required PMF.
  2. From a disconnected state, connect the Pi directly to the 5 GHz BSSID. Verify that wpa_supplicant reaches COMPLETED.
  3. Disconnect and connect to the 2.4 GHz BSSID. Verify the current association and confirm the 5 GHz target appears in the supplicant scan results. If the active network was pinned to 2.4 GHz, clear the runtime pin without disconnecting and verify the current association again.
  4. Run sudo wpa_cli -i wlan0 roam <TARGET_5_GHZ_BSSID>. It returns OK, but the target never reaches COMPLETED. Monitor the kernel log, supplicant log, and iw dev wlan0 link for 15 seconds.
Device (s)

Raspberry Pi 5

System
  • Raspberry Pi 5, ARM64, onboard BCM4345/6-class SDIO Wi-Fi
  • Kernel 6.12.115+rpt-rpi-2712, package 1:6.12.115-1+rpt1
  • brcmfmac with a local diagnostic module override, roamoff=1 and join_event_debug=Y
  • Wi-Fi firmware 7.45.265 (28bca26 CY), FWID 01-b677b91b
  • Access point Zyxel EX5601-T1
Logs

Channel 36, relative to the driver submitting the roam request. These are normalized excerpts, not verbatim logs.

+0.000 s   brcmfmac join iovar returned 0
+0.108 s   Firmware ROAM event, status=19, reason=0, event address all zeros
+9.078 s   iw link still reported the original 2.4 GHz association
+9.999 s   wpa_supplicant reported an authentication timeout for the target
+10.003 s  wpa_supplicant reported a locally generated disconnect
+12.889 s  Pi completed a connection to a different AP

On channel 100, the same firmware status appeared approximately 16 ms after join submission. An overnight trace contained 15 matching event-and-timeout pairs during automatic roam attempts to the same target.

Additional context

Could you confirm what firmware ROAM status 19, reason 0 means on FWID 01-b677b91b, and whether the join iovar is the intended command when already associated?

The brcmfmac roam handler appears to notify cfg80211 only on success. Is there an intended way to complete a failed host-requested roam while preserving a usable old association?

A stock-module comparison is planned. Only normalized excerpts are included to avoid disclosing identifiers from the local network and nearby networks.

Lingua principale
C
Stelle
13.3k
Fork
5.5k
Merge medio
4g 10h
PR unite (30g)
31

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di raspberrypi/linux

Tutte le issue di raspberrypi/linux

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.