Hi
Am 08.04.22 um 10:11 schrieb Michael Biebl:
Am 08.04.22 um 09:56 schrieb Andrej Shadura:
I noticed you uploaded the workaround to Debian, and it’s about to
migrate to testing — how about downgrading the bug from
release-critical? Assuming that it actually helps.
Once NM is in testing
Am 08.04.22 um 09:56 schrieb Andrej Shadura:
Hi,
On Mon, 4 Apr 2022, at 10:47, Michael Biebl wrote:
That said, there might be a workaround available in NetworkManager
I filed
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/964
and a potential fix is now available in
Hi,
On Mon, 4 Apr 2022, at 10:47, Michael Biebl wrote:
> That said, there might be a workaround available in NetworkManager
> I filed
> https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/964
> and a potential fix is now available in
>
>
On Fri, 25 Mar 2022 07:07:03 +0900 Masashi Honma
wrote:
> Masashi, if I understand you correctly, you argue that this is an issue
> with the AP (or its firmware).
> If so, should the company AVM be contacted about this?
> I'm afraid I'm not too knowledgeable in that regard.
Michael,
> Masashi, if I understand you correctly, you argue that this is an issue
> with the AP (or its firmware).
> If so, should the company AVM be contacted about this?
> I'm afraid I'm not too knowledgeable in that regard.
Michael, Hans-Peter Jansen already reported to AVM at 2022-02-06
Some more data points:
Disabling NetworkManager completely and using wpasupplicant alone with
the following config:
network={
ssid="wgrouter"
psk=""
key_mgmt=WPA-PSK
id_str="wgrouter"
}
does indeed work.
As soon as I enable NetworkManager though, my
On 21/03/2022 09:38, Andrej Shadura wrote:
Hi,
On Sun, 20 Mar 2022, at 00:23, Masashi Honma wrote:
In my opinion, this issue could be closed.
These are reasons.
1) It is not wpa_supplicant issue but AP issue.
2) Users affected by this issue have some workarounds.
It’s true, but I’m not
Hi,
On Sun, 20 Mar 2022, at 00:23, Masashi Honma wrote:
> In my opinion, this issue could be closed.
>
> These are reasons.
> 1) It is not wpa_supplicant issue but AP issue.
> 2) Users affected by this issue have some workarounds.
It’s true, but I’m not quite happy about not being able to fix
In my opinion, this issue could be closed.
These are reasons.
1) It is not wpa_supplicant issue but AP issue.
2) Users affected by this issue have some workarounds.
Details of the 1)
The investigation has revealed that the AP is in violation of "2.3
WPA3-Personal transition mode" of the "WPA3
Am 19.03.22 um 22:30 schrieb Andrej Shadura:
Hi,
Michael, Masashi, what’s your opinion, what should I do as the maintainer of
wpa in Debian?
I can still reproduce the problem.
If more debugging is needed, please let me know. I'll try to help as
much as I can.
Michael
OpenPGP_signature
Hi,
Michael, Masashi, what’s your opinion, what should I do as the maintainer of
wpa in Debian?
--
Cheers,
Andrej
> Is it possible that wpasupplicant reports that the driver (iwlwifi)
> supports SAE but my hardware does not actually support SAE?
It looks like your device supports SAE.
Because SAE authentication is completed in your log.
Jan 18 11:36:02 pluto wpa_supplicant[86593]: SME: SAE completed -
Since I could easily reproduce it, I ran git bisect.
7a9c36722511ce4df88b76cceceb241d6c6a151e is the first bad commit
commit 7a9c36722511ce4df88b76cceceb241d6c6a151e
Author: Brian Norris
Date: Fri Feb 28 15:50:47 2020 -0800
DBus: Add "sae" to interface key_mgmt capabilities
This
On Wed, 19 Jan 2022 11:13:05 +0100 Michael Biebl wrote:
I tried the various versions from snapshots.d.o
2:2.9.0-23 - works
2:2.9.0+git20200221+f65da0c-1 - works
2:2.9.0+git20200517+dd2daf0-1 - doesn't work
2:2.9.0+git20210909+a75fdcd-1 - doesn't work
2:2.9.0+git20211018+2e122945fa53-1 -
I will drop this patch, this does not solve the issue.
2022年1月23日(日) 10:30 Masashi Honma :
>
> 2022年1月19日(水) 19:13 Michael Biebl :
> > I tried the various versions from snapshots.d.o
> >
> > 2:2.9.0-23 - works
> > 2:2.9.0+git20200221+f65da0c-1 - works
> > 2:2.9.0+git20200517+dd2daf0-1 - doesn't
2022年1月19日(水) 19:13 Michael Biebl :
> I tried the various versions from snapshots.d.o
>
> 2:2.9.0-23 - works
> 2:2.9.0+git20200221+f65da0c-1 - works
> 2:2.9.0+git20200517+dd2daf0-1 - doesn't work
> 2:2.9.0+git20210909+a75fdcd-1 - doesn't work
> 2:2.9.0+git20211018+2e122945fa53-1 - doesn't work
>
Am 18.01.22 um 21:56 schrieb Andrej Shadura:
Hi Michael,
On Tue, 18 Jan 2022, at 21:52, Michael Biebl wrote:
Am 18.01.22 um 21:47 schrieb Masashi Honma:
The log indicates that the Wi-Fi access point rejected the association
request from the Wi-Fi station with status
Hi Michael,
On Tue, 18 Jan 2022, at 21:52, Michael Biebl wrote:
> Am 18.01.22 um 21:47 schrieb Masashi Honma:
>> The log indicates that the Wi-Fi access point rejected the association
>> request from the Wi-Fi station with status
>> code=WLAN_STATUS_INVALID_IE.
>>
>> We can't read from this log
Am 18.01.22 um 21:47 schrieb Masashi Honma:
The log indicates that the Wi-Fi access point rejected the association
request from the Wi-Fi station with status
code=WLAN_STATUS_INVALID_IE.
We can't read from this log why the Wi-Fi access point rejected the
assocication request.
If I have that
The log indicates that the Wi-Fi access point rejected the association
request from the Wi-Fi station with status
code=WLAN_STATUS_INVALID_IE.
We can't read from this log why the Wi-Fi access point rejected the
assocication request.
If I have that Wi-Fi access point on hand, I can bisect this
I tried forwarding the logs to the hostapd list, but apparently the file is too
large to be allowed by default.
The original message with the attachments can be found here:
https://bugs.debian.org/1003907#20
On Tue, 18 Jan 2022, at 11:50, Michael Biebl wrote:
> I only saw this reply by
Adding the Debian bug to the loop.
On Tue, 18 Jan 2022, at 03:59, Masashi Honma wrote:
> To investigate more, could you enable wpa_supplicant debug option and
> provide the log ?
>
> Procedure is like this.
>
> 1) Edit /etc/systemd/system/multi-user.target.wants/wpa_supplicant.service to
> add
Package: wpasupplicant
Version: 2:2.10-1
Severity: grave
Hi,
during todays upgrade of wpasupplicant 2:2.9.0-23 to 2:2.10-1 my network
connection was killed (I'm using NetworkManager 1.34.0) and I wasn't
able to successfully connect again, even after a reboot.
Only a downgrade to 2:2.9.0-23
23 matches
Mail list logo
