From: Johannes Berg <johannes@sipsolutions.net>
To: Alan Stern <stern@rowland.harvard.edu>, linux-wireless@vger.kernel.org
Cc: hostap@lists.infradead.org
Subject: Re: WiFi constantly changes association
Date: Mon, 26 Aug 2024 21:19:46 +0200 [thread overview]
Message-ID: <52752800050fdd10e3d883cb4870624455d1b34e.camel@sipsolutions.net> (raw)
In-Reply-To: <9f32e4ff8b59f137208d99c40fd166f81e8de4bc.camel@sipsolutions.net>
On Mon, 2024-08-26 at 21:14 +0200, Johannes Berg wrote:
> On Mon, 2024-08-26 at 15:06 -0400, Alan Stern wrote:
> >
> > Is there any way to debug those INVALID_TE and PREV_AUTH_NOT_VALID errors?
> >
>
> The kernel doesn't use those codes for its own deauth, if that were to
> happen, so you'll want to look at the wpa_supplicant log, perhaps
> increasing the logging verbosity for it (I think how to do that probably
> depends on the distro, and I don't know off the top of my head.)
>
Then again, while what I said is still true, reading the log more
carefully shows that wpa_s decided to roam and then got into those bad
situations that caused it to deauth. So you'd want to figure out why it
decides to roam there.
Or perhaps roaming would be OK, if it weren't for the failures during
it.
johannes
next prev parent reply other threads:[~2024-08-26 19:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 19:06 WiFi constantly changes association Alan Stern
2024-08-26 19:14 ` Johannes Berg
2024-08-26 19:19 ` Johannes Berg [this message]
2024-08-27 19:09 ` Alan Stern
2024-08-28 7:19 ` Johannes Berg
2024-08-28 7:49 ` Jouni Malinen
2024-08-28 7:55 ` Johannes Berg
2024-08-28 8:50 ` Jouni Malinen
2024-08-28 18:02 ` Alan Stern
2024-08-28 19:00 ` Jouni Malinen
2024-08-28 19:07 ` Alan Stern
2024-08-28 19:17 ` Jouni Malinen
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=52752800050fdd10e3d883cb4870624455d1b34e.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=hostap@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox