I have read multiple postings about very strange problems in various parts of OpenWRT. One common nominator seems to be that users are updating packages with opkg. I think that there is a quile wide consensus that you should not use the opkg update option. Instead flash the router with new snapshot.
But the problem is that even replacing one wpad implementation with another (mesh compatible or just full) cause hostapd-common upgrade, as I just found.
At the moment I use RC3 with wpad-mbedtls 2023-06-22-599d00be-1.2 with 802,11s meshes without any problems. I have used also many snapshots and replaced the wpad-basic-mbedtls with wpad-mbedtls. I use command line "opkg remove wpad-basic-mbedtls" and "opkg install wpad-mbedtls" commands.
just booted in rc2:
DISTRIB_REVISION='r23228-cd17d8df2a'
DISTRIB_TARGET='ipq40xx/mikrotik'
DISTRIB_ARCH='arm_cortex-a7_neon-vfpv4'
DISTRIB_DESCRIPTION='OpenWrt 23.05.0-rc2 r23228-cd17d8df2a'
When I leave the option in luci empty, 'nas_id=' is automatically set to mac of the interface. I noticed that when I was investigating my 'radio_config_id' issue. So, in your case, it's missing from the 'hostapd*,conf's completely? (When not set manually)
As you stated nas_id (which is item from '/etc/config/wireless') became no longer an optional value.
The "optionality" of this configuration item is/was done by using mac addr (stripped of semicolons and and in lower case format), and setting as 'nas_identifier' in '/var/run/hostapd-phy*.conf' (this is configuration file which is generated by '/lib/netifd/wireless/mac80211.sh').
I was just providing a way how to restore this behavior by editing the '/lib/netifd/wireless/mac80211.sh' file. Ofc just simply setting the item using luci is just another approach (but more work in my opinion).
Thank you, I can and will update around whatever faults OpenWRT may have, but it's easier to work around, if you know your challenges. Thanks for your input.
I think you are correct and your solution is also correct. Maybe a "if not already populated" might be even better than that, but I didnt't even offer a solution. Yours is better, all the way
Sure you can do a check and set the 'nas_identifier' only when necessary (not set from uci config).
There are two possible approaches, either use of the uci and look for the 'nas_id' in wireless configuration file or in place of the edit of 'mac80211.sh' and look in the 'hostapd_cfg' value (which is content of generated configuration of hostapd) where you look directly for 'nas_identifier'.