Steam Deck OLED: wpa_supplicant backend repeatedly joins an access point 50 dB weaker than another on the same SSID; iwd does not

Aperta
  • Qualcosa non va?
#3,059 1 commento 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
linux
Ambito
networking

Direzione di ricerca

Compare SteamOS behavior with the forced wpa_supplicant backend and iwd using the reproduction steps and the journal observations in the report. Start by investigating how NetworkManager selects an access point and handles the pending scan and bgscan setting. Done means the Deck reliably chooses the stronger AP or moves to it when the current link is poor.

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

Descrizione

Your system information
  • Steam client version: 1792618285
  • SteamOS version: 3.9.5, build 20261023.100
  • Opted into Steam client beta?: No
  • Opted into SteamOS beta?: No
  • Have you checked for updates in Settings > System?: Yes
Please describe your issue in as much detail as possible:

Two access points share one SSID and password, both WPA2-PSK with CCMP, with Ethernet backhaul:

  • AP A: ASUS RT-AC68U, Wi-Fi 5, channel 149, 80 MHz, -27 dBm at the Deck
  • AP B: GL.iNet GL-MT6000, Wi-Fi 6, channel 36, 80 MHz, -77 dBm at the Deck

With "Force WPA Supplicant WiFi backend" on (wpa_supplicant v2.12), the Deck joined AP B every time, at HE-MCS 0 with 17.2 Mbit/s send and 6 Mbit/s receive link rates. In an earlier session it stayed on AP B for 25 minutes at -79 dBm with no move recorded in the journal at default log level, even though NetworkManager listed AP A as stronger. NetworkManager passed bgscan "simple:30:-70:86400" and no BSSID lock. The journal also showed "Reject scan trigger since one is already pending".

With the setting off (iwd 3.12), in the same spot, the Deck joined AP A every time, at 866.7 Mbit/s send and 173.4 Mbit/s receive.

This differs from #2981 and #2992, where the connection fails. Here it connects, but to the far weaker access point.

Describe what you expected should happen and what did happen.

Expected: the Deck joins AP A, or at least moves to it when the link is poor.
Actual: the Deck joins AP B and stays there.

Steps for reproducing this issue:
  1. Set up two access points on one SSID, with a Wi-Fi 6 AP far away and a Wi-Fi 5 AP close by.
  2. Turn on "Force WPA Supplicant WiFi backend" and restart.
  3. Check the connected BSSID with iw dev wlan0 link.
  4. Turn Wi-Fi off and on three times, checking each time.
  5. Turn the setting off, restart and repeat.

Results: wpa_supplicant joined AP B 4 of 4 times. iwd joined AP A 7 of 7 times, with no connection failures.

Notes: tested at one site, with one Wi-Fi 5 and one Wi-Fi 6 AP, so I can't say whether the Wi-Fi standard is the deciding factor. The backend also switched to wpa_supplicant on entering Gaming Mode, which matches #3005. Since I turned the setting off, it has stayed on iwd through a restart and a round trip to Desktop Mode.

Lingua principale
Nessun dato sulla lingua
Stelle
2.7k
Fork
89
Nessuna PR unita negli ultimi 30g

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 ValveSoftware/SteamOS

Tutte le issue di ValveSoftware/SteamOS

Issue simili

Altre issue su Networking

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.