Client(WDS)/802.11s Mesh not working on MT7915E(NWA50AX/NWA55AXE)

I haven't been able to find discussions/info that would have solved this.

On both NWA50AX and NWA55AXE devices all three options of Client/802.11s/Client(WDS) makes luci give an error for requires wpa_supplicant with SAE support even tho I have the full wpad-mbedtls installed on both and I have also tried full versions of openssl and wolfssl with no luck. A full version of one of the wpad packages should be enough, right? I also tried installing mesh11sd but it didn't help either.

I can see that on an RT3200 luci does not give the same error. Both NWA's have a MT7915E wlan chip that is also in the RT3200, so idk any more.

RT3200 and NWA's are running version 23.05.3 and iw list lists -* mesh point under supported modes. I've seen discussion from other people saying that they are running a NWA55AXE as a mesh point. So the hw should be capable of meshing as the iw list suggests.

Am I missing a package? Is this a driver/firmware issue/bug?
opkg list-installed from NWA50AX

attendedsysupgrade-common - 8
base-files - 1554-r23809-234f1a2efa
busybox - 1.36.1-1
ca-bundle - 20230311-1
cgi-io - 2022-08-10-901b0f04-21
dnsmasq - 2.90-2
dropbear - 2022.82-6
firewall4 - 2023-09-01-598d9fbb-1
fstools - 2023-02-28-bfe882d5-1
fwtool - 2019-11-12-8f7fe925-1
getrandom - 2022-08-13-4c7b720b-2
hostapd-common - 2023-09-08-e5ccbfc6-6
iw - 5.19-1
iwinfo - 2023-07-01-ca79f641-1
jansson4 - 2.14-3
jshn - 2023-05-23-75a3b870-1
jsonfilter - 2024-01-23-594cfa86-1
kernel - 5.15.150-1-bee655e7f41679981b85a223f3aba35b
kmod-cfg80211 - 5.15.150+6.1.24-3
kmod-crypto-acompress - 5.15.150-1
kmod-crypto-aead - 5.15.150-1
kmod-crypto-ccm - 5.15.150-1
kmod-crypto-cmac - 5.15.150-1
kmod-crypto-crc32c - 5.15.150-1
kmod-crypto-ctr - 5.15.150-1
kmod-crypto-gcm - 5.15.150-1
kmod-crypto-gf128 - 5.15.150-1
kmod-crypto-ghash - 5.15.150-1
kmod-crypto-hash - 5.15.150-1
kmod-crypto-hmac - 5.15.150-1
kmod-crypto-manager - 5.15.150-1
kmod-crypto-null - 5.15.150-1
kmod-crypto-rng - 5.15.150-1
kmod-crypto-seqiv - 5.15.150-1
kmod-crypto-sha512 - 5.15.150-1
kmod-gpio-button-hotplug - 5.15.150-3
kmod-hwmon-core - 5.15.150-1
kmod-leds-gpio - 5.15.150-1
kmod-lib-crc-ccitt - 5.15.150-1
kmod-lib-crc32c - 5.15.150-1
kmod-lib-lzo - 5.15.150-1
kmod-mac80211 - 5.15.150+6.1.24-3
kmod-mt76-connac - 5.15.150+2023-09-11-f1e1e67d-1
kmod-mt76-core - 5.15.150+2023-09-11-f1e1e67d-1
kmod-mt7915-firmware - 5.15.150+2023-09-11-f1e1e67d-1
kmod-mt7915e - 5.15.150+2023-09-11-f1e1e67d-1
kmod-nf-conntrack - 5.15.150-1
kmod-nf-conntrack6 - 5.15.150-1
kmod-nf-flow - 5.15.150-1
kmod-nf-log - 5.15.150-1
kmod-nf-log6 - 5.15.150-1
kmod-nf-nat - 5.15.150-1
kmod-nf-reject - 5.15.150-1
kmod-nf-reject6 - 5.15.150-1
kmod-nfnetlink - 5.15.150-1
kmod-nft-core - 5.15.150-1
kmod-nft-fib - 5.15.150-1
kmod-nft-nat - 5.15.150-1
kmod-nft-offload - 5.15.150-1
kmod-ppp - 5.15.150-1
kmod-pppoe - 5.15.150-1
kmod-pppox - 5.15.150-1
kmod-slhc - 5.15.150-1
kmod-thermal - 5.15.150-1
libblobmsg-json20230523 - 2023-05-23-75a3b870-1
libc - 1.2.4-4
libgcc1 - 12.3.0-4
libiwinfo-data - 2023-07-01-ca79f641-1
libiwinfo20230701 - 2023-07-01-ca79f641-1
libjson-c5 - 0.16-3
libjson-script20230523 - 2023-05-23-75a3b870-1
liblucihttp-ucode - 2023-03-15-9b5b683f-1
liblucihttp0 - 2023-03-15-9b5b683f-1
libmbedtls12 - 2.28.7-2
libmnl0 - 1.0.5-1
libnftnl11 - 1.2.6-1
libnl-tiny1 - 2023-07-27-bc92a280-1
libpthread - 1.2.4-4
libubox20230523 - 2023-05-23-75a3b870-1
libubus20230605 - 2023-06-05-f787c97b-1
libuci20130104 - 2023-08-10-5781664d-1
libuclient20201210 - 2023-04-13-007d9454-1
libucode20230711 - 2023-11-07-a6e75e02-1
libustream-mbedtls20201210 - 2023-02-25-498f6e26-1
logd - 2022-08-13-4c7b720b-2
luci - git-23.051.66410-a505bb1
luci-app-attendedsysupgrade - git-23.339.51123-138595a
luci-app-firewall - git-24.067.01746-69867db
luci-app-opkg - git-24.043.63812-c89a68b
luci-base - git-24.086.45142-09d5a38
luci-light - git-23.024.33244-34dee82
luci-mod-admin-full - git-19.253.48496-3f93650
luci-mod-network - git-24.111.76511-ff6b275
luci-mod-status - git-24.087.58493-9370bdd
luci-mod-system - git-24.067.01860-7a82b2f
luci-proto-ipv6 - git-24.086.45108-51aee90
luci-proto-ppp - git-24.135.44542-f1ec9c2
luci-ssl - git-23.035.26083-7550ad6
luci-theme-bootstrap - git-24.086.46634-1ffe078
mtd - 26
netifd - 2024-01-04-c18cc79d-2
nftables-json - 1.0.8-1
odhcp6c - 2023-05-12-bcd28363-20
odhcpd-ipv6only - 2023-10-24-d8118f6e-1
openwrt-keyring - 2022-03-25-62471e69-2
opkg - 2022-02-24-d038e5b6-2
ppp - 2.4.9.git-2021-01-04-4
ppp-mod-pppoe - 2.4.9.git-2021-01-04-4
procd - 2023-06-25-2db83655-2
procd-seccomp - 2023-06-25-2db83655-2
procd-ujail - 2023-06-25-2db83655-2
px5g-mbedtls - 10
rpcd - 2023-07-01-c07ab2f9-1
rpcd-mod-file - 2023-07-01-c07ab2f9-1
rpcd-mod-iwinfo - 2023-07-01-c07ab2f9-1
rpcd-mod-luci - 20240305-1
rpcd-mod-rpcsys - 2023-07-01-c07ab2f9-1
rpcd-mod-rrdns - 20170710
rpcd-mod-ucode - 2023-07-01-c07ab2f9-1
ubi-utils - 2.1.5-1
uboot-envtools - 2023.04-1
ubox - 2022-08-13-4c7b720b-2
ubus - 2023-06-05-f787c97b-1
ubusd - 2023-06-05-f787c97b-1
uci - 2023-08-10-5781664d-1
uclient-fetch - 2023-04-13-007d9454-1
ucode - 2023-11-07-a6e75e02-1
ucode-mod-fs - 2023-11-07-a6e75e02-1
ucode-mod-html - 1
ucode-mod-math - 2023-11-07-a6e75e02-1
ucode-mod-nl80211 - 2023-11-07-a6e75e02-1
ucode-mod-rtnl - 2023-11-07-a6e75e02-1
ucode-mod-ubus - 2023-11-07-a6e75e02-1
ucode-mod-uci - 2023-11-07-a6e75e02-1
ucode-mod-uloop - 2023-11-07-a6e75e02-1
uhttpd - 2023-06-25-34a8a74d-2
uhttpd-mod-ubus - 2023-06-25-34a8a74d-2
urandom-seed - 3
urngd - 2023-11-01-44365eb1-1
usign - 2020-05-23-f1f65026-1
wireless-regdb - 2024.01.23-1
wpad-mbedtls - 2023-09-08-e5ccbfc6-6
zyxel-bootconfig - 1

you need to have the package wpad-mesh-mbedtls installed to support 802.11s.

No you don’t, wpad-mbedtls is the full package.

Assuming your wireless drivers support 802.11s, once you have removed wpad-basic-mbedtls and installed wpad-mbedtls (or wpad-mesh-mbettls) you have to either restart wpad or reboot.

service wpad restart should do it.

I always rebooted after swapping an installed wpad package and SSHing into the APs and running iw list command it shows that mesh point is supported.

But your comment about rebooting got me thinking about startup and rebooting.
OpenWrt Dumb Access Point guide has a startup script that disables unwanted daemons for a dumbAP on startup. I had copied the entire script with no real thought when I had setup my APs as dumpAPs. The script also has a line for

rm /usr/sbin/wpa_supplicant

which seemed like it would be causing this issue.

I removed the line from the script, re-flashed openwrt with attended sysupgrade and kept the same configuration(just to "easily" get back to a "baseline" install).

No longer getting the error : )
(P.S what a tearing my hair out situation this was for me)

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