Wireless Daemon for Linux
 help / color / mirror / Atom feed
From: Aleksman4o <aleksman4o@gmail.com>
To: iwd@lists.linux.dev
Cc: Aleks Man <aleksman4o@gmail.com>, prestwoj@gmail.com, denkenz@gmail.com
Subject: [PATCH v4 0/5] dbus: expose per-BSS RSN capabilities
Date: Tue, 28 Jul 2026 18:46:39 +0300	[thread overview]
Message-ID: <20260728154729.3485557-1-aleksman4o@gmail.com> (raw)
In-Reply-To: <f9cb0ba9-da64-48b1-a8a9-3fe5c463b568@gmail.com>

From: Aleks Man <aleksman4o@gmail.com>

James, thanks for the review.  This revision adds the requested iwctl
support for displaying the new fields.

Network.Type intentionally represents WPA2-Personal, WPA3-Personal, and
transition networks as "psk".  This series exposes the RSN information
that iwd already retains for each BSS so consumers can distinguish those
networks without changing the existing Network API.

The optional BasicServiceSet.RSN dictionary uses the same KeyMgmt,
Pairwise, and Group fields and values as wpa_supplicant's BSS.RSN
property.  NetworkManager can therefore reuse its existing parser rather
than add another translation layer.  Older consumers ignore the optional
property, and consumers can retain their Network.Type fallback for older
iwd versions.

The corresponding NetworkManager MR reads and combines the per-BSS
capabilities for its synthetic ESS access point:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2464

Validation:

  - make check: 273 passed, 6 skipped, 0 failed.
  - The installed patched iwd exposes the expected KeyMgmt, Pairwise, and
    Group values on a physical WPA2/WPA3 transition BSS.
  - The new iwctl output displays the capabilities in the get-bsses table.
  - An SAE profile auto-connects after restarting iwd and remains visible
    as connected in NetworkManager and the Plasma applet.
  - A NetworkManager disconnect/reconnect completes without a password
    prompt and reconnects as WPA3-Personal with FT.
  - The upstream CI suite passed all checks for v3.

Changes in v4:
  - Add iwctl parsing and display of the BasicServiceSet RSN dictionary,
    as requested by James.
  - Widen get-bsses property values so the capabilities remain readable
    while the table stays within 80 columns.
  - No changes to patches 1-3.

Changes in v3:
  - Shorten the auto-t filename so the generated patch metadata complies
    with GitLint's 80-column limit.  There are no code changes.

Changes in v2:
  - Resend with git-send-email after the Gmail web client corrupted the
    inline v1 patches.  There are no code changes.

RFC:
https://lore.kernel.org/iwd/CAMq8zouhDMRW4Q7qSpMCFftp21wCzuC%2BRaJKsKz0sUivGAQHXA@mail.gmail.com/

Related NetworkManager issues:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1489
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1693

Aleks Man (5):
  network: expose RSN capabilities on BSS
  doc: document BasicServiceSet RSN property
  auto-t: test BasicServiceSet RSN property
  client: display BasicServiceSet RSN property
  client: widen BSS property value column

 .../testBasicServiceSetRSN/bss_rsn_test.py    |  70 +++++++++++
 autotests/testBasicServiceSetRSN/hw.conf      |   9 ++
 autotests/testBasicServiceSetRSN/ssidSAE.conf |  11 ++
 .../ssidTransition.conf                       |  12 ++
 .../testBasicServiceSetRSN/ssidWPA2.conf      |   8 ++
 client/bss.c                                  |  76 ++++++++++++
 client/station.c                              |   4 +-
 doc/basic-service-set.txt                     |  23 ++++
 src/network.c                                 | 110 ++++++++++++++++++
 9 files changed, 321 insertions(+), 2 deletions(-)
 create mode 100644 autotests/testBasicServiceSetRSN/bss_rsn_test.py
 create mode 100644 autotests/testBasicServiceSetRSN/hw.conf
 create mode 100644 autotests/testBasicServiceSetRSN/ssidSAE.conf
 create mode 100644 autotests/testBasicServiceSetRSN/ssidTransition.conf
 create mode 100644 autotests/testBasicServiceSetRSN/ssidWPA2.conf

-- 
2.55.0

  reply	other threads:[~2026-07-28 15:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11 20:07 [RFC] dbus: expose per-BSS security capabilities Алексей
2026-07-14 13:27 ` James Prestwood
2026-07-14 20:36   ` [PATCH 0/3] dbus: expose per-BSS RSN capabilities Алексей
2026-07-14 20:37     ` [PATCH 1/3] network: expose RSN capabilities on BSS Алексей
2026-07-14 20:38     ` [PATCH 2/3] doc: document BasicServiceSet RSN property Алексей
2026-07-14 20:39     ` [PATCH 3/3] auto-t: test " Алексей
2026-07-14 21:12   ` [PATCH v2 0/3] dbus: expose per-BSS RSN capabilities Aleksman4o
2026-07-14 21:12     ` [PATCH v2 1/3] network: expose RSN capabilities on BSS Aleksman4o
2026-07-14 21:12     ` [PATCH v2 2/3] doc: document BasicServiceSet RSN property Aleksman4o
2026-07-14 21:12     ` [PATCH v2 3/3] auto-t: test " Aleksman4o
2026-07-14 22:48     ` [PATCH v3 0/3] dbus: expose per-BSS RSN capabilities Aleksman4o
2026-07-14 22:48       ` [PATCH v3 1/3] network: expose RSN capabilities on BSS Aleksman4o
2026-07-14 22:48       ` [PATCH v3 2/3] doc: document BasicServiceSet RSN property Aleksman4o
2026-07-14 22:48       ` [PATCH v3 3/3] auto-t: test " Aleksman4o
2026-07-28 13:31       ` [PATCH v3 0/3] dbus: expose per-BSS RSN capabilities Aleksman4o
2026-07-28 13:40       ` James Prestwood
2026-07-28 15:46         ` Aleksman4o [this message]
2026-07-28 15:46           ` [PATCH v4 1/5] network: expose RSN capabilities on BSS Aleksman4o
2026-07-28 15:46           ` [PATCH v4 2/5] doc: document BasicServiceSet RSN property Aleksman4o
2026-07-28 15:46           ` [PATCH v4 3/5] auto-t: test " Aleksman4o
2026-07-28 15:46           ` [PATCH v4 4/5] client: display " Aleksman4o
2026-07-28 15:46           ` [PATCH v4 5/5] client: widen BSS property value column Aleksman4o
2026-07-28 18:40           ` [PATCH v4 0/5] dbus: expose per-BSS RSN capabilities James Prestwood

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=20260728154729.3485557-1-aleksman4o@gmail.com \
    --to=aleksman4o@gmail.com \
    --cc=denkenz@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=prestwoj@gmail.com \
    /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