Re: [arch-general] Status of WPA3

2020-02-10 Thread Bjoern Franke via arch-general

Hi,

sorry for the late reply.


You might gather up your hw/fw/kernel wpa_supplicant hostapd info and
try the linux-wireless mailing list, as these are recent changes maybe
there are still some bugs. I would include the network profile, and
the hostapd config as well, and if you are able to get some more
verbose messages that could help maybe mount -t debugfs none
/sys/kernel and poke around in there or look at modinfo rtw88;
/sys/module/rtw88/parameters. Does the authentication just time out,
any deauth or dissasoc disconnected messages?


Unfortunately the AP does not give any access to hostapd-logs, and afaik 
AVM uses some own implementation.


The authentication just times out, I will ask on linux-wireless.

BR
Bjoern


Re: [arch-general] Status of WPA3

2020-01-26 Thread Justin Capella via arch-general
hrm, do you have access to the AP? Quick google suggest the
nl_recvmsgs might not be important--- related to scanning.

You might gather up your hw/fw/kernel wpa_supplicant hostapd info and
try the linux-wireless mailing list, as these are recent changes maybe
there are still some bugs. I would include the network profile, and
the hostapd config as well, and if you are able to get some more
verbose messages that could help maybe mount -t debugfs none
/sys/kernel and poke around in there or look at modinfo rtw88;
/sys/module/rtw88/parameters. Does the authentication just time out,
any deauth or dissasoc disconnected messages?

On Sun, Jan 26, 2020 at 4:27 AM Bjoern Franke via arch-general
 wrote:
>
> Am 25.01.20 um 23:12 schrieb Justin Capella:
> > More recent kernels should have 80211w for that driver which is also
> > required.
>
> 5.4.14/5.4.15 results in
> nl80211: send_and_recv->nl_recvmsgs failed: -33
> SME: Trying to authenticate with 44:4e:6d:a2:1f:df (SSID='xyz' freq=5500 MHz
> and not luck :/
>
> best regards
> Bjoern


Re: [arch-general] Status of WPA3

2020-01-26 Thread Bjoern Franke via arch-general

Am 25.01.20 um 23:12 schrieb Justin Capella:
More recent kernels should have 80211w for that driver which is also 
required.


5.4.14/5.4.15 results in
nl80211: send_and_recv->nl_recvmsgs failed: -33
SME: Trying to authenticate with 44:4e:6d:a2:1f:df (SSID='xyz' freq=5500 MHz
and not luck :/

best regards
Bjoern


Re: [arch-general] Status of WPA3

2020-01-25 Thread Justin Capella via arch-general
More recent kernels should have 80211w for that driver which is also
required.

https://elixir.bootlin.com/linux/latest/source/drivers/net/wireless/realtek/rtw88/main.c#L1239


Re: [arch-general] Status of WPA3

2020-01-25 Thread Bjoern Franke via arch-general

Am 25.01.20 um 18:10 schrieb Justin Capella via arch-general:

heftig has updated wpa_supplicant pkg
https://git.archlinux.org/svntogit/packages.git/diff/trunk/config?h=packages/wpa_supplicant=3337d901e02dc38e95b23b714747b0384b2e5171


Yes, 2:2.9-5 is the version I've used.


Re: [arch-general] Status of WPA3

2020-01-25 Thread Justin Capella via arch-general
heftig has updated wpa_supplicant pkg
https://git.archlinux.org/svntogit/packages.git/diff/trunk/config?h=packages/wpa_supplicant=3337d901e02dc38e95b23b714747b0384b2e5171

On Sat, Jan 25, 2020 at 3:50 AM Bjoern Franke via arch-general
 wrote:
>
> Hi,
>
> >
> > Using it with network manager is very easy to turn on - just create:
> > cat /etc/NetworkManager/conf.d/wifi_backend.conf
> > [device]
> > wifi.backend=iwd
>
> Thanks for your reply. Unfortunately iwd has some issues in my case,
> like packet loss and much more higher pings. I'm testing iwd from time
> to time (as NM-backend) to check if it got better.
>
>
> > And restart nm. Let us know if you get it working.
> >
>
> Unfortunately it did not work - neither with iwd or with heftig's
> updated wpa_supplicant. wpa_supplicant says:
> Failed to select authenticated key management type
>
> I think rtw88 is to blame in this case, as my Thinkpad X270 used for
> work with intel chipset on Ubuntu 20.04 is connecting fine.
>
> Best Regards
> Bjoern


Re: [arch-general] Status of WPA3

2020-01-25 Thread Bjoern Franke via arch-general

Hi,



Using it with network manager is very easy to turn on - just create:
cat /etc/NetworkManager/conf.d/wifi_backend.conf
[device]
wifi.backend=iwd


Thanks for your reply. Unfortunately iwd has some issues in my case, 
like packet loss and much more higher pings. I'm testing iwd from time 
to time (as NM-backend) to check if it got better.




And restart nm. Let us know if you get it working.



Unfortunately it did not work - neither with iwd or with heftig's 
updated wpa_supplicant. wpa_supplicant says:

Failed to select authenticated key management type

I think rtw88 is to blame in this case, as my Thinkpad X270 used for 
work with intel chipset on Ubuntu 20.04 is connecting fine.


Best Regards
Bjoern


Re: [arch-general] Status of WPA3

2020-01-22 Thread Genes Lists via arch-general
On 1/22/20 7:49 AM, Bjoern Franke via arch-general wrote:
> Hi,
> 
> recently AVM provided a beta-Firmware for Fritzboxes which support WPA3.
...

In addition to above, iwd has support for WPA3 - may be worth switching
over from wpa_supp to iwd and see if it works for you (i've been using
it for some time now and it's been working well, though I have no access
to test WPA3

Using it with network manager is very easy to turn on - just create:
cat /etc/NetworkManager/conf.d/wifi_backend.conf
[device]
wifi.backend=iwd

And restart nm. Let us know if you get it working.


[arch-general] Status of WPA3

2020-01-22 Thread Bjoern Franke via arch-general
Hi,

recently AVM provided a beta-Firmware for Fritzboxes which support WPA3.
Unfortunately, our wpa_supplicant seems not be capable of WPA3:

https://bugs.archlinux.org/task/57413

When setting explicitly WPA3 in NetworkManager, my laptop is unable to
connect to my WPA2/WPA3-wifi. I assume it is caused by the missing SAE
support, or do I miss something? The assumption is caused by
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/9

Best Regards
Bjoern