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

オープン
  • 何か問題がありますか？
#3,059 コメント 1 件 リアクション 1 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
45/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
linux
領域
networking

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
言語のデータがありません
スター
2.7k
フォーク
89
30日以内にマージされた PR はありません

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

ValveSoftware/SteamOS のほかの issue

ValveSoftware/SteamOS の issue をすべて見る

似ている issue

Networking の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。