Skip to contentSkip to conversation

EAP-Method=PEAP and tls_reset_handshake/authentication timeout results in core-dumped

DISCUSSION Simon Brand 2 participants 8 messages Dec 10, 2019 – Dec 13, 2019

lore
Share & tools
lore
#0 lore raw

Hello,

I use a config with EAP-Method=PEAP and EAP-PEAP-Phase2-Method=MSCHAPV2, which results in (random?) core-dump.
[0]
This happens after authentication timeout or tls_reset_handshake. [1] My system is an uptodate arch linux machine with iwd 1.2-1, Linux 5.4.2-arch1-1, glibc 2.30-3. If you need more information I am happy to provide it. There is no problem with PreSharedKey Wifis. Thank you for your time and this great tool.

[0] http://sprunge.us/5Ez0pP
[1] http://sprunge.us/c13AYe

#1 lore raw

Hi Simon,

Quoted 5 lines · Simon Brand

Hello,

I use a config with EAP-Method=PEAP and EAP-PEAP-Phase2-Method=MSCHAPV2, which results in (random?) core-dump.
[0]

So from the log it appears as if you're able to authenticate and establish a connection successfully the first time after iwd starts. Right? And the crash happens after the AP requests reauthentication.

Quoted 5 lines

This happens after authentication timeout or tls_reset_handshake. [1] My system is an uptodate arch linux machine with iwd 1.2-1, Linux 5.4.2-arch1-1, glibc 2.30-3. If you need more information I am happy to provide it. There is no problem with PreSharedKey Wifis. Thank you for your time and this great tool.

Any chance you can send us a core dump, or compile iwd with debugging enabled (./bootstrap-configure --enable-debug --disable-optimization if building from git) and send us the backtrace?

Also, what hardware are you running this on?

Regards,
-Denis

#2 lore raw

Hello Denis,

exactly, sometimes I am able to establish a connection and use it for a long time.
I am using Intel Corporation Wireless 8265 / 8275 (rev 78). [0] Is there any authentication data stored in the core dump?
I will compile it with debugging enabled, but I probably wont get to it the next two days.

Best and thanks,
Simon

[0] http://sprunge.us/Gyjrbx

Quoted 30 lines · On Tue, 10 Dec 2019 01:29:34 -0600 Denis Kenzior <[email protected]> wrote:

Hi Simon,

Quoted 5 lines · Simon Brand

Hello,

I use a config with EAP-Method=PEAP and EAP-PEAP-Phase2-Method=MSCHAPV2, which results in (random?) core-dump. [0]

So from the log it appears as if you're able to authenticate and establish a connection successfully the first time after iwd starts. Right? And the crash happens after the AP requests reauthentication.

Quoted 5 lines

This happens after authentication timeout or tls_reset_handshake.
[1] My system is an uptodate arch linux machine with iwd 1.2-1, Linux 5.4.2-arch1-1, glibc 2.30-3. If you need more information I am happy to provide it. There is no problem with PreSharedKey Wifis. Thank you for your time and this great tool.

Any chance you can send us a core dump, or compile iwd with debugging enabled (./bootstrap-configure --enable-debug --disable-optimization if building from git) and send us the backtrace?

Also, what hardware are you running this on?

Regards,
-Denis
_______________________________________________
iwd mailing list -- iwd(a)lists.01.org
To unsubscribe send an email to iwd-leave(a)lists.01.org

#3 lore raw

Hi Simon,

Quoted 4 lines · Simon Brand

Hello Denis,

exactly, sometimes I am able to establish a connection and use it for a long time.

Interesting. I'm starting to suspect that the firmware / driver sends something unexpected, confusing iwd. If you can get us a backtrace and iwd debug log, that would be great. An iwmon trace would also be very helpful to pinpoint what the kernel/driver is sending us. See
https://iwd.wiki.kernel.org/debugging.

Quoted 2 lines

I am using Intel Corporation Wireless 8265 / 8275 (rev 78). [0] Is there any authentication data stored in the core dump?

Yes, in theory there is. Really all we want is the backtrace, so no need to share the core dump if you can provide that instead.

Quoted 2 lines

I will compile it with debugging enabled, but I probably wont get to it the next two days.

No worries.

Quoted 7 lines

Best and thanks,
Simon

[0] http://sprunge.us/Gyjrbx

Regards,
-Denis

#4 lore raw
In reply to Simon Brand

Hello,

today I noticed that the same happend with a PSK WPA2 Network. iwd log: http://sprunge.us/7CJCtJ
dmesg: http://sprunge.us/aeUNQa

I looked through the log and I had the same behaviour with kernel 4.19 and also iwd 0.23.

Regards,
Simon

Quoted 52 lines · On Wed, 11 Dec 2019 09:51:02 +0100 Simon Brand <[email protected]>…

Hello Denis,

exactly, sometimes I am able to establish a connection and use it for a long time.
I am using Intel Corporation Wireless 8265 / 8275 (rev 78). [0] Is there any authentication data stored in the core dump? I will compile it with debugging enabled, but I probably wont get to it the next two days.

Best and thanks,
Simon

[0] http://sprunge.us/Gyjrbx

Quoted 24 lines · On Tue, 10 Dec 2019 01:29:34 -0600 Denis Kenzior <[email protected]> wrote:

Hi Simon,

Quoted 5 lines · Simon Brand

Hello,

I use a config with EAP-Method=PEAP and EAP-PEAP-Phase2-Method=MSCHAPV2, which results in (random?) core-dump. [0]

So from the log it appears as if you're able to authenticate and establish a connection successfully the first time after iwd starts. Right? And the crash happens after the AP requests reauthentication.

Quoted 5 lines

This happens after authentication timeout or tls_reset_handshake.
[1] My system is an uptodate arch linux machine with iwd 1.2-1, Linux 5.4.2-arch1-1, glibc 2.30-3. If you need more information I am happy to provide it. There is no problem with PreSharedKey Wifis. Thank you for your time and this great tool.

Any chance you can send us a core dump, or compile iwd with debugging enabled (./bootstrap-configure --enable-debug --disable-optimization if building from git) and send us the backtrace?

Quoted 7 lines

Also, what hardware are you running this on?

Regards,
-Denis
_______________________________________________
iwd mailing list -- iwd(a)lists.01.org
To unsubscribe send an email to iwd-leave(a)lists.01.org

_______________________________________________
iwd mailing list -- iwd(a)lists.01.org
To unsubscribe send an email to iwd-leave(a)lists.01.org

#5 lore raw

Hi,

I build iwd 1.2 with the mentioned options, got 4 backtraces and the journalctl and iwmon logs.
I tried to reproduce with another device, but was not able to, so probably device related (or just easier to reproduce with this device).

https://www.dropbox.com/s/w2xs4oggf0zognf/logs.tar.xz?dl=1

If I can provide anything else, please let me know.

Thanks,
Simon

#6 lore raw

Hi Simon,

Quoted 11 lines · Simon Brand

Hi,

I build iwd 1.2 with the mentioned options, got 4 backtraces and the journalctl and iwmon logs.
I tried to reproduce with another device, but was not able to, so probably device related (or just easier to reproduce with this device).

https://www.dropbox.com/s/w2xs4oggf0zognf/logs.tar.xz?dl=1

If I can provide anything else, please let me know.

So looking at your traces, it seems you've hit the same bug that was fixed upstream recently. Can you apply this fix (or just run iwd git HEAD) and see if the issue persists?

https://git.kernel.org/pub/scm/network/wireless/iwd.git/commit/?id=d2556a48b7d65eb670fb0ce20e3f929bf9839a20

We should have iwd 1.3 out in the next few days.

Regards,
-Denis

#7 lore raw

Hi Denis,

this seams to fix my problem, thank you very much. Sorry for your time, I should have tested the git version first.

Regards,
Simon

Quoted 29 lines · On Thu, 12 Dec 2019 10:46:08 -0600 Denis Kenzior <[email protected]> wrote:

Hi Simon,

Quoted 8 lines · Simon Brand

Hi,

I build iwd 1.2 with the mentioned options, got 4 backtraces and the journalctl and iwmon logs.
I tried to reproduce with another device, but was not able to, so probably device related (or just easier to reproduce with this device).

Quoted 4 lines

https://www.dropbox.com/s/w2xs4oggf0zognf/logs.tar.xz?dl=1

If I can provide anything else, please let me know.

So looking at your traces, it seems you've hit the same bug that was fixed upstream recently. Can you apply this fix (or just run iwd git HEAD) and see if the issue persists?

https://git.kernel.org/pub/scm/network/wireless/iwd.git/commit/?id=d2556a48b7d65eb670fb0ce20e3f929bf9839a20

We should have iwd 1.3 out in the next few days.

Regards,
-Denis
_______________________________________________
iwd mailing list -- iwd(a)lists.01.org
To unsubscribe send an email to iwd-leave(a)lists.01.org