From: Jesus Gonzalez <jesusmgh@gmail.com>
To: iwd@lists.01.org
Subject: Cannot connect to SAE protected AP with iwd 1.16 and beyond
Date: Fri, 27 Aug 2021 08:05:30 +0000 [thread overview]
Message-ID: <20210827080530.2802.3544@ml01.vlan13.01.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
First of all: I looked around and found no dedicated bug tracker. if this is not the place to report bugs, please excuse me, and I would be glad to be pointed in the correct direction. Thank you!
Starting with iwd 1.16 I am not able to connect to my home WLAN network. It is a WPA3 SAE protected access point running on a Netgear R7800 with OpenWRT, in case it matters. Connecting to my WPA2 PSK AP on my phone as a test works just fine.
The connection log from the client: https://pastebin.com/48umPPzh
The only but decisive log entry in the AP: https://pastebin.com/W7JsH1kY
It seems after iwd 1.16 the client tries to associate before it is correctly authenticated. Maybe a race condition, and iwd got too fast for the router?
I tried to bisect between 1.15 and 1.16 to get the commit, but I ran into problems while building (make[1]: *** No rule to make target 'ell/util.c', needed by 'ell/util.lo'. Stop.) and I currently lack the time to troubleshoot Makefiles.
Sorry for the vague infos. If you want more logs, tell me what you need and I'll be happy to provide it! Thank you!
next reply other threads:[~2021-08-27 8:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 8:05 Jesus Gonzalez [this message]
2021-08-28 2:42 ` Cannot connect to SAE protected AP with iwd 1.16 and beyond Denis Kenzior
2021-08-29 15:06 ` Jesus Gonzalez
2021-08-30 18:47 ` Jesus Gonzalez
2021-08-30 19:01 ` Denis Kenzior
2021-08-31 5:54 ` Jesus Gonzalez
2021-08-31 6:11 ` Paul Menzel
2021-09-01 13:05 ` Jesus Gonzalez
2021-08-31 13:24 ` Denis Kenzior
2021-09-01 13:09 ` Jesus Gonzalez
2021-09-01 15:51 ` Denis Kenzior
2021-09-01 18:59 ` Jesus Gonzalez
2021-09-01 20:54 ` Denis Kenzior
2021-09-07 21:18 ` James Prestwood
2021-09-08 8:41 ` Jesus Gonzalez
2021-09-08 16:44 ` James Prestwood
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=20210827080530.2802.3544@ml01.vlan13.01.org \
--to=jesusmgh@gmail.com \
--cc=iwd@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.