From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: Jes Sorensen <Jes.Sorensen@gmail.com>,
dbnusr495 <dbnusr4950@proton.me>,
Linux Wireless <linux-wireless@vger.kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: rtl8xxxu kernel module deauthenticate session from public open Wifi AP
Date: Sat, 10 Jun 2023 14:38:59 +0700 [thread overview]
Message-ID: <08dd7a08-62d2-8efe-91ea-fb4ffd4548f2@gmail.com> (raw)
In-Reply-To: <877csbhj38.fsf@kernel.org>
On 6/10/23 14:28, Kalle Valo wrote:
>> FYI, from Bugzilla [1], the reporter posted (untested) fix. Would you
>> like to review it?
>>
>> Thanks.
>>
>> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217531#c8
>
> I'm not seeing any fix from the reporter, where is it?
>
Oops, the Bugzilla diff link above just adds pr_warn() debugging info.
No fixes yet.
Sorry for inconvenience...
> Also more information would be good to have to pinpoint where the actual
> problem is. For example, it would be good to test different APs with
> different encryption methods and make a list what works and what doesn't
> on his device. There can be numerous reasons for the problem.
>
In the starting BZ thread, the reporter had issue with WPA enterprise
(as he can't reach login and usage disclaimer page).
Thanks.
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2023-06-10 7:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 13:32 Fwd: rtl8xxxu kernel module deauthenticate session from public open Wifi AP Bagas Sanjaya
2023-06-10 6:35 ` Bagas Sanjaya
2023-06-10 7:28 ` Kalle Valo
2023-06-10 7:38 ` Bagas Sanjaya [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=08dd7a08-62d2-8efe-91ea-fb4ffd4548f2@gmail.com \
--to=bagasdotme@gmail.com \
--cc=Jes.Sorensen@gmail.com \
--cc=dbnusr4950@proton.me \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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.