Hi !
After upgrading my tp-link from 22.03.3 to 22.03.5 my both wifi are not running... webif tell me devices are not active (both radios) but scanning works ...
in log i can see this
Thu Apr 27 22:28:49 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy wlan0) --> new PHY
Thu Apr 27 22:28:49 2023 daemon.err hostapd: Line 48: unknown configuration item 'wnm_sleep_mode'
Thu Apr 27 22:28:49 2023 daemon.err hostapd: Line 49: unknown configuration item 'wnm_sleep_mode_no_keys'
Thu Apr 27 22:28:49 2023 daemon.err hostapd: Line 50: unknown configuration item 'bss_transition'
Thu Apr 27 22:28:49 2023 daemon.err hostapd: Line 70: unknown configuration item 'proxy_arp'
Thu Apr 27 22:28:49 2023 daemon.err hostapd: Line 101: unknown configuration item 'wnm_sleep_mode'
Thu Apr 27 22:28:49 2023 daemon.err hostapd: Line 102: unknown configuration item 'wnm_sleep_mode_no_keys'
Thu Apr 27 22:28:49 2023 daemon.err hostapd: Line 103: unknown configuration item 'bss_transition'
Thu Apr 27 22:28:49 2023 daemon.err hostapd: Line 122: unknown configuration item 'proxy_arp'
Thu Apr 27 22:28:49 2023 daemon.err hostapd: 8 errors found in configuration file '/var/run/hostapd-phy0.conf'
Thu Apr 27 22:28:49 2023 daemon.err hostapd: Failed to set up interface with /var/run/hostapd-phy0.conf
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): Command failed: ubus call hostapd config_add {"iface":"wlan0", "config":"/var/run/hostapd-phy0.conf"} (Invalid argument)
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): Usage: ubus [<options>] <command> [arguments...]
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): Options:
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): -s <socket>: Set the unix domain socket to connect to
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): -t <timeout>: Set the timeout (in seconds) for a command to complete
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): -S: Use simplified output (for scripts)
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): -v: More verbose output
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): -m <type>: (for monitor): include a specific message type
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): (can be used more than once)
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): -M <r|t> (for monitor): only capture received or transmitted traffic
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425):
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): Commands:
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): - list [<path>] List objects
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): - call <path> <method> [<message>] Call an object method
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): - subscribe <path> [<path>...] Subscribe to object(s) notifications
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): - listen [<path>...] Listen for events
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): - send <type> [<message>] Send an event
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): - wait_for <object> [<object>...] Wait for multiple objects to appear on ubus
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): - monitor Monitor ubus traffic
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425):
Thu Apr 27 22:28:49 2023 daemon.notice netifd: radio0 (2425): Device setup failed: HOSTAPD_START_FAILED
Any hints ?
Ciao Gerd