OpenWrt/LEDE Project

  • Status Unconfirmed
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Base system
  • Assigned To No-one
  • Operating System All
  • Severity High
  • Priority Very Low
  • Reported Version openwrt-21.02
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by Márton Maráz - 27.11.2021

FS#4159 - hostapd-common update breaks WiFi completely when using the config file for the previous version

- Device problem occurs on

Linksys EA8300 AC2200 (advanced WiFi config - 802.11r related settings and a lots of other advanced settings are also modified compared to the default)
Raspberry Pi 4B+ (simple WiFi config - only SSID and password settings are modified)

- Software versions of OpenWrt/LEDE release, packages, etc.

Linksys EA8300: 21.02
Raspberry Pi 4B+: 21.02.1

- Steps to reproduce

`opkg upgrade hostapd-common`

It happened for me when I upgraded to 2020-06-08-5a8b3662-35 (the current latest release published on 2021-11-25) from the previous version or the one before that, I don’t exactly know, but I’m sure that I kept my packages up-to-date on a weekly basis recently, so my previous version cannot be older than 7 days.

I’ve got this error message in the system log on both of my devices:

Sat Nov 27 16:05:40 2021 daemon.notice netifd: radio0 (10527): command failed: No error information (-524)
Sat Nov 27 16:05:40 2021 daemon.notice netifd: radio0 (10527): command failed: I/O error (-5)
Sat Nov 27 16:05:41 2021 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy wlan0) –> new PHY
Sat Nov 27 16:05:41 2021 daemon.err hostapd: Line 47: unknown configuration item ‘snoop_iface’ Sat Nov 27 16:05:41 2021 daemon.err hostapd: Line 54: unknown configuration item ‘vlan_no_bridge’ Sat Nov 27 16:05:41 2021 daemon.err hostapd: Line 56: unknown configuration item ‘qos_map_set’ Sat Nov 27 16:05:41 2021 daemon.err hostapd: 3 errors found in configuration file ‘/var/run/hostapd-phy0.conf’ Sat Nov 27 16:05:41 2021 daemon.err hostapd: Failed to set up interface with /var/run/hostapd-phy0.conf
Sat Nov 27 16:05:41 2021 daemon.notice netifd: radio0 (10527): Command failed: Invalid argument
Sat Nov 27 16:05:41 2021 daemon.notice netifd: radio0 (10527): Device setup failed: HOSTAPD_START_FAILED
Sat Nov 27 16:05:41 2021 daemon.notice netifd: Wireless device ‘radio0’ set retry=0
Sat Nov 27 16:05:41 2021 daemon.crit netifd: Wireless device ‘radio0’ setup failed, retry=0
Sat Nov 27 16:05:42 2021 daemon.notice netifd: Wireless device ‘radio0’ is now down

Márton Maráz commented on 27.11.2021 17:37

Sorry, I mistaken the latest version of hostapd-common!

It's 2020-06-08-5a8b3662-37, and NOT 2020-06-08-5a8b3662-35.

And I also mistaken the Raspbery Pi's model name. It's not 4B+ (no such model exists). It's 4B (and by the way it has 4GB RAM)

Can someone with the appropriate rights modify the report's description please?

Michael C Wescott commented on 28.11.2021 17:25

Also seen on Netgear R8000 (BCM4709) with OpenWrt 21.02.1 r16325-88151b8303 / LuCI openwrt-21.02 branch git-21.295.67054-13df80d.

Upgrade of hostapd-common kills all wireless.

Michael C Wescott commented on 28.11.2021 20:29

Also occurs with

Buffalo WZR-600DHP
OpenWrt 21.02.1 r16325-88151b8303

Upgrade to

Syslog:
Sun Nov 28 20:13:03 2021 daemon.notice hostapd: wlan0: AP-DISABLED
Sun Nov 28 20:13:03 2021 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Sun Nov 28 20:13:03 2021 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Sun Nov 28 20:13:03 2021 kern.info kernel: [ 945.088067] device wlan0 left promiscuous mode
Sun Nov 28 20:13:03 2021 kern.info kernel: [ 945.092801] br-lan: port 3(wlan0) entered disabled state
Sun Nov 28 20:13:03 2021 daemon.notice netifd: Network device 'wlan0' link is down
Sun Nov 28 20:13:03 2021 daemon.notice wpa_supplicant[3497]: Successfully initialized wpa_supplicant
Sun Nov 28 20:13:04 2021 daemon.notice netifd: radio0 (3520): Command failed: Invalid argument
Sun Nov 28 20:13:04 2021 daemon.notice netifd: radio1 (3521): Command failed: Invalid argument
Sun Nov 28 20:13:06 2021 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy wlan0) –> new PHY
Sun Nov 28 20:13:06 2021 daemon.err hostapd: Line 41: unknown configuration item 'snoop_iface'
Sun Nov 28 20:13:06 2021 daemon.err hostapd: Line 48: unknown configuration item 'vlan_no_bridge'
Sun Nov 28 20:13:06 2021 daemon.err hostapd: Line 50: unknown configuration item 'qos_map_set'
Sun Nov 28 20:13:06 2021 daemon.err hostapd: 3 errors found in configuration file '/var/run/hostapd-phy0.conf'
Sun Nov 28 20:13:06 2021 daemon.err hostapd: Failed to set up interface with /var/run/hostapd-phy0.conf
Sun Nov 28 20:13:06 2021 daemon.notice netifd: radio0 (3545): Command failed: Invalid argument
Sun Nov 28 20:13:06 2021 daemon.notice netifd: radio0 (3545): Device setup failed: HOSTAPD_START_FAILED
Sun Nov 28 20:13:06 2021 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy1.conf (phy wlan1) –> new PHY
Sun Nov 28 20:13:06 2021 daemon.err hostapd: Line 39: unknown configuration item 'snoop_iface'
Sun Nov 28 20:13:06 2021 daemon.err hostapd: Line 46: unknown configuration item 'vlan_no_bridge'
Sun Nov 28 20:13:06 2021 daemon.err hostapd: Line 48: unknown configuration item 'qos_map_set'
Sun Nov 28 20:13:06 2021 daemon.err hostapd: 3 errors found in configuration file '/var/run/hostapd-phy1.conf'
Sun Nov 28 20:13:06 2021 daemon.err hostapd: Failed to set up interface with /var/run/hostapd-phy1.conf
Sun Nov 28 20:13:06 2021 daemon.notice netifd: radio1 (3547): Command failed: Invalid argument
Sun Nov 28 20:13:06 2021 daemon.notice netifd: radio1 (3547): Device setup failed: HOSTAPD_START_FAILED

Admin
Jo-Philipp Wich commented on 28.11.2021 21:03

This error will occur if you upgrade hostapd-common without upgrading *and* restarting the installed wpad flavor as well.

SiNONiMiTY commented on 29.11.2021 14:28

Same issue here, after updating the hostapd-common package, WiFi died on me. Restored the backup I made before updating the packages and WiFi worked again. Second attempt to update the packages, I installed the wpad first before the hostapd and it seems to work but afterwards, I got a lot of disconnection issues on the 5Ghz band. It seems that the latest update (one that ends in 37) breaks things. I suggest stay away from it.

Richard Applegate commented on 08.12.2021 22:06

Hi, I had same issues on Raspberry Pi
infomation system:
Raspberry pi 4B
2GB Ram
2 Access point Netgear Ac2160(one for client, one for AP 5.0Ghz)
1 Built in (one for AP 2.4Ghz)

Openwrt Infomation copy and paste.

Hostname OpenWrt
Model Raspberry Pi 4 Model B Rev 1.4
Architecture ARMv8 Processor rev 3
Firmware Version OpenWrt 21.02.1 r16325-88151b8303 / LuCI openwrt-21.02 branch git-21.327.65561-7f37a58
Kernel Version 5.4.154

after i reset factory the Raspberry pi then upgrade rest but not hostapd-common because it will crash my build in Wifi... I need 2.4 for smart house as well.

Bruno commented on 18.12.2021 21:34

Hi. I've had the same issue with D-Link DIR-2640 A1. After running the following upgrade:

hostapd-common - 2020-06-08-5a8b3662-35 - 2020-06-08-5a8b3662-37

More details:
Model D-Link DIR-2640 A1
Architecture MediaTek MT7621 ver:1 eco:3
Firmware Version OpenWrt 21.02.0 r16279-5cc0535800 / LuCI openwrt-21.02 branch git-21.340.48972-61cc3b1
Kernel Version 5.4.143

equid0x commented on 19.12.2021 11:12

Same issue here. I was able to workaround it with the downloaded package from https://archive.openwrt.org/releases/packages-21.02/arm_cortex-a9/base/

opkg remove hostapd-common –force-depends
opkg install hostapd-common_2020-06-08-5a8b3662-35_arm_cortex-a9.ipk –cache .

Once installed, restart the WiFi interfaces.

Model Linksys WRT1900AC v1
Architecture ARMv7 Processor rev 2 (v7l)
Firmware Version OpenWrt 21.02.1 r16325-88151b8303 / LuCI openwrt-21.02 branch git-21.340.48972-61cc3b1
Kernel Version 5.4.154

Harry Martin commented on 05.01.2022 03:11

Having this with openwrt 21.02.1 running on x86_64. (I believe this is the same issue.)

I get this out-of-the-box, so to speak. I didn't do any upgrade, per se.

KsmoinO commented on 06.01.2022 13:35

Jo-Philipp Wich comment on 28 November 2021 23:03, solves the issue for me except for radius authentication

I set it up following this guide https://openwrt.org/docs/guide-user/network/wifi/freeradius

When I upgrade hostapd-common 2020-06-08-5a8b3662-35 to 2020-06-08-5a8b3662-38, hostapd seems not be able to contact radius:

daemon.notice hostapd: wlan0: RADIUS No response from Accounting server 127.0.0.1:1813 - failover
daemon.notice hostapd: wlan0: RADIUS No response from Authentication server 127.0.0.1:1812 - failover

Downgrading hostapd-common to 2020-06-08-5a8b3662-35 restore radius authentication

Harry Martin commented on 15.01.2022 03:40

I don't understand what Jo-Philipp's comment means in terms of her configuration and what she specifically did to get it to work. I've tried installing just one package at a time to isolate the fault–it turns out, in my case at least, to be the installation of the hostapd-common package. All I know is the following:

I begin with a stock copy of the openwrt 21.02.1 x86_64 image and convert it to a vbox image (this works for all of my other routers, including my old belkin wireless usb adapter, which would still be running but for the unit physically falling apart). I proceed to configure an upstream interface (working perfectly), a management interface (also working perfectly), and then the wireless interface. openwrt detects the adapter and even turns the LED on and I can use the scan and see all of my neighbors' wifi APs. Running "ip link" shows the wlan0 device is present.

Then, I go to add the hostapd-common package, and nothing else yet. After that, even after a cold reboot, I can no longer run the scan. It no longer reports any of my neighbors' APs. The wlan0 device no longer shows in the output of "ip link." Adding a wireless network is pointless (I tried) because it will not work. This leads me to believe there is an issue with hostapd-common (hostapd package is not yet installed). (Again, I was able to get this working for my belkin adapter; sadly, that adapter physically disintegrated.)

It is possible I do not have the right driver. openwrt loads the rtl8812au driver for this NETIS WF2180 usb (no exterior antenna). Other linux users claim it works for them on Ubuntu, so there must be at least some hope for this device running on openwrt.

Addendum: logread no longer sends messages to my syslog server either. It emits one message telling the daemon has started, but no further messages. If it had, I would add the log as an attachment here.

Admin
Jo-Philipp Wich commented on 16.01.2022 15:28

You can't just upgrade hostapd-common alone, you need to upgrade all related packages (wpad etc.)

Harry Martin commented on 17.01.2022 22:52

Starting with the 19.07.8 image, and then proceeding the same as my last post, I am able to get slightly farther. At least I don't seem to lose the wlan0 device entirely. I can install hostapd-common, and even install, say, hostapd and configure it, etc. Now I can run scans repeatedly without the complete loss of the wireless. I can see all of my neighbors' APs both before and after changes to the router (as I make configuration changes).

The problem is I can't seem to get the radio to start. The wireless page in LuCI always shows "Device is not active" – even though I can successfully scan. Restart does nothing to change that state.

So downgrading appears to allow scanning to work persistently, although after some time, I find I need to cold start the router as reboots no longer restore the running state of the VM to where it was when I could still run scans. Hopefully this update post might give someone here an idea for me to try. Meanwhile, I continue my rubber duck debugging as best as I can. (I'm also working on building a custom image so I can eventually do some debugging.)

EDIT: I also note that logread still is unable to send on the management interface to my syslog server, even with 19.07.8. logread worked successfully up until I added the wireless AP software. I am also logging to a local file on the router, and I can see it is failing to send to port 514. I cannot even ping from that interface to the syslog server, whereas it worked prior to the install of AP packages. The syslog server continues getting UDP from my other openwrt router.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing