From: James Prestwood <prestwoj@gmail.com>
To: Michael John <MJohn@midmark.com>,
"iwd@lists.linux.dev" <iwd@lists.linux.dev>
Subject: Re: support for multiple EAP methods in one config?
Date: Thu, 9 Jan 2025 06:26:19 -0800 [thread overview]
Message-ID: <fcd2ddec-e21c-4a4c-9d28-c9c8bce8e6d5@gmail.com> (raw)
In-Reply-To: <LV8PR08MB9350114FC7C034E2E52F199BAE132@LV8PR08MB9350.namprd08.prod.outlook.com>
Hi Michael,
On 1/9/25 5:37 AM, Michael John wrote:
> Hello,
>
> I'm looking to see if IWD supports the ability to support multiple EAP method, like what can be done in wpa_supplicant.
At the moment no, there is no way to configure this.
>
> network={
> ssid="example"
> key_mgmt=WPA-EAP
> eap=TTLS PEAP
> identity="username"
> password="password"
> # Try basically every common inner method
> phase2="autheap=MSCHAPV2 autheap=MD5 autheap=GTC autheap=OTP autheap=TLS auth=MSCHAPV2 auth=MSCHAP auth=PAP auth=CHAP auth=GTC"
> }
>
> My use case is that I'm given a username and password for a network but don't know the outer or inner protocols (or even if its personal or enterprise but I can determine that from the broadcast beacon).
So does the network actually support multiple inner methods? or is this
just more of a "debugging" feature to determine which (single) method it
supports. I'd be interested in the motivation for a feature like this.
Is it:
- There are _real_ networks that exist which support multiple EAP
methods, or...
- Your network administrators are not providing their clients with
enough information.
I do know its possible to configure/allow multiple EAP methods with
hostapd at least, so it is _possible_ that networks like this exist. I'm
more just curious if its done ever in practice, and if so I guess that's
something IWD might want to support.
Also, you should be able to determine at least if its PSK or enterprise
based on the AKM in the beacon. And IWD will also print this in the
debug logs when it scans.
Thanks,
James
>
> Thanks,
>
> Michael John
> Midmark Corporation
>
> CONFIDENTIALITY NOTICE: This message, including any attachments, contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited.
>
next prev parent reply other threads:[~2025-01-09 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 13:37 support for multiple EAP methods in one config? Michael John
2025-01-09 14:26 ` James Prestwood [this message]
2025-01-09 14:40 ` Michael John
2025-01-09 14:47 ` James Prestwood
2025-01-10 16:10 ` 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=fcd2ddec-e21c-4a4c-9d28-c9c8bce8e6d5@gmail.com \
--to=prestwoj@gmail.com \
--cc=MJohn@midmark.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