EDIT: This is an INCORRECT solution/workaround !!!
See here for a better one.
On my AX3600 wireless with FT (fast transition) enabled, none of the wireless networks started after updating the following packages:
hostapd-common
wpad-basic-mbedtls
Error messages:
Sat Sep 16 04:29:03 2023 daemon.err hostapd: FT (IEEE 802.11r) requires nas_identifier to be configured as a 1..48 octet string
Sat Sep 16 04:29:03 2023 daemon.err hostapd: 1 errors found in configuration file '/var/run/hostapd-phy2.conf'
Sat Sep 16 04:29:03 2023 daemon.err hostapd: Failed to set up interface with /var/run/hostapd-phy2.conf
Sat Sep 16 04:29:03 2023 daemon.notice netifd: radio2 (2268): Command failed: ubus call hostapd config_add {"iface":"phy2-ap0", "config":"/var/run/hostapd-phy2.conf"} (Invalid argument)
It's true, there is no 'nas_identifier' string in the config.
root@routerXYZ:~# cat /var/run/hostapd-phy2.conf | grep nas_identifier | awk '/=[A-Za-z0-9]{1,48}$/ {print}'
returns no match.
"nas_identifier" is supposed to be optional, but since I got the error message complaining about it being wrong I tried adding it anyway.
The configuration script "/lib/netifd/hostapd.sh" needed to be updated after line 921 to contain
append bss_conf "nas_identifier=$mobility_domain" "$N"
The context looks like this
[ -n "$network_ifname" ] && append bss_conf "ft_iface=$network_ifname" "$N"
append bss_conf "mobility_domain=$mobility_domain" "$N"
append bss_conf "nas_identifier=$mobility_domain" "$N"
append bss_conf "ft_psk_generate_local=$ft_psk_generate_local" "$N"
This adds the "nas_identifier" to the configuration. For example:
root@routerXYZ:~# cat /var/run/hostapd-phy2.conf | grep nas_identifier | awk '/=[A-Za-z0-9]{1,48}$/ {print}'
nas_identifier=1234
nas_identifier=ABCD
After a reboot wireless is working again.
I'm uncertain, if this is the correct context, or if it should be fixed somewhere else.