Issues with mac80211.sh: wpa_supplicant_run: not found

Installing and Using OpenWrt Network and Wireless Configuration
1

hi,

I have recently updated my device and I find that after this step of upgrade process the mesh network that I have has stopped working. It seems that the wpa3 auth does not activate it and I get this error in the log.

ue Sep 12 10:42:01 2023 daemon.notice netifd: radio0 (7050): ./mac80211.sh: eval: line 871: wpa_supplicant_run: not found
Tue Sep 12 10:42:01 2023 daemon.notice netifd: radio0 (7050): command failed: Link has been severed (-67)
Tue Sep 12 10:42:01 2023 daemon.notice netifd: radio0 (7050): command failed: Link has been severed (-67)

here version of openwrt:

 -----------------------------------------------------
 OpenWrt SNAPSHOT, r23375-cdfcac6e24
 -----------------------------------------------------
root@ro-:~# uname -a
Linux ro- 6.1.33 #0 SMP Wed Jun 14 21:27:29 2023 aarch64 GNU/Linux

any idea?

thanks for your support!

2

What happens with stable version 22.03.5 or 23.05.0-rc3?

3

How did you upgrade recently to a 3-month old snapshot? That wpa_supplicant_run code has been replaced since August 1. Did you run opkg upgrade mistakenly?

3 Likes
4

I have a router redmi ax6, but in this web https://firmware-selector.openwrt.org/ for my model I can't find the stable version :-/
do you know how I could do if it is not installing the SNAPSHOT ?

5

I ran it using this website a snapshot
any other suggestion?

6

RC3, if available for your device ...

7

For snapshots, you must now use the qualcommax/ipq807x target instead of ipq807x/generic when downloading for your model. On the 23.05 branch, it’s still ipq807x/generic.

2 Likes
8

I got the same on my Xiaomi AX3600 with [LuCI openwrt-23.05 branch (git-23.236.53405-fc638c8)] / [OpenWrt 23.05.0-rc3 (r23389-5deed175a5)]

I can not get mesh running well.

Wed Sep 20 23:01:51 2023 daemon.notice netifd: radio1 (3532): ./mac80211.sh: eval: line 871: wpa_supplicant_run: not found
Wed Sep 20 23:01:51 2023 daemon.notice netifd: radio1 (3532): command failed: Link has been severed (-67)
Wed Sep 20 23:01:51 2023 daemon.notice netifd: radio1 (3532): command failed: Link has been severed (-67)

...

Wed Sep 20 23:01:53 2023 daemon.notice mesh11sd[25791]: m-11s-0 is not up - giving up for now.
9

@doreks @itsmeagain
Have you removed the default wpad and installed wpad-mbedtls?
Without doing this you will get the errors seen...

10

Same problem:
``

daemon.notice netifd: radio0 (3516): ./mac80211.sh: eval: line 871: wpa_supplicant_run: not found

OpenWrt 23.05.0-rc3, r23389-5deed175a5
wpad-mbedtls - 2023-09-08-e5ccbfc6-3

customized on firmware-selector.openwrt.org, by packages and custom init

for device BPI-R3

also there a problem in same script with 'radio_config_id' and hostapd does not recognize this option in generated config.

11

I finally got my own snapshop using qualcommax/ipq807x. This way I have been able to run the mesh network again without any problems.

12

Installed wpad-mbedtls but issues not fixed

Sun Sep 24 00:10:37 2023 daemon.notice netifd: radio0 (14799): ./mac80211.sh: eval: line 871: wpa_supplicant_run: not found
Sun Sep 24 00:10:37 2023 daemon.notice netifd: radio0 (14799): command failed: Link has been severed (-67)
Sun Sep 24 00:10:37 2023 daemon.notice netifd: radio0 (14799): command failed: Link has been severed (-67)
13

So which one is it?

14

Show the output of:
iw list | grep -A 10 "Supported interface modes:"

15

Sorry, I Two routers running openwrt, one of them fixed with custum firmware and second one with stock firmware having issues..

16

this is the print out from my ax3600

	Supported interface modes:
		 * managed
		 * AP
		 * monitor
		 * mesh point
	Band 1:
		Capabilities: 0x11e7
			RX LDPC
			HT20/HT40
			Dynamic SM Power Save
			RX HT20 SGI
--
	Supported interface modes:
		 * managed
		 * AP
		 * monitor
		 * mesh point
	Band 2:
		Capabilities: 0x19e7
			RX LDPC
			HT20/HT40
			Dynamic SM Power Save
			RX HT20 SGI
--
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
		 * mesh point
		 * P2P-client
		 * P2P-GO
		 * P2P-device
	Band 1:

thanks for your support!

17

I can only duplicate these errors if I have wpad basic.
Also if I upgrade to wpad-mbdtls (or wpad-mesh-mbedtls) but have not rebooted after the upgrade, I still get the errors.
Presumably you have rebooted since?

You could try, for test purposes, turning encryption off and see if the interface then comes up.