Does it make sense to test WPA3 with that build? After changing encryption to WPA3 via Luci there are no errors in the log, interface is up but no client is connecting.
In mixed mode clients are connecting but based on my understanding they default to WPA2.
In WPA3 mode the WPA3 enabled clients connect ok. At least my Android 10 phone connects, but I have no other WPA3 devices to test with...
OpenWrt SNAPSHOT r12106-c6c4701def
no additional modules and just Luci config?
Yep. Sure, I am running my own build quite as it is.
And yes, I did configure WPA3 via LuCI (but that shouldn't make a difference)
Thanks! Indeed it works as long as 802.11r is disabled.
Figuring out if the client is really connected with WPA3 can be a bit difficult.
See discussion in WPA3: Can I see which encryption each client is using?
I have tested pure WPA3 so no doubt. I just wonder if WPA3 is by design incompatible with roaming or if there is a bug.
Edit: Based on that WPA3 is missing 802.11r support.
Do any of the new builds support more than 32-38 clients? I've tried the stock 19.07, r10879, r12106 and few others but they all end up with this error. To avoid issues with other config, after a factory reset, I login and only setup my 2.4G and 5G wifi and I can't get all my devices to connect. I get keep getting the following in the syslog and my /tmp/dhcp goes upto 38 records and stops growing.
Fri Jan 24 02:56:13 2020 daemon.notice hostapd: wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: Could not add STA to kernel driver
Fri Jan 24 02:56:14 2020 daemon.notice hostapd: wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: Could not add STA to kernel driver
Fri Jan 24 02:56:14 2020 kern.warn kernel: [ 726.980751] ath10k_pci 0001:01:00.0: refusing to associate station: too many connected already (32)
Fri Jan 24 02:56:14 2020 daemon.notice hostapd: wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: Could not add STA to kernel driver
Fri Jan 24 02:56:14 2020 kern.warn kernel: [ 726.984495] ath10k_pci 0001:01:00.0: refusing to associate station: too many connected already (32)
Fri Jan 24 02:56:14 2020 kern.warn kernel: [ 726.992537] ath10k_pci 0001:01:00.0: refusing to associate station: too many connected already (32)
Fri Jan 24 02:56:14 2020 daemon.notice hostapd: wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: Could not add STA to kernel driver
Fri Jan 24 02:56:14 2020 daemon.notice hostapd: wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: Could not add STA to kernel driver
Have you tried playing with maxassoc in /etc/config/wireless?
Something like:
config wifi-iface 'default_radio0'
option device 'radio0'
option network 'lan'
...
option maxassoc '255'
And the same for remaining interfaces.
Other option would be hostapd.conf and max_num_sta.
For those considering master build version from 20200123 seems to have performance issue. Might be related to Netgear R7800 exploration (IPQ8065, QCA9984).
One needs to look at /proc/softirqs now to tell if for both cores are used...
Tried that and no luck. When the limit is reached my wired devices with with static IP address also get blocked.
Have you checked size of your DHCP scope?
Assuming 19.07 is using ath10k-ct driver and firmware, you should see this response (and the link he provides in it) by the ct dev to increase the number of stations beyond 32.
HTH
1 Like
Thank you, this looks like what I needed.
What is the recommended way to update/upgrade all upgradable packages with this build?
The wiki says
The package repositories in the development snapshots are updated by the build bots to new versions very often, so it's very likely you won't be able to upgrade some packages due to broken dependencies with kernel or kernel-related packages. In that case, it's recommended to use the Image Builder and make a new firmware image with all packages you need and flash that instead of upgrading through opkg.
So I've to upgrade each time via flashing? What percentage of my settings, certificates and so on will remain? Or is it OK to use
opkg list-upgradable | cut -f 1 -d ' ' | xargs opkg upgrade
?
The recommended way is not to do that at all, ever. Flash a newer snapshot, but don't try to upgrade packages en masse.
1 Like
With what frequency do you upgrade your router? What settings will I have to apply again?
Well, I build a new build every few days, so I build quite frequently.
All your settings should survive sysupgrade, but you need to reinstall the possible extra packages.