All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesus Gonzalez <jesusmgh@gmail.com>
To: iwd@lists.01.org
Subject: Re: Cannot connect to SAE protected AP with iwd 1.16 and beyond
Date: Mon, 30 Aug 2021 18:47:54 +0000	[thread overview]
Message-ID: <20210830184754.2717.75524@ml01.vlan13.01.org> (raw)
In-Reply-To: <25c80bed-e1f6-6e18-2516-779f0750cbc7@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

Hello,

I got time to upgrade again and start iwd with debug output enabled, and apparently it doesn't find any suitable BSS for the AP. Looking through the code, it goes through the PSK path (correct), and doesn't mistake it for a WPA2 AP (also correct) , but it still returns an empty list as far as available and connectable BSS goes. I deleted the log by mistake, but the relevant messages, taken from the code base, were:

station.c: autoconnect: No suitable BSSes found
wiphy.c: Network is WPA3-Personal...

And that's it. The scan shows the AP perfectly fine with all the correct information (as PSK) with full signal strength, but trying to connect it returns an empty list of BSS it can actually connect to.

Regards,
Jesus

  parent reply	other threads:[~2021-08-30 18:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27  8:05 Cannot connect to SAE protected AP with iwd 1.16 and beyond Jesus Gonzalez
2021-08-28  2:42 ` Denis Kenzior
2021-08-29 15:06   ` Jesus Gonzalez
2021-08-30 18:47   ` Jesus Gonzalez [this message]
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=20210830184754.2717.75524@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.