public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: Bryce Johnson <bryce@redpinelabs.com>, iwd@lists.linux.dev
Subject: Re: Is there a way to manually force the security protocol with IWD?
Date: Fri, 30 Jan 2026 06:48:35 -0800	[thread overview]
Message-ID: <3d09fed3-9728-43e4-840d-13052b5fbf6e@gmail.com> (raw)
In-Reply-To: <CADXxVSJ5FrxYs_s_tz5y6LeGbVLnCgJP3YO8TQEXTnXs+rFuug@mail.gmail.com>

Hi Bryce,

On 1/30/26 6:43 AM, Bryce Johnson wrote:
> Hi All
> We are working to get our product through wifi certification.  Our
> testing company mentioned there was several negative test cases that
> were failing where IWD was connecting anyways because it would decide
> on the security type based on the AP.  Is there a way to force IWD to
> use a security type that is different than the AP so it would fail the
> connection?  Can we disable WPA1-only connection or force WPA2 only
> connection?

There unfortunately isn't at the moment. We do have a "developer mode" 
by specifying "-E" to IWD and this seems like it would fall into that 
category, support would need to be added of course.

But I'm somewhat confused (and maybe this is just poor test cases by 
WFA?), why would you need to certify that IWD fails when using a 
different security type than the AP? A client should not ever use a 
security type the AP doesn't advertise support for... This feels like 
its testing the AP, not IWD :)

>
> Thanks
> Bryce
>

  reply	other threads:[~2026-01-30 14:48 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 [this message]
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

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=3d09fed3-9728-43e4-840d-13052b5fbf6e@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=bryce@redpinelabs.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