Re: support for multiple EAP methods in one config?

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.
>