All of lore.kernel.org
 help / color / mirror / Atom feed
From: Madhu <enometh@meer.net>
To: linux-wireless@vger.kernel.org
Subject: Re: help troubleshooting failures connect to an access point with iw/iwd
Date: Tue, 14 Sep 2021 08:41:16 +0530 (IST)	[thread overview]
Message-ID: <20210914.084116.1726846422542610443.enometh@meer.net> (raw)
In-Reply-To: 20210912.033932.2187976226343353888.enometh@meer.net


* I Wrote on Sun, 12 Sep 2021 03:39:32 +0530 (IST),
in <20210912.033932.2187976226343353888.enometh@meer.net> :

> I've been using wpa_supplicant with rtw88 and b43 cards to connect to
> a wpa-psk home router successfully for many years. This was with
> -Wext. However I'm not able to accomplish this with iw or iwd.

The iwd part of the story has a resolution:

> $/usr/libexec/iwd --version
> 1.17
> $/usr/libexec/iwd -d
> $ iwctl station wlan0 get-hidden-access-points
> $ iwctl --passphrase=XXX  station wlan0 connect SSID
>
> If this connects it always immediately disconnects
>
> kernel: [86195.924708] wlan0: authenticate with 58:xx:6e:xx:51:e4
> kernel: [86196.264641] wlan0: send auth to 58:xx:6e:xx:51:e4 (try 1/3)
> kernel: [86196.268477] wlan0: authenticated
> kernel: [86196.274379] wlan0: associate with 58:xx:6e:xx:51:e4 (try 1/3)
> kernel: [86196.281420] wlan0: RX AssocResp from 58:xx:6e:xx:51:e4
> (capab=0x411 status=0 aid=1)
> kernel: [86196.281491] rtw_8822ce 0000:xx:00.0: sta 58:xx:6e:xx:51:e4
> joined with macid 0
> kernel: [86196.282235] wlan0: associated
> kernel: [86238.445926] wlan0: deauthenticated from 58:xx:6e:xx:51:e4
> (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
> kernel: [86238.594381] rtw_8822ce 0000:xx:00.0: sta 58:xx:6e:xx:51:e4 with macid 0 left
>
> - So an connection, after authentication immediately deauthenticates
>   with (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA). The deauthentication
>   happens when any packet is to be sent on the interface

As was pointed out, this is avoided by a

[General]
ControlPortOverNL80211=False

item in /etc/iwd/main.conf

The other problems are outstanding.

      reply	other threads:[~2021-09-14  3:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20  1:02 rtw88 strange killall behaviour with nm Madhu
2021-04-20  4:34 ` Klaus Müller
2021-04-21  4:51   ` Madhu
2021-09-11 22:09     ` help troubleshooting failures connect to an access point with iw/iwd Madhu
2021-09-14  3:11       ` Madhu [this message]

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=20210914.084116.1726846422542610443.enometh@meer.net \
    --to=enometh@meer.net \
    --cc=linux-wireless@vger.kernel.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.