From: Denis Kenzior <denkenz@gmail.com>
To: Bryce Johnson <bryce@redpinelabs.com>,
James Prestwood <prestwoj@gmail.com>
Cc: iwd@lists.linux.dev
Subject: Re: Is there a way to manually force the security protocol with IWD?
Date: Fri, 30 Jan 2026 11:39:16 -0600 [thread overview]
Message-ID: <a8468bd1-d652-4e41-ba86-297b4f1a2f59@gmail.com> (raw)
In-Reply-To: <CADXxVSKsC=gmYoXk9UiPDfHW0a_MbfKpDc2YYH=qprA5bGNfSg@mail.gmail.com>
Hi Bryce,
> Here were the test cases
> For test case 10153_1: The test bed AP beacons with no security. The
> test case requires the STAUT to connect with WPA2-PSK only. Because
> of the mismatch of security protocols, the connection will fail.
This is a tough one since iwd categorizes networks into SSID+security and treats
each combo as a separate network. In other words SSID Foobar that advertises
Open and SSID Foobar that advertises WPA-Personal will be treated as two
separate networks.
Best we can do is add some sort of global restriction setting to iwd (like
always use WPA2+ or WPA3+). But really, this is almost always not what a
typical user would want. Users do want to connect to Open/OWE networks, legacy
networks, etc.
Another thing to try is to force OWE-only mode for the Open network, but I'm not
sure whether that will work for the 'spirit' of what the test is trying to do.
Adding SSID.open with something like:
"
[Settings]
TransitionDisable=true
DisabledTransitionModes=open
"
>
> For test case 10165_1: The test bed AP advertises at WPA2-Personal
> only. The test case requires the STAUT to connect with WPA3-Personal.
> Because of the mismatch of security protocols, the connection will
> also fail.
This is a little bit easier. You can add a SSID.psk setting with the following:
"
[Settings]
TransitionDisable=true
DisbledTransitionModes=personal
"
Refer to man 5 iwd.network for more details.
Regards,
-Denis
prev parent reply other threads:[~2026-01-30 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 14:43 Is there a way to manually force the security protocol with IWD? Bryce Johnson
2026-01-30 14:48 ` James Prestwood
2026-01-30 15:01 ` Bryce Johnson
2026-01-30 15:07 ` James Prestwood
2026-01-30 17:21 ` Bryce Johnson
2026-01-30 17:36 ` James Prestwood
2026-01-30 17:39 ` Denis Kenzior [this message]
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=a8468bd1-d652-4e41-ba86-297b4f1a2f59@gmail.com \
--to=denkenz@gmail.com \
--cc=bryce@redpinelabs.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