Wireless Daemon for Linux
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: Aleksman4o <aleksman4o@gmail.com>, iwd@lists.linux.dev
Cc: Denis Kenzior <denkenz@gmail.com>
Subject: Re: [PATCH v3 0/3] dbus: expose per-BSS RSN capabilities
Date: Tue, 28 Jul 2026 06:40:17 -0700	[thread overview]
Message-ID: <f9cb0ba9-da64-48b1-a8a9-3fe5c463b568@gmail.com> (raw)
In-Reply-To: <cover.1784069194.git.aleksman4o@gmail.com>

Hi Aleks,

On 7/14/26 3:48 PM, Aleksman4o wrote:
> From: Aleks Man <aleksman4o@gmail.com>
>
> James, thanks for confirming that extending BasicServiceSet is a
> reasonable approach.
>
> 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.
>
> A corresponding NetworkManager series reads and combines the per-BSS
> capabilities for its synthetic ESS access point.  It will be submitted
> separately after this API series.
>
> Validation:
>
>    - iwd builds successfully with make -j4.
>    - On a physical WPA2/WPA3 transition network, an initial PSK connection
>      was reported as WPA2.  After changing the saved profile to SAE, a
>      disconnect/reconnect through the stock Plasma applet completed without
>      a password prompt and was reported as WPA3-SAE.
>    - Cycling Wi-Fi subsequently auto-connected the SAE profile and kept it
>      visible as connected in the applet.
>    - The upstream CI auto-t runner passed the v2 series.
>
> 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 (3):
>    network: expose RSN capabilities on BSS
>    doc: document BasicServiceSet RSN property
>    auto-t: test BasicServiceSet RSN property
>
>   .../testBasicServiceSetRSN/bss_rsn_test.py    |  70 +++++++++++
>   autotests/testBasicServiceSetRSN/hw.conf      |   9 ++
>   autotests/testBasicServiceSetRSN/ssidSAE.conf |  11 ++
>   .../ssidTransition.conf                       |  12 ++
>   .../testBasicServiceSetRSN/ssidWPA2.conf      |   8 ++
>   doc/basic-service-set.txt                     |  23 ++++
>   src/network.c                                 | 110 ++++++++++++++++++
>   7 files changed, 243 insertions(+)
>   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
>
Overall this looks good. It would be nice to have some support in iwctl 
to see these fields. Those properties and getters/updaters can be 
implemented here if possible:

https://git.kernel.org/pub/scm/network/wireless/iwd.git/tree/client/bss.c

We will need to wait for Denis to comment/merge though.

Thanks,

James


  parent reply	other threads:[~2026-07-28 13:40 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 [this message]
2026-07-28 15:46         ` [PATCH v4 0/5] " Aleksman4o
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=f9cb0ba9-da64-48b1-a8a9-3fe5c463b568@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=aleksman4o@gmail.com \
    --cc=denkenz@gmail.com \
    --cc=iwd@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