"I can't confirm or deny that" as seems to be the catch-phrase of the last couple years.
If I were to go for a "quick" approach, I'd try the LAN ports for one subnet and the WAN port for the other. Untagged to the off-board switch, then tagged from there to the rest of your infrastructure.
Yes, on my short list to resolve, as I'd like to replace my "main" Archer C7v2 with one of my EA8300s, but neck deep in driver code for SPI NAND and getting it accepted upstream (Linux) right now.
I am so sorry:
But I have to get it clarified, as I don't (really) understand it.
What do I have to tag and what not, with which VLANs (assuming I have one LAN cable in the WAN port and the other LAN cable in LAN1)?
Thank you very much!!
I think you should be able to run "SSID 1" as untagged on a LAN port on one cable and "SSID 2" as untagged on the "WAN" port.
At least as far as I understand the switch / MAC configuration, the four LAN ports are tagged by the switch internally as VLAN 1 vlan_tag = <1 0x1f>; and sent to gmac0, while the Internet port is tagged internally as VLAN 2 vlan_tag = <2 0x20>; and sent to gmac1. (The second value there is, as I recall, a bit map of the ports to which it applies).
Edit: I wish I knew all the "rules" to help you with this one -- I had one here on the bench talking over a management VLAN, but I don't enough yet as to how and why to provide more guidance as to the limitations.
Thank you very much!!
I got it working just like you said (untagged) - this is good enough for me at the moment. Looking forward for your fix however! 
Nevertheless, I think I ran into another issue with the Wi-Fi devices (specifically with the 3rd band, which serves only channels starting from 100) - sometimes it seems like the SSID is not getting broadcasted (LuCi says "Wireless is not associated" for that SSID, although it is) and I cannot find it using any wireless device (tested with a Google Pixel 2 XL and a Lenovo ThinkPad [2018 model, forgot the exact naming, sorry]).
I have a feeling it is somehow associated to "DFS" - although I have just a really basic understanding of that topic, but I thought I'd point it out and you (or someone else) gets a clue through that.
I tried a lot of different settings, but apparently it is not associated to my total number of SSIDs (I have 4), as I am able to create all of them on the other 5GHz (2 of them here) and the 2,4GHz (2 of them here) bands.
I have checked via iw list, but as far as I understand the output, I am able to bring up 16 SSIDs per band - so far more than I need.
Here is the output of it:
root@OpenWrt:~# iw list
Wiphy phy2
max # scan SSIDs: 16
max scan IEs length: 199 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* monitor
* mesh point
* P2P-client
* P2P-GO
* P2P-device
Band 2:
Capabilities: 0x19ef
RX LDPC
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
VHT Capabilities (0x339959b2):
Max MPDU length: 11454
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
TX STBC
SU Beamformer
SU Beamformee
MU Beamformer
MU Beamformee
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
Frequencies:
* 5180 MHz [36] (20.0 dBm)
* 5200 MHz [40] (20.0 dBm)
* 5220 MHz [44] (20.0 dBm)
* 5240 MHz [48] (20.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] (disabled)
* 5520 MHz [104] (disabled)
* 5540 MHz [108] (disabled)
* 5560 MHz [112] (disabled)
* 5580 MHz [116] (disabled)
* 5600 MHz [120] (disabled)
* 5620 MHz [124] (disabled)
* 5640 MHz [128] (disabled)
* 5660 MHz [132] (disabled)
* 5680 MHz [136] (disabled)
* 5700 MHz [140] (disabled)
* 5720 MHz [144] (disabled)
* 5745 MHz [149] (disabled)
* 5765 MHz [153] (disabled)
* 5785 MHz [157] (disabled)
* 5805 MHz [161] (disabled)
* 5825 MHz [165] (disabled)
* 5845 MHz [169] (disabled)
* 5865 MHz [173] (disabled)
valid interface combinations:
* #{ managed } <= 16, #{ AP, mesh point } <= 16, #{ IBSS } <= 1,
total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }
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
Supported extended features:
* [ VHT_IBSS ]: VHT-IBSS
* [ RRM ]: RRM
* [ SET_SCAN_DWELL ]: scan dwell setting
* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
Wiphy phy1
max # scan SSIDs: 16
max scan IEs length: 195 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* monitor
* mesh point
* P2P-client
* P2P-GO
* P2P-device
Band 1:
Capabilities: 0x19ef
RX LDPC
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
VHT Capabilities (0x339959b2):
Max MPDU length: 11454
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
TX STBC
SU Beamformer
SU Beamformee
MU Beamformer
MU Beamformee
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
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:
* #{ managed } <= 16, #{ AP, mesh point } <= 16, #{ IBSS } <= 1,
total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }
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
Supported extended features:
* [ VHT_IBSS ]: VHT-IBSS
* [ RRM ]: RRM
* [ SET_SCAN_DWELL ]: scan dwell setting
* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
Wiphy phy0
max # scan SSIDs: 16
max scan IEs length: 199 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 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
* monitor
* mesh point
* P2P-client
* P2P-GO
* P2P-device
Band 2:
Capabilities: 0x19ef
RX LDPC
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
VHT Capabilities (0x339979b2):
Max MPDU length: 11454
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
TX STBC
SU Beamformer
SU Beamformee
MU Beamformer
MU Beamformee
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
Frequencies:
* 5180 MHz [36] (disabled)
* 5200 MHz [40] (disabled)
* 5220 MHz [44] (disabled)
* 5240 MHz [48] (disabled)
* 5260 MHz [52] (disabled)
* 5280 MHz [56] (disabled)
* 5300 MHz [60] (disabled)
* 5320 MHz [64] (disabled)
* 5500 MHz [100] (26.0 dBm) (radar detection)
* 5520 MHz [104] (26.0 dBm) (radar detection)
* 5540 MHz [108] (26.0 dBm) (radar detection)
* 5560 MHz [112] (26.0 dBm) (radar detection)
* 5580 MHz [116] (26.0 dBm) (radar detection)
* 5600 MHz [120] (26.0 dBm) (radar detection)
* 5620 MHz [124] (26.0 dBm) (radar detection)
* 5640 MHz [128] (26.0 dBm) (radar detection)
* 5660 MHz [132] (26.0 dBm) (radar detection)
* 5680 MHz [136] (26.0 dBm) (radar detection)
* 5700 MHz [140] (26.0 dBm) (radar detection)
* 5720 MHz [144] (disabled)
* 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] (disabled)
* 5865 MHz [173] (disabled)
valid interface combinations:
* #{ managed } <= 16, #{ AP, mesh point } <= 16, #{ IBSS } <= 1,
total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }
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
Supported extended features:
* [ VHT_IBSS ]: VHT-IBSS
* [ RRM ]: RRM
* [ SET_SCAN_DWELL ]: scan dwell setting
* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
root@OpenWrt:~#
Also following the output of /etc/config/network:
root@OpenWrt:~# cat /etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fda0:6d9e:9136::/48'
config interface 'home'
option type 'bridge'
option ifname 'eth0'
option proto 'dhcp'
option ip6assign '60'
option delegate '0'
config interface 'office'
option type 'bridge'
option ifname 'eth1'
option proto 'dhcp'
option ip6assign '60'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '1 2 3 4 0'
root@OpenWrt:~#
And the output of /etc/config/wireless (with the current non-working settings for band3 (channel >= 100):
root@OpenWrt:~# cat /etc/config/wireless
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11a'
option path 'soc/40000000.pci/pci0000:00/0000:00:00.0/0000:01:00.0'
option htmode 'VHT80'
option country 'DE'
option channel 'auto'
option legacy_rates '0'
config wifi-device 'radio1'
option type 'mac80211'
option hwmode '11g'
option path 'platform/soc/a000000.wifi'
option htmode 'HT20'
option legacy_rates '1'
option country 'DE'
option txpower '20'
option channel '6'
config wifi-device 'radio2'
option type 'mac80211'
option hwmode '11a'
option path 'platform/soc/a800000.wifi'
option htmode 'VHT80'
option legacy_rates '1'
option txpower '20'
option channel '36'
option country 'DE'
config wifi-iface
option device 'radio1'
option mode 'ap'
option ssid 'Toadette'
option encryption 'psk2'
option key 'REMOVED'
option network 'office'
config wifi-iface
option device 'radio2'
option mode 'ap'
option network 'home'
option encryption 'psk2'
option key 'REMOVED'
option ssid 'Yoshi'
config wifi-iface
option device 'radio1'
option mode 'ap'
option ssid 'Kirby'
option network 'home'
option encryption 'psk2'
option key 'REMOVED'
config wifi-iface
option device 'radio0'
option mode 'ap'
option ssid 'Peach'
option network 'office'
option encryption 'psk2'
option key 'REMOVED'
config wifi-iface
option device 'radio2'
option mode 'ap'
option ssid 'Peach'
option network 'office'
option encryption 'psk2'
option key 'REMOVED'
Please note, I added the second SSID Peach twice (for testing purposes only). I am only interested in bringing Peach up on the "3rd band".
BTW: Should I open another thread for this issue, or can we discuss it here?
Thank you very much!
Small note:
The EA8300 has definitely better Wi-Fi than my WRT3200ACMs (range wise), with still reasonable throughput (~300MBit on the 5GHz band) on mid range (~10-15m with two walls across) - I am super happy with that.
Third band?
This sounds like the DFS radar detector, it should not be used for WiFi setups.
It's a Tri-Band router - my understanding was I can actually use the third band.
Quote from Linksys page:
TRI-BAND TECHNOLOGY
Three bands that deliver the fastest combined Wi-Fi speeds to more devices.
Is my understanding wrong?
Interesting...I believe I stand corrected (regarding your specific device). I see this is a Linksys-based feature (and designed to provide channels in the DFS range).
I can perfectly configure channels >=100 (and only starting from 100) on the 3rd band, but sometimes the Wi-Fi simply does not broadcast the SSID from the 3rd band and LuCi shows the message "Wireless is not associated "
I bet if I restart the router again, it magically starts working again - that is why I am a bit confused. Like 3 hours ago the third band worked perfectly fine, with the same signal strength as the 2nd 5GHz band and I were able to connect to it and behave just like on the 2nd 5GHz band as well.
I don't know, whether this is related to my 4 SSIDs (which I don't believe, but I am not an expert on that matter), some other configuration failure on my side or simply a bug.
That's why I asked for help on that one
Thanks!
This is normal with no associations.
Odd...
Can you try giving different SSIDs?
Perhaps they have the same MAC (BSSID).
(You may want to create another thread.)
The EA8300 a three-radio device with all radios intended for active use. There are several of these on the market now.
Note: The first 5 GHz radio (IPQ4019) is limited to ch. 64 and below. The second 5 GHz radio (QCA9888), is limited to ch. 100 and above. This is consistent with OEM firmware and is a result of the ART data and the data in the OEM firmware's cal data. This is perhaps due to RF design optimization and/or interoperation with 2.4 GHz, such as the two, shared antennas.
Check logread for evidence of misbehavior of the QCA9888 radio. If you find any, we can open an EA8300-support thread.
Try using channel 149 or higher to avoid waiting for DFS clearance.
When i try to bring up the 3rd band with "auto" settings (auto power, auto channel), following is happening:
Thu May 30 09:11:09 2019 daemon.notice netifd: radio0 (14630): command failed: Not supported (-95)
Thu May 30 09:11:09 2019 user.notice mac80211: Failed command: iw phy phy0 set distance 0
Thu May 30 09:11:09 2019 daemon.notice netifd: radio0 (14630): sh: out of range
Thu May 30 09:11:10 2019 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Thu May 30 09:11:12 2019 kern.warn kernel: [46924.726337] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
Thu May 30 09:11:12 2019 kern.warn kernel: [46924.726392] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32
Thu May 30 09:11:12 2019 kern.info kernel: [46924.780928] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
Thu May 30 09:11:12 2019 kern.info kernel: [46924.782192] ath10k_pci 0000:01:00.0: wmi print 'free: 117936 iram: 22500 sram: 29708'
Thu May 30 09:11:12 2019 daemon.notice hostapd: wlan0: INTERFACE-ENABLED
Thu May 30 09:11:12 2019 kern.warn kernel: [46925.092157] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Thu May 30 09:11:12 2019 kern.warn kernel: [46925.110398] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
Thu May 30 09:11:12 2019 daemon.notice hostapd: wlan0: INTERFACE-DISABLED
Thu May 30 09:11:12 2019 daemon.err hostapd: nl80211: Could not configure driver mode
Thu May 30 09:11:12 2019 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Thu May 30 09:11:12 2019 daemon.err hostapd: nl80211 driver initialization failed.
Thu May 30 09:11:12 2019 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->DISABLED
Thu May 30 09:11:12 2019 daemon.notice hostapd: wlan0: AP-DISABLED
Thu May 30 09:11:12 2019 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Thu May 30 09:11:12 2019 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0 wasn't started
Thu May 30 09:11:12 2019 daemon.notice netifd: radio0 (14630): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 2315 path ()
Thu May 30 09:11:12 2019 daemon.notice netifd: radio0 (14630): Device setup failed: HOSTAPD_START_FAILED
When i start it with a fixed channel value (channel 157) and power on auto:
Thu May 30 09:13:33 2019 daemon.notice netifd: radio0 (15792): command failed: Not supported (-95)
Thu May 30 09:13:33 2019 user.notice mac80211: Failed command: iw phy phy0 set distance 0
Thu May 30 09:13:33 2019 daemon.notice netifd: radio0 (15792): sh: out of range
Thu May 30 09:13:33 2019 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Thu May 30 09:13:35 2019 kern.warn kernel: [47067.994929] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
Thu May 30 09:13:35 2019 kern.warn kernel: [47067.994981] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32
Thu May 30 09:13:35 2019 kern.info kernel: [47068.049452] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
Thu May 30 09:13:35 2019 kern.info kernel: [47068.051020] ath10k_pci 0000:01:00.0: wmi print 'free: 117936 iram: 22500 sram: 29708'
Thu May 30 09:13:35 2019 kern.warn kernel: [47068.360109] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Thu May 30 09:13:35 2019 daemon.notice hostapd: wlan0: INTERFACE-ENABLED
Thu May 30 09:13:35 2019 kern.warn kernel: [47068.374833] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
Thu May 30 09:13:35 2019 daemon.notice hostapd: wlan0: INTERFACE-DISABLED
Thu May 30 09:13:35 2019 daemon.err hostapd: nl80211: Could not configure driver mode
Thu May 30 09:13:35 2019 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Thu May 30 09:13:35 2019 daemon.err hostapd: nl80211 driver initialization failed.
Thu May 30 09:13:35 2019 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->DISABLED
Thu May 30 09:13:35 2019 daemon.notice hostapd: wlan0: AP-DISABLED
Thu May 30 09:13:35 2019 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Thu May 30 09:13:35 2019 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0 wasn't started
Thu May 30 09:13:35 2019 daemon.notice netifd: radio0 (15792): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 2315 path ()
Thu May 30 09:13:36 2019 daemon.notice netifd: radio0 (15792): Device setup failed: HOSTAPD_START_FAILED
When i start it with both values fixed (channel 157, power 13 dbm (max)):
Thu May 30 09:17:15 2019 daemon.notice netifd: radio0 (17188): command failed: Not supported (-95)
Thu May 30 09:17:15 2019 user.notice mac80211: Failed command: iw phy phy0 set distance 0
Thu May 30 09:17:15 2019 daemon.notice netifd: radio0 (17188): sh: out of range
Thu May 30 09:17:16 2019 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Thu May 30 09:17:18 2019 kern.warn kernel: [47290.777939] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
Thu May 30 09:17:18 2019 kern.warn kernel: [47290.777984] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32
Thu May 30 09:17:18 2019 kern.info kernel: [47290.832445] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
Thu May 30 09:17:18 2019 kern.info kernel: [47290.834756] ath10k_pci 0000:01:00.0: wmi print 'free: 117936 iram: 22500 sram: 29708'
Thu May 30 09:17:18 2019 daemon.notice hostapd: wlan0: INTERFACE-ENABLED
Thu May 30 09:17:18 2019 kern.warn kernel: [47291.146624] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Thu May 30 09:17:18 2019 kern.warn kernel: [47291.148729] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
Thu May 30 09:17:18 2019 daemon.err hostapd: nl80211: Could not configure driver mode
Thu May 30 09:17:18 2019 daemon.notice hostapd: wlan0: INTERFACE-DISABLED
Thu May 30 09:17:18 2019 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Thu May 30 09:17:18 2019 daemon.err hostapd: nl80211 driver initialization failed.
Thu May 30 09:17:18 2019 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->DISABLED
Thu May 30 09:17:18 2019 daemon.notice hostapd: wlan0: AP-DISABLED
Thu May 30 09:17:18 2019 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Thu May 30 09:17:18 2019 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0 wasn't started
Thu May 30 09:17:18 2019 daemon.notice netifd: radio0 (17188): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 2315 path ()
Thu May 30 09:17:18 2019 daemon.notice netifd: radio0 (17188): Device setup failed: HOSTAPD_START_FAILED
Does that help you in any way?
From what I can tell the MACs are different:
root@OpenWrt:~# ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-home state UP qlen 1000
link/ether 30:23:03:6e:1a:52 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-office state UP qlen 1000
link/ether 30:23:03:6e:1a:53 brd ff:ff:ff:ff:ff:ff
7: br-home: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
link/ether 30:23:03:6e:1a:52 brd ff:ff:ff:ff:ff:ff
inet 10.10.40.3/24 brd 10.10.40.255 scope global br-home
valid_lft forever preferred_lft forever
8: br-office: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
link/ether 30:23:03:6e:1a:53 brd ff:ff:ff:ff:ff:ff
inet 10.10.20.9/24 brd 10.10.20.255 scope global br-office
valid_lft forever preferred_lft forever
93: wlan1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-office state UP qlen 1000
link/ether **30:23:03:6e:1a:54** brd ff:ff:ff:ff:ff:ff
94: wlan1-1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-home state UP qlen 1000
link/ether 32:23:03:6e:1a:54 brd ff:ff:ff:ff:ff:ff
123: wlan2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-home state UP qlen 1000
link/ether **30:23:03:6e:1a:55** brd ff:ff:ff:ff:ff:ff
140: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN qlen 1000
link/ether **32:23:03:6e:1a:56** brd ff:ff:ff:ff:ff:ff
root@OpenWrt:~#
All the SSIDs on this device are different (as said, 4 of them, with different names).
Did that already, thanks!
Might want to set encryption to psk2+ccmp as PSK2 (alone) may be incompatible with 802.11ac
I'll poke at mine later on, assuming I have a wired connection to it at the moment.
Just tried an AP on the QCA9888 radio and I don't seen any "strange" behavior like what you're showing in your logs.
config wifi-device 'radio5pci'
option type 'mac80211'
option channel '149'
option hwmode '11a'
option path 'soc/40000000.pci/pci0000:00/0000:00:00.0/0000:01:00.0'
option htmode 'VHT80'
option require_mode 'ac'
option legacy_rates '0'
[...]
config wifi-iface '5Gap'
option device 'radio5pci'
option mode 'ap'
option ssid '5Gap'
option key 'kljhlkhlkjh'
option encryption 'psk2+ccmp'
option network 'vlan1234'
root@test:~# tail -n0 -f /var/log/messages &
root@test:~# wifi up
'radio2' is disabled
'radio2' is disabled
root@test:~# May 30 15:11:44 test mac80211: Failed command: iw phy phy2 set distance 0
May 30 15:11:44 test mac80211: Failed command: iw phy phy0 set distance 0
May 30 15:11:44 test hostapd: Configuration file: /var/run/hostapd-phy0.conf
May 30 15:11:47 test hostapd: wlan0: interface state UNINITIALIZED->HT_SCAN
May 30 15:11:47 test hostapd: Using interface wlan0 with hwaddr 32:23:03:xx:xx:xx and ssid "5Gap"
May 30 15:11:47 test hostapd: wlan0: interface state HT_SCAN->ENABLED
May 30 15:11:47 test hostapd: wlan0: AP-ENABLED
After disabling the radio, changing my country code to 'DE', rebooting, then re-enabling the radio, it also seems to work as expected. Changing the country code is not recommended unless you are absolutely certain that doing so will not permit unauthorized emissions.
root@test:~# tail -n0 -f /var/log/messages &
root@test:~# wifi up
'radio2' is disabled
'radio5soc' is disabled
'radio2' is disabled
'radio5soc' is disabled
root@test:~# May 30 15:20:39 test mac80211: Failed command: iw phy phy0 set distance 0
May 30 15:20:39 test hostapd: Configuration file: /var/run/hostapd-phy0.conf
May 30 15:20:42 test hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
May 30 15:20:42 test hostapd: wlan0: interface state COUNTRY_UPDATE->HT_SCAN
May 30 15:20:42 test hostapd: Using interface wlan0 with hwaddr 32:23:03:67:e9:5a and ssid "5Gap"
May 30 15:20:43 test hostapd: wlan0: interface state HT_SCAN->ENABLED
May 30 15:20:43 test hostapd: wlan0: AP-ENABLED
May 30 15:20:53 test hostapd: wlan0: interface state ENABLED->DISABLED
May 30 15:20:53 test hostapd: wlan0: AP-DISABLED
May 30 15:20:53 test hostapd: wlan0: CTRL-EVENT-TERMINATING
May 30 15:20:53 test hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
May 30 08:20:53 test kernel: [ 106.862007] br-vlan1010: port 3(wlan0) entered disabled state
May 30 15:20:53 test mac80211: Failed command: iw phy phy0 set distance 0
May 30 15:20:53 test hostapd: Configuration file: /var/run/hostapd-phy0.conf
May 30 08:20:56 test kernel: [ 109.621470] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
May 30 08:20:56 test kernel: [ 109.622337] ath10k_pci 0000:01:00.0: wmi print 'free: 117936 iram: 22500 sram: 29708'
May 30 15:20:56 test hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
May 30 15:20:56 test hostapd: wlan0: interface state COUNTRY_UPDATE->HT_SCAN
May 30 15:20:56 test hostapd: Using interface wlan0 with hwaddr 32:23:03:67:e9:5a and ssid "5Gap"
May 30 15:20:57 test hostapd: wlan0: interface state HT_SCAN->ENABLED
May 30 15:20:57 test hostapd: wlan0: AP-ENABLED
I just ran into the issue, that I realized, that none of my devices, which should go into that 3rd band are able to connect to 5GHz Wi-Fis in the higher ranges (besides my laptop that is). Not that it is problem of OpenWrt, just very frustrating.
My expectation was, that 5GHz support = all available channels - but apparently this is not the case.
I started playing around with the 3rd band channel and power settings and I believe I can reproduce the issue consistently.
Fri May 31 14:48:05 2019 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->HT_SCAN
Fri May 31 14:48:05 2019 daemon.notice hostapd: wlan0: interface state HT_SCAN->DFS
Fri May 31 14:48:05 2019 daemon.notice hostapd: wlan0: DFS-CAC-START freq=5500 chan=100 sec_chan=1, width=1, seg0=106, seg1=0, cac_time=60s
Fri May 31 14:48:29 2019 daemon.notice hostapd: wlan0: DFS-CAC-COMPLETED success=0 freq=5500 ht_enabled=0 chan_offset=0 chan_width=3 cf1=5530 cf2=0
Fri May 31 14:48:29 2019 kern.warn kernel: [ 286.650559] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
Fri May 31 14:48:29 2019 daemon.notice hostapd: wlan0: INTERFACE-DISABLED
Fri May 31 14:48:29 2019 kern.info kernel: [ 286.744667] br-office: port 3(wlan0) entered disabled state
Fri May 31 14:48:29 2019 kern.info kernel: [ 286.819462] device wlan0 left promiscuous mode
Fri May 31 14:48:29 2019 kern.info kernel: [ 286.819529] br-office: port 3(wlan0) entered disabled state
Fri May 31 14:48:29 2019 daemon.notice netifd: radio0 (3076): command failed: Not supported (-95)
Fri May 31 14:48:29 2019 user.notice mac80211: Failed command: iw phy phy0 set distance 0
Fri May 31 14:48:29 2019 daemon.notice netifd: radio0 (3076): sh: out of range
Fri May 31 14:48:29 2019 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Fri May 31 14:48:32 2019 kern.warn kernel: [ 289.353804] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
Fri May 31 14:48:32 2019 kern.warn kernel: [ 289.353849] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32
Fri May 31 14:48:32 2019 kern.info kernel: [ 289.408176] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
Fri May 31 14:48:32 2019 kern.info kernel: [ 289.409211] ath10k_pci 0000:01:00.0: wmi print 'free: 117936 iram: 22500 sram: 29708'
Fri May 31 14:48:32 2019 daemon.notice hostapd: wlan0: INTERFACE-ENABLED
Fri May 31 14:48:32 2019 kern.warn kernel: [ 289.712468] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Fri May 31 14:48:32 2019 kern.warn kernel: [ 289.714952] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
Fri May 31 14:48:32 2019 daemon.err hostapd: nl80211: Could not configure driver mode
Fri May 31 14:48:32 2019 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Fri May 31 14:48:32 2019 daemon.err hostapd: nl80211 driver initialization failed.
Fri May 31 14:48:32 2019 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->DISABLED
Fri May 31 14:48:32 2019 daemon.notice hostapd: wlan0: AP-DISABLED
Fri May 31 14:48:32 2019 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Fri May 31 14:48:32 2019 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0 wasn't started
Fri May 31 14:48:32 2019 daemon.notice hostapd: wlan0: INTERFACE-DISABLED
Fri May 31 14:48:32 2019 daemon.notice netifd: radio0 (3076): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 2558 path ()
Fri May 31 14:48:32 2019 daemon.notice netifd: radio0 (3076): Device setup failed: HOSTAPD_START_FAILED
Fri May 31 14:48:43 2019 daemon.notice netifd: radio0 (3280): command failed: Not supported (-95)
Fri May 31 14:48:43 2019 user.notice mac80211: Failed command: iw phy phy0 set distance 0
Fri May 31 14:48:43 2019 daemon.notice netifd: radio0 (3280): sh: out of range
Fri May 31 14:48:43 2019 kern.info kernel: [ 300.317944] IPv6: ADDRCONF(NETDEV_UP): tmp.radio0: link is not ready
Fri May 31 14:48:43 2019 kern.info kernel: [ 300.575925] IPv6: ADDRCONF(NETDEV_UP): tmp.radio0: link is not ready
Fri May 31 14:48:43 2019 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Fri May 31 14:48:45 2019 kern.warn kernel: [ 302.901420] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
Fri May 31 14:48:45 2019 kern.warn kernel: [ 302.901466] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32
Fri May 31 14:48:45 2019 kern.info kernel: [ 302.955943] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
Fri May 31 14:48:45 2019 kern.info kernel: [ 302.957556] ath10k_pci 0000:01:00.0: wmi print 'free: 117936 iram: 22500 sram: 29708'
Fri May 31 14:48:46 2019 daemon.notice hostapd: wlan0: INTERFACE-ENABLED
Fri May 31 14:48:46 2019 kern.warn kernel: [ 303.270962] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Fri May 31 14:48:46 2019 kern.warn kernel: [ 303.282462] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
Fri May 31 14:48:46 2019 daemon.notice hostapd: wlan0: INTERFACE-DISABLED
Fri May 31 14:48:46 2019 daemon.err hostapd: nl80211: Could not configure driver mode
Fri May 31 14:48:46 2019 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Fri May 31 14:48:46 2019 daemon.err hostapd: nl80211 driver initialization failed.
Fri May 31 14:48:46 2019 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->DISABLED
Fri May 31 14:48:46 2019 daemon.notice hostapd: wlan0: AP-DISABLED
Fri May 31 14:48:46 2019 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Fri May 31 14:48:46 2019 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0 wasn't started
Fri May 31 14:48:46 2019 daemon.notice netifd: radio0 (3280): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 2558 path ()
Fri May 31 14:48:46 2019 daemon.notice netifd: radio0 (3280): Device setup failed: HOSTAPD_START_FAILED
Fri May 31 14:49:04 2019 daemon.notice netifd: radio0 (3767): command failed: Not supported (-95)
Fri May 31 14:49:04 2019 user.notice mac80211: Failed command: iw phy phy0 set distance 0
Fri May 31 14:49:05 2019 daemon.notice netifd: radio0 (3767): sh: out of range
Fri May 31 14:49:05 2019 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Fri May 31 14:49:07 2019 kern.warn kernel: [ 324.544747] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
Fri May 31 14:49:07 2019 kern.warn kernel: [ 324.544801] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32
Fri May 31 14:49:07 2019 kern.info kernel: [ 324.599415] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
Fri May 31 14:49:07 2019 kern.info kernel: [ 324.601019] ath10k_pci 0000:01:00.0: wmi print 'free: 117936 iram: 22500 sram: 29708'
Fri May 31 14:49:07 2019 kern.warn kernel: [ 324.913100] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Fri May 31 14:49:07 2019 daemon.notice hostapd: wlan0: INTERFACE-ENABLED
Fri May 31 14:49:07 2019 kern.warn kernel: [ 324.925896] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
Fri May 31 14:49:07 2019 daemon.notice hostapd: wlan0: INTERFACE-DISABLED
Fri May 31 14:49:07 2019 daemon.err hostapd: nl80211: Could not configure driver mode
Fri May 31 14:49:07 2019 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Fri May 31 14:49:07 2019 daemon.err hostapd: nl80211 driver initialization failed.
Fri May 31 14:49:07 2019 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->DISABLED
Fri May 31 14:49:07 2019 daemon.notice hostapd: wlan0: AP-DISABLED
Fri May 31 14:49:07 2019 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Fri May 31 14:49:07 2019 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0 wasn't started
Fri May 31 14:49:07 2019 daemon.notice netifd: radio0 (3767): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 2558 path ()
Fri May 31 14:49:07 2019 daemon.notice netifd: radio0 (3767): Device setup failed: HOSTAPD_START_FAILED
This issue is only "fixable" with a reboot.
I believe this should be fixed, as non-experienced OpenWrt users (like myself) might run into the same issue, when playing around with the Wi-Fi settings in LuCi.
Of course this issue is simply avoidable by not selecting any "bad"/incompatible values at all.
Taking it one thing at a time, as my coffee hasn't hit quite yet (and, with apologies, as I seem to have forgotten to send this earlier)
Looking at the capability data, I agree that this is a setting that is not surprising that the driver rejects and that the GUI shouldn't be offering it if the capability for that radio on that channel is 13 dBm.
Wiphy phy0
max # scan SSIDs: 16
[...]
VHT TX highest supported: 0 Mbps
Frequencies:
* 5180 MHz [36] (disabled)
* 5200 MHz [40] (disabled)
* 5220 MHz [44] (disabled)
* 5240 MHz [48] (disabled)
* 5260 MHz [52] (disabled)
* 5280 MHz [56] (disabled)
* 5300 MHz [60] (disabled)
* 5320 MHz [64] (disabled)
* 5500 MHz [100] (26.0 dBm) (radar detection)
* 5520 MHz [104] (26.0 dBm) (radar detection)
* 5540 MHz [108] (26.0 dBm) (radar detection)
* 5560 MHz [112] (26.0 dBm) (radar detection)
* 5580 MHz [116] (26.0 dBm) (radar detection)
* 5600 MHz [120] (26.0 dBm) (radar detection)
* 5620 MHz [124] (26.0 dBm) (radar detection)
* 5640 MHz [128] (26.0 dBm) (radar detection)
* 5660 MHz [132] (26.0 dBm) (radar detection)
* 5680 MHz [136] (26.0 dBm) (radar detection)
* 5700 MHz [140] (26.0 dBm) (radar detection)
* 5720 MHz [144] (disabled)
* 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] (disabled)
* 5865 MHz [173] (disabled)
valid interface combinations:
* #{ managed } <= 16, #{ AP, mesh point } <= 16, #{ IBSS } <= 1,
total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }
[...]
Is there a bug tracker I can adress this to, or how is the general approach on that?
Thanks!
In my experience, it seems the "best way" is to at least find the cause, better to patch it yourself, and submit to the dev mailing list.
https://bugs.openwrt.org/ and the mailing list, even without a solution, but a clear, concise
is the path I'd take.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.