Mesh 5GHz UniFi AC Lite not working

olegvekhov · December 5, 2019, 7:58pm

Hello! Has successfully setup mesh network on other devices, but no luck on UniFi AC Lite.

Tried on 18.06.5 and on latest trunk (last build today)...
Interface not showing up. Nothing works.

If i change radio0 to radio1 the 2.4ghz iface work perfectly with mesh.
5GHz Wifi in AP mode works perfectly

If I do ifconfig wlan0 up:

ifconfig: SIOCSIFFLAGS: Resource busy

Here is config:

config wifi-iface 'wifinet3'
        option network 'lan'
        option mesh_rssi_threshold '0'
        option key 'mykey'
        option encryption 'sae'
        option device 'radio0'
        option mode 'mesh'
        option mesh_fwding '1'
        option mesh_id 'dupamesh5'

Here is more info:

 Dec  5 22:52:10 2019 kern.info kernel: [  740.118889] br-lan: port 4(wlan1) entered disabled state
Thu Dec  5 22:52:10 2019 kern.info kernel: [  740.129076] br-lan: port 4(wlan1) entered disabled state
Thu Dec  5 22:52:10 2019 daemon.notice hostapd: wlan1-1: AP-DISABLED
Thu Dec  5 22:52:10 2019 daemon.notice hostapd: wlan1-1: CTRL-EVENT-TERMINATING
Thu Dec  5 22:52:10 2019 daemon.notice hostapd: nl80211: deinit ifname=wlan1-1 disabled_11b_rates=0
Thu Dec  5 22:52:10 2019 kern.info kernel: [  740.142955] device wlan1-1 left promiscuous mode
Thu Dec  5 22:52:10 2019 kern.info kernel: [  740.147858] br-lan: port 2(wlan1-1) entered disabled state
Thu Dec  5 22:52:10 2019 daemon.notice netifd: Network device 'wlan0-1' link is down
Thu Dec  5 22:52:10 2019 daemon.notice netifd: Network device 'wlan1-1' link is down
Thu Dec  5 22:52:11 2019 daemon.notice netifd: radio0 (3831): sh: out of range
Thu Dec  5 22:52:11 2019 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Thu Dec  5 22:52:12 2019 kern.warn kernel: [  742.144577] ath10k_pci 0000:00:00.0: 10.1 wmi init: vdevs: 16  peers: 127  tid: 256
Thu Dec  5 22:52:12 2019 kern.info kernel: [  742.162683] ath10k_pci 0000:00:00.0: wmi print 'P 128 V 8 T 410'
Thu Dec  5 22:52:12 2019 kern.info kernel: [  742.169164] ath10k_pci 0000:00:00.0: wmi print 'msdu-desc: 1424  sw-crypt: 0 ct-sta: 0'
Thu Dec  5 22:52:12 2019 kern.info kernel: [  742.177435] ath10k_pci 0000:00:00.0: wmi print 'alloc rem: 20904 iram: 26072'
Thu Dec  5 22:52:12 2019 kern.warn kernel: [  742.249936] ath10k_pci 0000:00:00.0: pdev param 0 not supported by firmware
Thu Dec  5 22:52:12 2019 kern.info kernel: [  742.269876] br-lan: port 2(wlan0-1) entered blocking state
Thu Dec  5 22:52:12 2019 kern.info kernel: [  742.275554] br-lan: port 2(wlan0-1) entered disabled state
Thu Dec  5 22:52:12 2019 kern.info kernel: [  742.281516] device wlan0-1 entered promiscuous mode
Thu Dec  5 22:52:12 2019 daemon.err hostapd: Using interface wlan0-1 with hwaddr 1a:e8:29:cb:8d:54 and ssid "CosattoSupaDupa"
Thu Dec  5 22:52:12 2019 kern.info kernel: [  742.356941] br-lan: port 2(wlan0-1) entered blocking state
Thu Dec  5 22:52:12 2019 kern.info kernel: [  742.362667] br-lan: port 2(wlan0-1) entered forwarding state
Thu Dec  5 22:52:12 2019 daemon.notice hostapd: wlan0-1: interface state UNINITIALIZED->ENABLED
Thu Dec  5 22:52:12 2019 daemon.notice hostapd: wlan0-1: AP-ENABLED
Thu Dec  5 22:52:12 2019 daemon.notice wpa_supplicant[3770]: nl80211: Failed to set interface into station mode
Thu Dec  5 22:52:12 2019 daemon.err wpa_supplicant[3770]:  Failed to stop hostapd AP interfaces
Thu Dec  5 22:52:12 2019 daemon.notice wpa_supplicant[3770]: nl80211: deinit ifname=wlan1 disabled_11b_rates=0
Thu Dec  5 22:52:12 2019 kern.info kernel: [  742.408993] br-lan: port 4(wlan1) entered disabled state
Thu Dec  5 22:52:12 2019 daemon.notice netifd: radio0 (3831): RTNETLINK answers: Resource busy
Thu Dec  5 22:52:12 2019 daemon.notice netifd: radio0 (3831): Interface 1 setup failed: IFUP_ERROR
Thu Dec  5 22:52:12 2019 daemon.notice netifd: Network device 'wlan0-1' link is up
Thu Dec  5 22:52:13 2019 daemon.info hostapd: wlan0-1: STA ac:ed:5c:85:64:9d IEEE 802.11: authenticated
Thu Dec  5 22:52:13 2019 daemon.info hostapd: wlan0-1: STA ac:ed:5c:85:64:9d IEEE 802.11: associated (aid 1)
Thu Dec  5 22:52:13 2019 daemon.notice hostapd: wlan0-1: AP-STA-CONNECTED ac:ed:5c:85:64:9d
Thu Dec  5 22:52:13 2019 daemon.info hostapd: wlan0-1: STA ac:ed:5c:85:64:9d RADIUS: starting accounting session EFA95906A08F49F8
Thu Dec  5 22:52:13 2019 daemon.info hostapd: wlan0-1: STA ac:ed:5c:85:64:9d WPA: pairwise key handshake completed (RSN)
Thu Dec  5 22:52:13 2019 daemon.info dnsmasq-dhcp[2649]: DHCPREQUEST(br-lan) 192.168.249.232 ac:ed:5c:85:64:9d
Thu Dec  5 22:52:13 2019 daemon.info dnsmasq-dhcp[2649]: DHCPACK(br-lan) 192.168.249.232 ac:ed:5c:85:64:9d tg-guestroom
Thu Dec  5 22:52:13 2019 daemon.info hostapd: wlan0-1: STA 00:0a:f5:5d:5c:94 IEEE 802.11: authenticated
Thu Dec  5 22:52:13 2019 daemon.info hostapd: wlan0-1: STA 00:0a:f5:5d:5c:94 IEEE 802.11: associated (aid 2)
Thu Dec  5 22:52:13 2019 daemon.notice hostapd: wlan0-1: AP-STA-CONNECTED 00:0a:f5:5d:5c:94
Thu Dec  5 22:52:13 2019 daemon.info hostapd: wlan0-1: STA 00:0a:f5:5d:5c:94 RADIUS: starting accounting session 072287BD75115C8B
Thu Dec  5 22:52:13 2019 daemon.info hostapd: wlan0-1: STA 00:0a:f5:5d:5c:94 WPA: pairwise key handshake completed (RSN)
Thu Dec  5 22:52:13 2019 daemon.info dnsmasq-dhcp[2649]: DHCPDISCOVER(br-lan) 00:0a:f5:5d:5c:94
Thu Dec  5 22:52:13 2019 daemon.info dnsmasq-dhcp[2649]: DHCPOFFER(br-lan) 192.168.249.104 00:0a:f5:5d:5c:94
Thu Dec  5 22:52:13 2019 daemon.info dnsmasq-dhcp[2649]: DHCPREQUEST(br-lan) 192.168.249.104 00:0a:f5:5d:5c:94
Thu Dec  5 22:52:13 2019 daemon.info dnsmasq-dhcp[2649]: DHCPACK(br-lan) 192.168.249.104 00:0a:f5:5d:5c:94 MIPAD4PLUS-MiPad
Thu Dec  5 22:52:13 2019 daemon.notice wpa_supplicant[3770]: wlan1: CTRL-EVENT-TERMINATING
Thu Dec  5 22:52:13 2019 daemon.notice wpa_supplicant[3770]: ELOOP: remaining socket: sock=25 eloop_data=0x5d1620 user_data=0 handler=0x46b105
Thu Dec  5 22:52:13 2019 kern.info kernel: [  743.498226] br-lan: port 4(wlan1) entered disabled state
Thu Dec  5 22:52:13 2019 kern.info kernel: [  743.512971] device wlan1 left promiscuous mode
Thu Dec  5 22:52:13 2019 kern.info kernel: [  743.517887] br-lan: port 4(wlan1) entered disabled state
Thu Dec  5 22:52:14 2019 daemon.notice netifd: radio1 (3974): sh: out of range
Thu Dec  5 22:52:14 2019 daemon.err hostapd: Configuration file: /var/run/hostapd-phy1.conf
Thu Dec  5 22:52:14 2019 kern.info kernel: [  744.488447] br-lan: port 3(wlan1-1) entered blocking state
Thu Dec  5 22:52:14 2019 kern.info kernel: [  744.494318] br-lan: port 3(wlan1-1) entered disabled state
Thu Dec  5 22:52:14 2019 kern.info kernel: [  744.500324] device wlan1-1 entered promiscuous mode
Thu Dec  5 22:52:14 2019 daemon.err hostapd: Using interface wlan1-1 with hwaddr 1a:e8:29:ca:8d:54 and ssid "CosattoSupaDupa"
Thu Dec  5 22:52:14 2019 kern.info kernel: [  744.623594] br-lan: port 3(wlan1-1) entered blocking state
Thu Dec  5 22:52:14 2019 kern.info kernel: [  744.629308] br-lan: port 3(wlan1-1) entered forwarding state
Thu Dec  5 22:52:14 2019 daemon.notice hostapd: wlan1-1: interface state UNINITIALIZED->ENABLED
Thu Dec  5 22:52:14 2019 daemon.notice hostapd: wlan1-1: AP-ENABLED
Thu Dec  5 22:52:15 2019 daemon.notice wpa_supplicant[4117]: Successfully initialized wpa_supplicant
Thu Dec  5 22:52:15 2019 daemon.notice netifd: radio1 (3974): command failed: Link has been severed (-67)
Thu Dec  5 22:52:15 2019 user.notice mac80211: Failed command: iw dev wlan1 set mesh_param mesh_rssi_threshold 0
Thu Dec  5 22:52:15 2019 daemon.notice netifd: radio1 (3974): command failed: Link has been severed (-67)
Thu Dec  5 22:52:15 2019 user.notice mac80211: Failed command: iw dev wlan1 set mesh_param mesh_fwding 1
Thu Dec  5 22:52:15 2019 kern.info kernel: [  745.046368] br-lan: port 4(wlan1) entered blocking state
Thu Dec  5 22:52:15 2019 kern.info kernel: [  745.051919] br-lan: port 4(wlan1) entered disabled state
Thu Dec  5 22:52:15 2019 kern.info kernel: [  745.057918] device wlan1 entered promiscuous mode
Thu Dec  5 22:52:15 2019 kern.info kernel: [  745.478110] br-lan: port 3(wlan1-1) entered disabled state

jeff · December 5, 2019, 8:37pm

Try the non-CT ath10k drivers and firmware. “Wave 1” chips, which your device may have, are not supported for mesh by the -CT drivers and firmware.

olegvekhov · December 6, 2019, 7:59pm

Thank you for reply! I tried to compile with CT drivers and firmware just to try. The same situation happens with standart drivers - the same identical error messages

jeff · December 6, 2019, 11:39pm

Perhaps a typo or misunderstanding, the Wave 1 chips need the "regular" ath10k drivers and firmware to run mesh, not the default ath10k-CT ones.

mk24 · December 7, 2019, 12:14am

This is a Wave 1 device. Make sure the firmware and the driver are both mainline, not CT. Make sure you have set the radio to your country code. Mesh operations require all nodes to be set explicitly to the same channel, and for that reason DFS channels can't be used.

It looks like you're trying to bring up two interfaces on the radio, to simplify things test with just the mesh.

olegvekhov · December 8, 2019, 12:24am

Finally I can start mesh. I compiled 19.07 rc2 from scratch, deleted my old dirs, with non-CT drivers for ath10k.

Now I fall into other issue: daemon.notice wpa_supplicant[1904]: wlan1: MESH-SAE-AUTH-FAILURE addr=78:a3:51:08:13:ac

This message is on two devices (miwifi mini and my Ubiquity AC lite). This is not related to ath10k driver - i tried to switch to 2,4 GHz wifi and got the same message. I tried wpad-mesh-openssl and wpad-mesh-wolfssl - same error. Two routers has 19.07-rc2