Hi Yuri,
On 3/22/21 6:51 AM, Yuri D'Elia wrote:
Hi everyone.
Recently my organization upgraded our APs to some Cisco C9115AXI-E from
some older 3500I (also Cisco).
iwd used to be able to connect, but not anymore. I can still connect
through wpa_supplicant, so I suspect an issue with iwd.
Configuration for the 8021x network is unchanged and as follows:
[Security]
EAP-Method=PEAP
EAP-Identity=a(a)b.c
EAP-PEAP-Phase2-Method=MSCHAPV2
EAP-PEAP-Phase2-Identity=a(a)b.c
EAP-PEAP-Phase2-Password=xyz
Looks good. But you're not validating the certificate, which is probably not
great for security...
When connecting with IWD_TLS_DEBUG=1 iwd -d, I normally see this
just
after association:
Hmm, I would have actually expected a lot more output with IWD_TLS_DEBUG being
enabled, but maybe it is not getting far enough.
<snip>
src/station.c:station_handshake_event() Handshaking
src/netdev.c:netdev_mlme_notify() MLME notification Unknown(139)
src/netdev.c:netdev_unicast_notify() Unicast notification 129
src/netdev.c:netdev_control_port_frame_event()
4-Way handshake failed for ifindex: 17, reason: 15
So AP sends us the first packet, but we time out some time later. Can you do
two things:
1. Add the following to /etc/iwd/main.conf
[EAPoL]
MaxHandshakeTime=15
See if the handshake proceeds further. The default timeout is 5 seconds, so if
the AP or RADIUS server is extremely slow things might time out. However, this
is probably unlikely.
2. Send us or me privately an iwmon pcap trace of the first packet that the AP
sends. Maybe it has something unexpected. See [1].
Regards,
-Denis
[1]
https://iwd.wiki.kernel.org/debugging