802.11s mesh interface doesn't come up

I'm trying to add a second router via 802.11s mesh to my main router following the manual in the wiki and the @onemarcfifty Video.
Unfortnuately my mesh doesn't come up :frowning: I installed wpad-mesh-openssl Here is my config:

cat /etc/config/wireless 

config wifi-device 'radio0'
	option type 'mac80211'
	option path '1e140000.pcie/pci0000:00/0000:00:01.0/0000:02:00.0'
	option band '2g'
	option htmode 'HT20'
	option channel '6'
	option cell_density '0'

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

config wifi-device 'radio1'
	option type 'mac80211'
	option path '1e140000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
	option band '5g'
	option cell_density '0'
	option channel '48'
	option htmode 'VHT80'

config wifi-iface 'wifinet1'
	option device 'radio0'
	option mode 'mesh'
	option encryption 'sae'
	option mesh_id 'my-mesh'
	option mesh_fwding '1'
	option mesh_rssi_threshold '0'
	option key 'test1234'
	option network 'lan'

This is what logread says:

Sat Dec 17 02:01:55 2022 daemon.notice netifd: Wireless device 'radio1' is now down
Sat Dec 17 02:01:56 2022 daemon.notice netifd: lan (2202): udhcpc: lease of 192.168.2.231 obtained from 192.168.2.1, lease time 43200
Sat Dec 17 02:01:56 2022 daemon.notice netifd: radio1 (5198): command failed: Link has been severed (-67)
Sat Dec 17 02:01:56 2022 daemon.notice netifd: radio1 (5198): command failed: Link has been severed (-67)
Sat Dec 17 02:01:56 2022 daemon.notice netifd: Wireless device 'radio1' is now up
Sat Dec 17 02:01:56 2022 kern.info kernel: [  130.394658] br-lan: port 3(mesh1) entered blocking state
Sat Dec 17 02:01:56 2022 kern.info kernel: [  130.399993] br-lan: port 3(mesh1) entered disabled state
Sat Dec 17 02:01:56 2022 kern.info kernel: [  130.406099] device mesh1 entered promiscuous mode
Sat Dec 17 02:01:57 2022 daemon.notice netifd: lan (2202): udhcpc: sending renew to server 192.168.2.1
Sat Dec 17 02:01:57 2022 daemon.notice netifd: lan (2202): udhcpc: lease of 192.168.2.231 obtained from 192.168.2.1, lease time 43200
Sat Dec 17 02:02:02 2022 daemon.notice wpa_supplicant[1278]: mesh1: interface state UNINITIALIZED->ENABLED
Sat Dec 17 02:02:02 2022 daemon.notice wpa_supplicant[1278]: mesh1: AP-ENABLED
Sat Dec 17 02:02:02 2022 daemon.notice wpa_supplicant[1278]: mesh1: joining mesh MMMesh
Sat Dec 17 02:02:02 2022 daemon.notice netifd: Network device 'mesh1' link is up
Sat Dec 17 02:02:02 2022 kern.info kernel: [  136.276200] IPv6: ADDRCONF(NETDEV_CHANGE): mesh1: link becomes ready
Sat Dec 17 02:02:02 2022 kern.info kernel: [  136.282853] br-lan: port 3(mesh1) entered blocking state
Sat Dec 17 02:02:02 2022 kern.info kernel: [  136.288155] br-lan: port 3(mesh1) entered forwarding state
Sat Dec 17 02:02:02 2022 daemon.notice wpa_supplicant[1278]: mesh1: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=0 id_str=]
Sat Dec 17 02:02:02 2022 daemon.notice wpa_supplicant[1278]: mesh1: MESH-GROUP-STARTED ssid="MMMesh" id=0
Sat Dec 17 02:03:10 2022 kern.info kernel: [  203.996880] device mesh1 left promiscuous mode
Sat Dec 17 02:03:10 2022 kern.info kernel: [  204.001563] br-lan: port 3(mesh1) entered disabled state
Sat Dec 17 02:03:10 2022 daemon.notice netifd: lan (2202): udhcpc: sending renew to server 192.168.2.1
Sat Dec 17 02:03:10 2022 daemon.notice netifd: lan (2202): udhcpc: lease of 192.168.2.231 obtained from 192.168.2.1, lease time 43200
Sat Dec 17 02:03:10 2022 daemon.notice wpa_supplicant[1278]: mesh1: MESH-GROUP-REMOVED mesh1
Sat Dec 17 02:03:10 2022 daemon.notice wpa_supplicant[1278]: mesh1: leaving mesh
Sat Dec 17 02:03:10 2022 daemon.notice wpa_supplicant[1278]: mesh1: interface state ENABLED->DISABLED
Sat Dec 17 02:03:10 2022 daemon.notice wpa_supplicant[1278]: mesh1: AP-DISABLED
Sat Dec 17 02:03:11 2022 daemon.notice wpa_supplicant[1278]: mesh1: CTRL-EVENT-DSCP-POLICY clear_all
Sat Dec 17 02:03:11 2022 daemon.notice wpa_supplicant[1278]: mesh1: CTRL-EVENT-DSCP-POLICY clear_all
Sat Dec 17 02:03:11 2022 daemon.notice wpa_supplicant[1278]: nl80211: deinit ifname=mesh1 disabled_11b_rates=0
Sat Dec 17 02:03:11 2022 daemon.err wpa_supplicant[1278]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Sat Dec 17 02:03:11 2022 daemon.notice netifd: Wireless device 'radio1' is now down
Sat Dec 17 02:03:11 2022 daemon.notice netifd: Wireless device 'radio1' is now up
Sat Dec 17 02:07:32 2022 daemon.notice netifd: radio0 (10578): command failed: Link has been severed (-67)
Sat Dec 17 02:07:32 2022 daemon.notice netifd: radio0 (10578): command failed: Link has been severed (-67)
Sat Dec 17 02:07:32 2022 daemon.notice netifd: Wireless device 'radio1' is now down
Sat Dec 17 02:07:32 2022 daemon.notice netifd: Wireless device 'radio1' is now up
Sat Dec 17 02:07:33 2022 daemon.notice wpa_supplicant[1278]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Sat Dec 17 02:07:33 2022 daemon.notice wpa_supplicant[1278]: wlan0: interface state UNINITIALIZED->ENABLED
Sat Dec 17 02:07:33 2022 daemon.notice wpa_supplicant[1278]: wlan0: AP-ENABLED
Sat Dec 17 02:07:33 2022 daemon.notice wpa_supplicant[1278]: wlan0: joining mesh my-mesh
Sat Dec 17 02:07:33 2022 daemon.notice wpa_supplicant[1278]: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=0 id_str=]
Sat Dec 17 02:07:33 2022 daemon.notice wpa_supplicant[1278]: wlan0: MESH-GROUP-STARTED ssid="my-mesh" id=0
Sat Dec 17 02:07:33 2022 kern.info kernel: [  466.877540] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sat Dec 17 02:07:34 2022 daemon.err mesh11sd[1680]: Error getting mesh interface name
Sat Dec 17 02:07:42 2022 daemon.notice netifd: Wireless device 'radio0' is now down
Sat Dec 17 02:07:42 2022 daemon.notice netifd: radio0 (10830): ip: SIOCSIFFLAGS: No error information
Sat Dec 17 02:07:42 2022 daemon.notice netifd: radio0 (10830): Interface 0 setup failed: IFUP_ERROR
Sat Dec 17 02:07:42 2022 daemon.notice wpa_supplicant[1278]: wlan0: MESH-GROUP-REMOVED wlan0
Sat Dec 17 02:07:42 2022 daemon.notice wpa_supplicant[1278]: wlan0: leaving mesh
Sat Dec 17 02:07:42 2022 daemon.notice wpa_supplicant[1278]: wlan0: interface state ENABLED->DISABLED
Sat Dec 17 02:07:42 2022 daemon.notice wpa_supplicant[1278]: wlan0: AP-DISABLED
Sat Dec 17 02:07:42 2022 daemon.notice wpa_supplicant[1278]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Sat Dec 17 02:07:42 2022 daemon.notice wpa_supplicant[1278]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Sat Dec 17 02:07:42 2022 daemon.notice wpa_supplicant[1278]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Sat Dec 17 02:07:42 2022 daemon.err wpa_supplicant[1278]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Sat Dec 17 02:07:42 2022 daemon.notice netifd: Wireless device 'radio0' is now up
Sat Dec 17 02:07:54 2022 daemon.notice mesh11sd[1680]: mesh0 is not up - giving up for now.
Sat Dec 17 02:08:14 2022 daemon.notice mesh11sd[1680]: mesh0 is not up - giving up for now.
Sat Dec 17 02:08:35 2022 daemon.notice mesh11sd[1680]: mesh0 is not up - giving up for now.
Sat Dec 17 02:08:55 2022 daemon.notice mesh11sd[1680]: mesh0 is not up - giving up for now.
Sat Dec 17 02:08:56 2022 authpriv.info dropbear[11754]: Child connection from 192.168.2.225:47284
Sat Dec 17 02:08:58 2022 authpriv.notice dropbear[11754]: Auth succeeded with blank password for 'root' from 192.168.2.225:47284
Sat Dec 17 02:09:15 2022 daemon.notice mesh11sd[1680]: mesh0 is not up - giving up for now.
Sat Dec 17 02:09:36 2022 daemon.notice mesh11sd[1680]: mesh0 is not up - giving up for now.
Sat Dec 17 02:09:56 2022 daemon.notice mesh11sd[1680]: mesh0 is not up - giving up for now.

By coincidence the devices are exactly the same as in the video. TP-Link Archer C7v2 as the main device and a Xiaomi Mi4 Gigabit as a second one. Both with OpenWrt 22.03.2. I tried on 5GHz first, with and without encryption, but no difference.

Do you have an idea why the mesh interface doesn't come up?

1 Like

do younhas try package mesh11sd

normally younare 2 interface Like this

Yes, I have installed mesh11sd on both devices. The log output therefore is a bit better, but it doesn't solve the problem.
I have activated mesh only on one interface, but it doesn't matter if I use 2,4 or 5 GHz.

You have to use ath10k and not ath10k-ct.