Why is my wireless disabled ("interface is disabled") when it's not?

nagyv · December 17, 2024, 12:27pm

Hello,

I'm setting up my 2nd dumb AP for fast roaming. I Configured the wireless (I think) exactly as I have on my 1st dump AP (where it works), but my router still says that it's disabled ... or rather it says both enabled and disabled ... in either case, it does not work: the SSID is not available close to the router where the other router/AP can not broadcast.

On the screenshots, I'm focusing on the "Templom-9" SSID. I disabled the other two SSID as I was troubleshooting this setup, but they showed the same behavior.

What am I missing?

frollic · December 17, 2024, 12:31pm

run logread -f while you click the enable button, post the output.

nagyv · December 17, 2024, 12:38pm

Thank you frollic! Below is the output of logread -f.

Independently of the logs, I just noticed that my other devices have phy0-ap1, phy0-ap2 etc devices, this one does not have such devices auto-created, even though it expects a phy1-ap0 device.

Tue Dec 17 12:30:10 2024 kern.info kernel: [ 1605.831792] rt3050-esw 10110000.esw: port 0 link down
Tue Dec 17 12:30:10 2024 kern.info kernel: [ 1605.837853] br-lan: port 1(eth0.3) entered disabled state
Tue Dec 17 12:30:10 2024 kern.info kernel: [ 1605.843733] br-lan: port 2(eth0.4) entered disabled state
Tue Dec 17 12:30:10 2024 kern.info kernel: [ 1605.849677] br-lan: port 3(eth0.99) entered disabled state
Tue Dec 17 12:30:10 2024 daemon.notice netifd: Network device 'eth0' link is down
Tue Dec 17 12:30:10 2024 daemon.notice netifd: VLAN 'eth0.3' link is down
Tue Dec 17 12:30:10 2024 daemon.notice netifd: VLAN 'eth0.4' link is down
Tue Dec 17 12:30:10 2024 daemon.notice netifd: VLAN 'eth0.99' link is down
Tue Dec 17 12:30:10 2024 daemon.notice netifd: bridge 'br-lan' link is down
Tue Dec 17 12:30:11 2024 daemon.notice netifd: radio1 (3740): WARNING: Variable 'data' does not exist or is not an array/object
Tue Dec 17 12:30:11 2024 daemon.notice netifd: VLAN 'br-lan.3' link is down
Tue Dec 17 12:30:11 2024 daemon.notice netifd: Interface 'IOT' has link connectivity loss
Tue Dec 17 12:30:11 2024 daemon.notice netifd: VLAN 'br-lan.4' link is down
Tue Dec 17 12:30:11 2024 daemon.notice netifd: Interface 'guest' has link connectivity loss
Tue Dec 17 12:30:11 2024 daemon.notice netifd: VLAN 'br-lan.99' link is down
Tue Dec 17 12:30:11 2024 daemon.notice netifd: Interface 'lan' has link connectivity loss
Tue Dec 17 12:30:12 2024 daemon.notice hostapd: Set new config for phy phy1:
Tue Dec 17 12:30:12 2024 daemon.notice netifd: guest (3437): udhcpc: received SIGTERM
Tue Dec 17 12:30:12 2024 daemon.notice netifd: guest (3437): udhcpc: unicasting a release of 192.168.4.140 to 192.168.4.1
Tue Dec 17 12:30:12 2024 daemon.notice netifd: guest (3437): udhcpc: sending release
Tue Dec 17 12:30:12 2024 daemon.notice netifd: guest (3437): udhcpc: entering released state
Tue Dec 17 12:30:12 2024 daemon.notice netifd: IOT (3436): udhcpc: received SIGTERM
Tue Dec 17 12:30:12 2024 daemon.notice netifd: IOT (3436): udhcpc: unicasting a release of 192.168.3.140 to 192.168.3.1
Tue Dec 17 12:30:12 2024 daemon.notice netifd: IOT (3436): udhcpc: sending release
Tue Dec 17 12:30:12 2024 daemon.notice netifd: IOT (3436): udhcpc: entering released state
Tue Dec 17 12:30:12 2024 daemon.notice netifd: lan (3435): udhcpc: received SIGTERM
Tue Dec 17 12:30:12 2024 daemon.notice netifd: lan (3435): udhcpc: unicasting a release of 192.168.0.140 to 192.168.0.1
Tue Dec 17 12:30:12 2024 daemon.notice netifd: lan (3435): udhcpc: sending release
Tue Dec 17 12:30:12 2024 daemon.notice netifd: lan (3435): udhcpc: entering released state
Tue Dec 17 12:30:12 2024 daemon.notice wpa_supplicant[989]: Set new config for phy phy1
Tue Dec 17 12:30:12 2024 daemon.notice netifd: guest (3437): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "guest" } (Permission denied)
Tue Dec 17 12:30:12 2024 daemon.notice netifd: Interface 'guest' is now down
Tue Dec 17 12:30:12 2024 daemon.notice netifd: IOT (3436): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "IOT" } (Permission denied)
Tue Dec 17 12:30:12 2024 daemon.notice netifd: Interface 'IOT' is now down
Tue Dec 17 12:30:12 2024 daemon.notice netifd: lan (3435): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "lan" } (Permission denied)
Tue Dec 17 12:30:12 2024 daemon.notice netifd: Interface 'lan' is now down
Tue Dec 17 12:30:14 2024 daemon.notice wpa_supplicant[989]: Set new config for phy phy1
Tue Dec 17 12:30:14 2024 daemon.notice hostapd: Set new config for phy phy1: /var/run/hostapd-phy1.conf
Tue Dec 17 12:30:14 2024 daemon.notice hostapd: Restart interface for phy phy1
Tue Dec 17 12:30:14 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=HU ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=100 chanlist=36 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1] ieee80211ac=1 vht_oper_chwidth=0 vht_oper_centr_freq_seg0_idx= vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][MAX-A-MPDU-LEN-EXP7] channel=36  interface=phy1-ap0 bssid=50:ff:20:af:33:69 ctrl_interface=/var/run/hostapd ap_isolate=1 bss_load_update_period=60 chan_util_avg_period=600 disassoc_low_ack=1 skip_inactivity_poll=0 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 utf8_ssid=1 multi_ap=0 wpa_passphrase=Bika&Gazella&Kutya&Macska wpa_psk_file=/var/run/hostapd-phy1-ap0.psk auth_algs=1 wpa=2 wpa_pairwise=CCMP ssid=Templom-9 bridge=br-lan wds_bridge= snoop_iface=br-lan.99 wpa_
Tue Dec 17 12:30:14 2024 daemon.err hostapd: Could not set interface phy1-ap0 flags (UP): I/O error
Tue Dec 17 12:30:14 2024 daemon.err hostapd: nl80211: Could not set interface 'phy1-ap0' UP
Tue Dec 17 12:30:14 2024 daemon.notice hostapd: nl80211: deinit ifname=phy1-ap0 disabled_11b_rates=0
Tue Dec 17 12:30:14 2024 daemon.err hostapd: nl80211 driver initialization failed.
Tue Dec 17 12:30:14 2024 daemon.notice hostapd: phy1-ap0: CTRL-EVENT-TERMINATING
Tue Dec 17 12:30:14 2024 daemon.err hostapd: hostapd_free_hapd_data: Interface phy1-ap0 wasn't started
Tue Dec 17 12:30:14 2024 daemon.notice hostapd: hostapd.add_iface failed for phy phy1 ifname=phy1-ap0
Tue Dec 17 12:30:15 2024 daemon.notice netifd: Wireless device 'radio1' is now up
Tue Dec 17 12:30:15 2024 kern.info kernel: [ 1610.241263] rt3050-esw 10110000.esw: port 0 link up
Tue Dec 17 12:30:15 2024 kern.info kernel: [ 1610.246726] br-lan: port 1(eth0.3) entered blocking state
Tue Dec 17 12:30:15 2024 kern.info kernel: [ 1610.252271] br-lan: port 1(eth0.3) entered forwarding state
Tue Dec 17 12:30:15 2024 kern.info kernel: [ 1610.258316] br-lan: port 2(eth0.4) entered blocking state
Tue Dec 17 12:30:15 2024 kern.info kernel: [ 1610.263810] br-lan: port 2(eth0.4) entered forwarding state
Tue Dec 17 12:30:15 2024 kern.info kernel: [ 1610.269875] br-lan: port 3(eth0.99) entered blocking state
Tue Dec 17 12:30:15 2024 kern.info kernel: [ 1610.275458] br-lan: port 3(eth0.99) entered forwarding state
Tue Dec 17 12:30:15 2024 daemon.notice netifd: Network device 'eth0' link is up
Tue Dec 17 12:30:15 2024 daemon.notice netifd: VLAN 'eth0.3' link is up
Tue Dec 17 12:30:15 2024 daemon.notice netifd: VLAN 'eth0.4' link is up
Tue Dec 17 12:30:15 2024 daemon.notice netifd: VLAN 'eth0.99' link is up
Tue Dec 17 12:30:15 2024 daemon.notice netifd: bridge 'br-lan' link is up
Tue Dec 17 12:30:15 2024 daemon.notice netifd: VLAN 'br-lan.3' link is up
Tue Dec 17 12:30:15 2024 daemon.notice netifd: Interface 'IOT' has link connectivity
Tue Dec 17 12:30:15 2024 daemon.notice netifd: Interface 'IOT' is setting up now
Tue Dec 17 12:30:15 2024 daemon.notice netifd: VLAN 'br-lan.4' link is up
Tue Dec 17 12:30:15 2024 daemon.notice netifd: Interface 'guest' has link connectivity
Tue Dec 17 12:30:15 2024 daemon.notice netifd: Interface 'guest' is setting up now
Tue Dec 17 12:30:15 2024 daemon.notice netifd: VLAN 'br-lan.99' link is up
Tue Dec 17 12:30:15 2024 daemon.notice netifd: Interface 'lan' has link connectivity
Tue Dec 17 12:30:15 2024 daemon.notice netifd: Interface 'lan' is setting up now
Tue Dec 17 12:30:15 2024 daemon.notice netifd: guest (4060): udhcpc: started, v1.36.1
Tue Dec 17 12:30:15 2024 daemon.notice netifd: lan (4061): udhcpc: started, v1.36.1
Tue Dec 17 12:30:15 2024 daemon.notice netifd: IOT (4062): udhcpc: started, v1.36.1
Tue Dec 17 12:30:16 2024 daemon.notice netifd: lan (4061): udhcpc: broadcasting discover
Tue Dec 17 12:30:16 2024 daemon.notice netifd: IOT (4062): udhcpc: broadcasting discover
Tue Dec 17 12:30:16 2024 daemon.notice netifd: guest (4060): udhcpc: broadcasting discover
Tue Dec 17 12:30:18 2024 daemon.notice netifd: lan (4061): udhcpc: broadcasting discover
Tue Dec 17 12:30:19 2024 daemon.notice netifd: lan (4061): udhcpc: broadcasting select for 192.168.0.140, server 192.168.0.1
Tue Dec 17 12:30:19 2024 daemon.notice netifd: IOT (4062): udhcpc: broadcasting discover
Tue Dec 17 12:30:19 2024 daemon.notice netifd: guest (4060): udhcpc: broadcasting discover
Tue Dec 17 12:30:21 2024 daemon.notice netifd: lan (4061): udhcpc: broadcasting select for 192.168.0.140, server 192.168.0.1
Tue Dec 17 12:30:22 2024 daemon.notice netifd: IOT (4062): udhcpc: broadcasting discover
Tue Dec 17 12:30:22 2024 daemon.notice netifd: guest (4060): udhcpc: broadcasting discover
Tue Dec 17 12:30:22 2024 daemon.notice netifd: IOT (4062): udhcpc: broadcasting select for 192.168.3.140, server 192.168.3.1
Tue Dec 17 12:30:22 2024 daemon.notice netifd: guest (4060): udhcpc: broadcasting select for 192.168.4.140, server 192.168.4.1
Tue Dec 17 12:30:22 2024 daemon.notice netifd: lan (4061): udhcpc: lease of 192.168.0.140 obtained from 192.168.0.1, lease time 43200
Tue Dec 17 12:30:22 2024 daemon.notice netifd: Interface 'lan' is now up
Tue Dec 17 12:30:25 2024 daemon.notice netifd: guest (4060): udhcpc: broadcasting select for 192.168.4.140, server 192.168.4.1
Tue Dec 17 12:30:25 2024 daemon.notice netifd: IOT (4062): udhcpc: broadcasting select for 192.168.3.140, server 192.168.3.1
Tue Dec 17 12:30:25 2024 daemon.notice netifd: IOT (4062): udhcpc: lease of 192.168.3.140 obtained from 192.168.3.1, lease time 43200
Tue Dec 17 12:30:25 2024 daemon.notice netifd: guest (4060): udhcpc: lease of 192.168.4.140 obtained from 192.168.4.1, lease time 3600
Tue Dec 17 12:30:25 2024 daemon.notice netifd: Interface 'IOT' is now up
Tue Dec 17 12:30:25 2024 daemon.notice netifd: Interface 'guest' is now up

brada4 · December 17, 2024, 1:05pm

Set channel width to 80?

nagyv · December 17, 2024, 1:10pm

This did not help.

brada4 · December 17, 2024, 1:11pm

What is in /etc/config/wireless ? Minus passwords
In channel map of iw list ?

nagyv · December 17, 2024, 1:19pm

cat /etc/config/wireless

config wifi-device 'radio0'
	option type 'mac80211'
	option path 'platform/10300000.wmac'
	option channel '1'
	option band '2g'
	option htmode 'HT20'
	option disabled '1'

config wifi-iface 'default_radio0'
	option device 'radio0'
	option network 'lan'
	option mode 'ap'
	option ssid 'OpenWrt'
	option encryption 'none'

config wifi-device 'radio1'
	option type 'mac80211'
	option path 'pci0000:00/0000:00:00.0/0000:01:00.0'
	option channel '36'
	option band '5g'
	option htmode 'VHT80'
	option cell_density '0'
	option country 'HU'

config wifi-iface 'wifinet1'
	option device 'radio1'
	option mode 'ap'
	option ssid 'Templom-9'
	option encryption 'psk2'
	option key 'xxx'
	option ieee80211r '1'
	option mobility_domain 'f457'
	option ft_over_ds '0'
	option ft_psk_generate_local '1'
	option network 'lan'

config wifi-iface 'wifinet2'
	option device 'radio1'
	option mode 'ap'
	option ssid 'Templom-9_iot'
	option encryption 'psk2'
	option key 'xxx'
	option ieee80211r '1'
	option mobility_domain '1f32'
	option ft_over_ds '0'
	option ft_psk_generate_local '1'
	option network 'IOT'
	option disabled '1'

config wifi-iface 'wifinet3'
	option device 'radio1'
	option mode 'ap'
	option ssid 'Templom-9_vendeg'
	option encryption 'psk2'
	option key 'xxx'
	option ieee80211r '1'
	option mobility_domain 'abc6'
	option ft_over_ds '0'
	option ft_psk_generate_local '1'
	option network 'guest'
	option disabled '1'

iw list output:

Wiphy phy1
	wiphy index: 1
	max # scan SSIDs: 4
	max scan IEs length: 543 bytes
	max # sched scan SSIDs: 10
	max # match sets: 16
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports AP-side u-APSD.
	Device supports T-DLS.
	Available Antennas: TX 0x3 RX 0x3
	Configured Antennas: TX 0x3 RX 0x3
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
		 * mesh point
		 * P2P-client
		 * P2P-GO
	Band 2:
		Capabilities: 0x1ff
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX Greenfield
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 3839 bytes
			No DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: No restriction (0x00)
		HT TX/RX MCS rate indexes supported: 0-15
		VHT Capabilities (0x338001f8):
			Max MPDU length: 3895
			Supported Channel Width: 160 MHz, 80+80 MHz
			RX LDPC
			short GI (80 MHz)
			short GI (160/80+80 MHz)
			TX STBC
			RX antenna pattern consistency
			TX antenna pattern consistency
		VHT RX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT RX highest supported: 0 Mbps
		VHT TX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT TX highest supported: 0 Mbps
		VHT extended NSS: not supported
		Frequencies:
			* 5180 MHz [36] (23.0 dBm)
			* 5200 MHz [40] (23.0 dBm)
			* 5220 MHz [44] (23.0 dBm)
			* 5240 MHz [48] (23.0 dBm)
			* 5260 MHz [52] (20.0 dBm) (radar detection)
			* 5280 MHz [56] (20.0 dBm) (radar detection)
			* 5300 MHz [60] (20.0 dBm) (radar detection)
			* 5320 MHz [64] (20.0 dBm) (radar detection)
			* 5500 MHz [100] (23.0 dBm) (radar detection)
			* 5520 MHz [104] (23.0 dBm) (radar detection)
			* 5540 MHz [108] (23.0 dBm) (radar detection)
			* 5560 MHz [112] (23.0 dBm) (radar detection)
			* 5580 MHz [116] (23.0 dBm) (radar detection)
			* 5600 MHz [120] (23.0 dBm) (radar detection)
			* 5620 MHz [124] (23.0 dBm) (radar detection)
			* 5640 MHz [128] (23.0 dBm) (radar detection)
			* 5660 MHz [132] (23.0 dBm) (radar detection)
			* 5680 MHz [136] (23.0 dBm) (radar detection)
			* 5700 MHz [140] (23.0 dBm) (radar detection)
			* 5720 MHz [144] (13.0 dBm) (radar detection)
			* 5745 MHz [149] (13.0 dBm)
			* 5765 MHz [153] (13.0 dBm)
			* 5785 MHz [157] (13.0 dBm)
			* 5805 MHz [161] (13.0 dBm)
			* 5825 MHz [165] (13.0 dBm)
			* 5845 MHz [169] (13.0 dBm)
			* 5865 MHz [173] (13.0 dBm)
			* 5885 MHz [177] (disabled)
	valid interface combinations:
		 * #{ IBSS } <= 1, #{ managed, AP, mesh point, P2P-client, P2P-GO } <= 16,
		   total <= 16, #channels <= 1, STA/AP BI must match
	HT Capability overrides:
		 * MCS: ff ff ff ff ff ff ff ff ff ff
		 * maximum A-MSDU length
		 * supported channel width
		 * short GI for 40 MHz
		 * max A-MPDU length exponent
		 * min MPDU start spacing
	max # scan plans: 1
	max scan plan interval: 65535
	max scan plan iterations: 0
	Supported extended features:
		* [ VHT_IBSS ]: VHT-IBSS
		* [ RRM ]: RRM
		* [ MU_MIMO_AIR_SNIFFER ]: MU-MIMO sniffer
		* [ SET_SCAN_DWELL ]: scan dwell setting
		* [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
		* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
		* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
		* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
		* [ CAN_REPLACE_PTK0 ]: can safely replace PTK 0 when rekeying
		* [ AIRTIME_FAIRNESS ]: airtime fairness scheduling
		* [ AQL ]: Airtime Queue Limits (AQL)
		* [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
		* [ DEL_IBSS_STA ]: deletion of IBSS station support
		* [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
		* [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support
Wiphy phy0
	wiphy index: 0
	max # scan SSIDs: 4
	max scan IEs length: 2257 bytes
	max # sched scan SSIDs: 0
	max # match sets: 0
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports AP-side u-APSD.
	Device supports T-DLS.
	Available Antennas: TX 0x3 RX 0x3
	Configured Antennas: TX 0x3 RX 0x3
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
		 * mesh point
		 * P2P-client
		 * P2P-GO
	Band 1:
		Capabilities: 0x1fe
			HT20/HT40
			SM Power Save disabled
			RX Greenfield
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 3839 bytes
			No DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: No restriction (0x00)
		HT TX/RX MCS rate indexes supported: 0-15
		Frequencies:
			* 2412 MHz [1] (20.0 dBm)
			* 2417 MHz [2] (20.0 dBm)
			* 2422 MHz [3] (20.0 dBm)
			* 2427 MHz [4] (20.0 dBm)
			* 2432 MHz [5] (20.0 dBm)
			* 2437 MHz [6] (20.0 dBm)
			* 2442 MHz [7] (20.0 dBm)
			* 2447 MHz [8] (20.0 dBm)
			* 2452 MHz [9] (20.0 dBm)
			* 2457 MHz [10] (20.0 dBm)
			* 2462 MHz [11] (20.0 dBm)
			* 2467 MHz [12] (20.0 dBm)
			* 2472 MHz [13] (20.0 dBm)
			* 2484 MHz [14] (disabled)
	valid interface combinations:
		 * #{ IBSS } <= 1, #{ managed, AP, mesh point, P2P-client, P2P-GO } <= 4,
		   total <= 4, #channels <= 1, STA/AP BI must match
	HT Capability overrides:
		 * MCS: ff ff ff ff ff ff ff ff ff ff
		 * maximum A-MSDU length
		 * supported channel width
		 * short GI for 40 MHz
		 * max A-MPDU length exponent
		 * min MPDU start spacing
	max # scan plans: 1
	max scan plan interval: -1
	max scan plan iterations: 0
	Supported extended features:
		* [ RRM ]: RRM
		* [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
		* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
		* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
		* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
		* [ SCAN_RANDOM_SN ]: use random sequence numbers in scans
		* [ SCAN_MIN_PREQ_CONTENT ]: use probe request with only rate IEs in scans
		* [ AIRTIME_FAIRNESS ]: airtime fairness scheduling
		* [ AQL ]: Airtime Queue Limits (AQL)
		* [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
		* [ DEL_IBSS_STA ]: deletion of IBSS station support
		* [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
		* [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support

nagyv · December 17, 2024, 4:04pm

I'm still trying to debug the issue.

Is it normal to not have the interface (phy1-ap0) shown in the Wireless device configuration (2nd screenshot of the first post in the thread) listed under the Network / Interfaces / Devices tab or is this an error/bug?

nagyv · December 17, 2024, 4:06pm

Btw, I just noticed that the WiFi led is down. The led used to work when I used the stock Keenetic firmware (this is a KN-1613 router), and I could switch it with the router's button. I never tested it actually working with the stock firmware.

Might there be some low-level switch to enable the device?

brada4 · December 17, 2024, 5:40pm

There is no tinkering needed, radio calibration data is intact.
What is your openwrt version

ubus call system board

The iw list says it supports 16 AP-s.
Dunno, maybe clean all 11R settings? They serve zero purpose on singular AP with unique name.

nagyv · December 17, 2024, 5:41pm

I'm on latest stable

# ubus call system board
{
	"kernel": "5.15.167",
	"hostname": "mozi-router",
	"system": "MediaTek MT7628AN ver:1 eco:2",
	"model": "Keenetic KN-1613",
	"board_name": "keenetic,kn-1613",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "23.05.5",
		"revision": "r24106-10cc5fcd00",
		"target": "ramips/mt76x8",
		"description": "OpenWrt 23.05.5 r24106-10cc5fcd00"
	}
}

What do you mean by "clean all 11R settings"? How can I do that?

brada4 · December 17, 2024, 6:04pm

config wifi-device 'radio1'
	option type 'mac80211'
	option path 'pci0000:00/0000:00:00.0/0000:01:00.0'
	option channel '36'
	option band '5g'
	option htmode 'VHT80'
	option cell_density '0'
	option country 'HU'

config wifi-iface 'wifinet1'
	option device 'radio1'
	option mode 'ap'
	option ssid 'Templom-9'
	option encryption 'psk2'
	option key 'xxx'
-	option ieee80211r '1'
-	option mobility_domain 'f457'
-	option ft_over_ds '0'
-	option ft_psk_generate_local '1'
	option network 'lan'

mk24 · December 17, 2024, 7:13pm

If no STA is connected to an AP, Luci may falsely show it as "disabled." Can clients connect?

Restart wifi and check that the log shows the "AP-ENABLED" state being reached, and not a fatal error.

brada4 · December 17, 2024, 7:17pm

nagyv:

Tue Dec 17 12:30:14 2024 daemon.err hostapd: Could not set interface phy1-ap0 flags (UP): I/O error
Tue Dec 17 12:30:14 2024 daemon.err hostapd: nl80211: Could not set interface 'phy1-ap0' UP
Tue Dec 17 12:30:14 2024 daemon.notice hostapd: nl80211: deinit ifname=phy1-ap0 disabled_11b_rates=0
Tue Dec 17 12:30:14 2024 daemon.err hostapd: nl80211 driver initialization failed.
Tue Dec 17 12:30:14 2024 daemon.notice hostapd: phy1-ap0: CTRL-EVENT-TERMINATING
Tue Dec 17 12:30:14 2024 daemon.err hostapd: hostapd_free_hapd_data: Interface phy1-ap0 wasn't started
Tue Dec 17 12:30:14 2024 daemon.notice hostapd: hostapd.add_iface failed for phy phy1 ifname=phy1-ap0

Log frag of fail

nagyv · December 17, 2024, 7:45pm

As brada4 already mentioned, the logs show failure.

I restarted both the router, and disabled/enabled the wireless device, but it did not help.

As I wrote above, my guess is that the phy1-ap0 is disabled / switched off as it does not show up under Network / Interfaces / Devices, while I have similar devices on my other routers.

nagyv · December 17, 2024, 7:46pm

These 4 line (especially the first 2) configure WiFi fast-roaming. As I wrote above, I have another AP already configured, and it works with the config.

brada4 · December 17, 2024, 7:47pm

Power router off with wifi disabled, if you jumped etsi/fcc/jp it may have dfs clogged up till poweroff

nagyv · December 17, 2024, 8:26pm

Interestingly, as I moved the wireless SSID configurations under the other device, it works. It only support 802.11n, no ac, but it might be ok.

I tried re-configuring them under the phy1-ap0 device, but they remained disabled and the corresponding device is never created.

brada4 · December 17, 2024, 8:40pm

Try to add single AP configuring bare minimum - name, wpa2 or wpa3, network, country code. It should work fine in EU on channel 36 80MHz wide.

system · December 27, 2024, 8:41pm

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.