Send connman mailing list submissions to
        [email protected]

To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."

Today's Topics:

   1. Wired 802.1x via WPA_Supplicant (Ryan Smith)


----------------------------------------------------------------------

Date: Sun, 10 May 2020 04:39:57 -0000
From: "Ryan Smith" <[email protected]>
Subject: Wired 802.1x via WPA_Supplicant
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"

I messaged a while back about connecting to a wired 802.1x connection via 
connman. I was able to make a rudimentary integration using ead as the 
supplicant. This worked. However, ead has a version requirement for the Linux 
kernel that is >= 4.20 for EAP-TLS. Unfortunately, the device I am targeting 
does not have a new enough kernel available. I am investigating the feasibility 
of using wpa_supplicant for the wired 802.1x connection similar to how it is 
done for the wifi plugin. The device does not require simultaneous use of WiFi 
and Ethernet. We are setting SingleConnectedTechnology=true. The device is 
fixed in place and has no need to roam. It can be configured to connect to WiFi 
or Ethernet (and hopefully 802.1x).

I have started an integration, using the wifi plugin as a pattern. I am 
creating a new plugin (and disabling the ethernet one). It looks like the 
g_supplicant code (and probably wpa_supplicant) only allows one user. Is there 
a way to switch between the two of them, or is this a no go?

Thanks for any insight!

------------------------------

Subject: Digest Footer

_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]


------------------------------

End of connman Digest, Vol 55, Issue 4
**************************************

Reply via email to