X5000r update 24.10.2 wifi fail (unknown configuration item 'bss_transition')

Installing and Using OpenWrt
1

updated x5000r to latest 24.10.2 and the wifi will not start if bss_transition is enabled. Editing in LUCI also fails. Going into CLI and using VI to remove all traces of bss_transition is the only way to solve it.

from error log:

Thu Jul  3 10:32:49 2025 daemon.err hostapd: Line 78: unknown configuration item 'bss_transition'
Thu Jul  3 10:32:49 2025 daemon.err hostapd: Line 116: unknown configuration item 'bss_transition'
Thu Jul  3 10:32:49 2025 daemon.err hostapd: 2 errors found in configuration file '<inline>'
Thu Jul  3 10:32:49 2025 daemon.err hostapd: Failed to set up interface with data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=TH ieee80211d=1 hw_mode=g supported_rates=60 90 120 180 240 360 480 540 basic_rates=60 120 240 beacon_int=100 stationary_ap=1 chanlist=5 #num_global_macaddr=1 #macaddr_base= ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935] ieee80211ax=1 he_su_beamformer=1 he_su_beamformee=1 he_mu_beamformer=1 he_bss_color=128 he_spr_sr_control=3 he_default_pe_duration=4 he_rts_threshold=1023 he_mu_edca_qos_info_param_count=0 he_mu_edca_qos_info_q_ack=0 he_mu_edca_qos_info_queue_request=0 he_mu_edca_qos_info_txop_request=0 he_mu_edca_ac_be_aifsn=8 he_mu_edca_ac_be_aci=0 he_mu_edca_ac_be_ecwmin=9 he_mu_edca_ac_be_ecwmax=10 he_mu_edca_ac_be_timer=255 he_mu_edca_ac_bk_aifsn=15 he_mu_edca_ac_bk_aci=1 he_mu_edca_ac_bk_ecwmin=9 he_mu_edca_ac_bk_ecwmax=10 he_mu_edca_ac_bk_timer=255 he_mu_edca_ac_vi_ecwmi
Thu Jul  3 10:32:49 2025 daemon.notice hostapd: hostapd.add_iface failed for phy phy0 ifname=phy0-ap0
Thu Jul  3 10:32:49 2025 daemon.notice wpa_supplicant[1536]: Set new config for phy phy1
Thu Jul  3 10:32:49 2025 daemon.notice netifd: radio0 (5159): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 1537 path (/usr/sbin/wpad (deleted))
Thu Jul  3 10:32:49 2025 daemon.notice netifd: radio1 (5143): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 1536 path (/usr/sbin/wpad (deleted))
Thu Jul  3 10:32:49 2025 daemon.notice hostapd: Set new config for phy phy1: /var/run/hostapd-phy1.conf
Thu Jul  3 10:32:49 2025 daemon.notice hostapd: Remove bss 'phy1-ap1' on phy 'phy1'
Thu Jul  3 10:32:49 2025 daemon.notice hostapd: phy1-ap1: AP-DISABLED
Thu Jul  3 10:32:49 2025 daemon.notice hostapd: phy1-ap1: CTRL-EVENT-TERMINATING
Thu Jul  3 10:32:49 2025 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Thu Jul  3 10:32:49 2025 daemon.notice hostapd: nl80211: Failed to remove interface phy1-ap1 from bridge br-lan: No such device
Thu Jul  3 10:32:49 2025 daemon.notice hostapd: Remove bss 'phy1-ap2' on phy 'phy1'
2

You have probably had in your old image hostapd/wpad with more features, while you now have just wpad-basic that does not support all features. Feature-limited wpad-basic is the default, as it is somewhat smaller than the full wpad.

Use opkg to remove wpad-basic, and install then wpad. (Note that there are SSL library based variants of each host and size, so the exact package is wpad-mbedtls or wpad-openssl.)

2 Likes
3

THe first thing - why do you have such parameter enabled at all?

4

I have 6 access points scattered around my house and patio. I trust BSS does what it says it does and suggests to mobile devices which next best AP to reconnect when roaming.

5

Rexommend luci-app-attendedsysupgrade for less confusion.

You can use usteer , it will just do nothing if KV cannot be enabled on the fly. At least you maintain basic connectivity if you install "default" sysupgrade.

6

this was attended-sysupgrade. After that I downloaded the image sysupgrade from firmware selector and still the error persisted. The only way to bring up wifi was to edit the wireless config file directly.

7

one thing I remember happened during attended-sysupgrade....the process of firmware building took a while ...like 15 mins... which was unusual so I thought the process had crashed. I refreshed the browser which reloaded the attended-sysupgrade page and the firmware process completed successfully.

8

Ok, sttendedsysupgrase setver glitched and you hd to get default image. Normally it upgrades image with all custom packages.