WIFI Issue with Update 199

Networking
1

Hi,

Since update 199, I haven’t been able to access the AP. I have just run a software update on my APU board with a Compex WLE600VX 802.11ac Wireless LAN Mini-PCIe Card featuring a Qualcomm Atheros QCA9882, which I bought in 2018. It has been working fine for years.

My clients try to connect, but they don’t receive an IP address. I’ve tried different wireless modes, but the AP is only visible in 802.11an, and I can’t start the AP if I choose 802.11ac.

14:21:01 hostapd: blue0: EAPOL-4WAY-HS-COMPLETED ac:5a:fc:ad:e9:45
14:21:01 hostapd: blue0: AP-STA-CONNECTED ac:5a:fc:ad:e9:45
14:20:54 hostapd: blue0: AP-ENABLED
14:20:54 hostapd: blue0: interface state ACS->ENABLED
14:20:53 hostapd: blue0: ACS-COMPLETED freq=5825 channel=165
14:20:33 hostapd: blue0: ACS-STARTED
14:20:33 hostapd: blue0: interface state COUNTRY_UPDATE->ACS
14:20:33 hostapd: ACS: Automatic channel selection started, this may take a bit
14:20:33 hostapd: blue0: interface state UNINITIALIZED->COUNTRY_UPDATE
14:20:33 kernel: ath10k_pci 0000:04:00.0: pdev param 0 not supported by firmware
14:20:30 kernel: ath10k_pci 0000:04:00.0: DFS region 0x0 not supported, will trigger radar for every pulse
14:20:30 hostapd: nl80211: deinit ifname=blue0 disabled_11b_rates=0
14:20:30 hostapd: blue0: CTRL-EVENT-TERMINATING
14:20:30 hostapd: blue0: AP-DISABLED
14:20:30 hostapd: blue0: interface state ENABLED->DISABLED
14:16:23 hostapd: blue0: AP-ENABLED
14:16:23 hostapd: blue0: interface state ACS->ENABLED
14:16:23 hostapd: blue0: ACS-COMPLETED freq=5845 channel=169
14:16:03 hostapd: blue0: ACS-STARTED
14:16:03 hostapd: blue0: interface state COUNTRY_UPDATE->ACS
14:16:03 hostapd: ACS: Automatic channel selection started, this may take a bit
14:16:03 hostapd: blue0: interface state UNINITIALIZED->COUNTRY_UPDATE
14:16:03 kernel: ath10k_pci 0000:04:00.0: pdev param 0 not supported by firmware
14:12:49 hostapd: hostapd_free_hapd_data: Interface blue0 wasn’t started
14:12:49 hostapd: blue0: CTRL-EVENT-TERMINATING
14:12:49 hostapd: blue0: AP-DISABLED
14:12:49 hostapd: blue0: interface state DISABLED->DISABLED
14:12:49 hostapd: blue0: interface state DISABLED->DISABLED
14:12:48 hostapd: nl80211: deinit ifname=blue0 disabled_11b_rates=0
14:12:48 hostapd: hostapd_free_hapd_data: Interface blue0 wasn’t started
14:12:48 hostapd: blue0: AP-DISABLED
14:12:48 hostapd: ACS: Failed to start
14:12:48 hostapd: ACS: Possibly channel configuration is invalid, please report this along with your config file.
14:12:48 hostapd: blue0: AP-DISABLED
14:12:48 hostapd: blue0: interface state DFS->DISABLED
14:12:48 hostapd: Interface initialization failed
14:12:48 hostapd: DFS start_dfs_cac() failed, -1
14:12:48 hostapd: Can’t set freq params
14:12:48 hostapd: 80/80+80 MHz: no second channel offset
14:12:48 hostapd: blue0: DFS-CAC-START freq=5700 chan=140 sec_chan=0, width=1, seg0=138, seg1=0, cac_time=60s
14:12:48 hostapd: blue0: interface state ACS->DFS
14:12:48 hostapd: blue0: ACS-COMPLETED freq=5700 channel=140
14:12:28 hostapd: blue0: ACS-STARTED
14:12:28 hostapd: blue0: interface state COUNTRY_UPDATE->ACS
14:12:28 hostapd: ACS: Automatic channel selection started, this may take a bit
14:12:28 hostapd: blue0: interface state UNINITIALIZED->COUNTRY_UPDATE
14:12:28 kernel: ath10k_pci 0000:04:00.0: pdev param 0 not supported by firmware
14:12:25 kernel: ath10k_pci 0000:04:00.0: DFS region 0x0 not supported, will trigger radar for every pulse
14:12:25 kernel: ath10k_pci 0000:04:00.0: could not get mac80211 beacon
14:12:25 hostapd: nl80211: deinit ifname=blue0 disabled_11b_rates=0
14:12:25 hostapd: blue0: CTRL-EVENT-TERMINATING
14:12:25 hostapd: blue0: AP-DISABLED
14:12:25 hostapd: blue0: AP-STA-DISCONNECTED ac:5a:fc:ad:e9:45
14:12:25 hostapd: blue0: interface state ENABLED->DISABLED
14:10:22 hostapd: blue0: EAPOL-4WAY-HS-COMPLETED ac:5a:fc:ad:e9:45
14:10:22 hostapd: blue0: AP-STA-CONNECTED ac:5a:fc:ad:e9:45

I have deleted the password in the posted picture:

WIFI AP
WIFI AP803×912 102 KB

Is this a known problem? I can’t figure out how to get the system running again.

Thanks.

Claus

2

Small hint…

Change your country code from DE to any other UE country, save, try again to connect. and see if the words UNINITIALIZED->COUNTRY_UPDATE disappear from your logs.

3

I’ve changed it to “BE” but this doesn’t help:

17:45:21 hostapd: blue0: interface state UNINITIALIZED->COUNTRY_UPDATE

4

There was a bug in the hostapd changes. The root cause is being investigated and a solution will be identified.

Unfortunately no users that use hostapd did any evaluation during the Testing phase of CU199 so the problem was only identified when CU199 had full release.

3 Likes
5

@bonnietwin Thank you for the update. I’ve just updated to the latest version (hostapd-f747ae0-70). Unfortunately, this has made things worse, as my log is now flooded. I’ve added a short excerpt. This repeats every few minutes.
I had to stop the service.

19:19:49 kernel: ath10k_pci 0000:04:00.0: DFS region 0x0 not supported, will trigger radar for every pulse
19:19:49 hostapd: hostapd_cleanup_iface: free iface=0x3f277880
19:19:49 hostapd: hostapd_cleanup_iface_partial(0x3f277880)
19:19:49 hostapd: hostapd_cleanup_iface(0x3f277880)
19:19:49 hostapd: hostapd_interface_free: free hapd 0x3f27c610
19:19:49 hostapd: hostapd_interface_free(0x3f277880)
19:19:49 hostapd: nl80211: Unsubscribe mgmt frames handle 0x88888888b7af3c59 (AP teardown)
19:19:49 hostapd: nl80211: Teardown AP(blue0) - device_ap_sme=0
19:19:49 hostapd: nl80211: Set mode ifindex 5 iftype 2 (STATION)
19:19:49 hostapd: netlink: Operstate: ifindex=5 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
19:19:49 hostapd: nl80211: Remove beacon (ifindex=5)
19:19:49 hostapd: nl80211: deinit ifname=blue0 disabled_11b_rates=0
19:19:49 hostapd: hostapd_interface_deinit_free: driver=0x571840 drv_priv=0x3f281810 → hapd_deinit
19:19:49 hostapd: hostapd_free_hapd_data(blue0)
19:19:49 hostapd: blue0: CTRL-EVENT-TERMINATING
19:19:49 hostapd: hostapd_cleanup(hapd=0x3f27c610 (blue0))
19:19:49 hostapd: blue0: AP-DISABLED
19:19:49 hostapd: nl80211: Frame TX command accepted; cookie 0x1f
19:19:49 hostapd: CMD_FRAME - hexdump(len=26): c0 00 00 00 ff ff ff ff ff ff 04 f0 21 41 90 07 04 f0 21 41 90 07 00 00 03 00
19:19:49 hostapd: nl80211: CMD_FRAME freq=5640 wait=0 no_cck=0 no_ack=0 offchanok=0
19:19:49 hostapd: nl80211: send_mlme → send_frame_cmd
19:19:49 hostapd: nl80211: send_mlme - Use bss->freq=5640
19:19:49 hostapd: nl80211: send_mlme - da=ff:ff:ff:ff:ff:ff sa=04:f0:21:41:90:07 bssid=04:f0:21:41:90:07 noack=0 freq=0 no_cck=0 offchanok=0 wait_time=0 no_encrypt=0 fc=0xc0 (WLAN_FC_STYPE_DEAUTH) nlmode=3
19:19:49 hostapd: blue0: Deauthenticate all stations
19:19:49 hostapd: ap_free_sta: cancel ap_handle_timer for ac:5a:fc:ad:e9:45
19:19:49 hostapd: nl80211: multicast to unicast enabled on interface blue0
19:19:49 hostapd: nl80211: sae_pwe=0
19:19:49 hostapd: * channel_type=1
19:19:49 hostapd: * sec_channel_offset=0
19:19:49 hostapd: * radar_background=0
19:19:49 hostapd: * ht_enabled=1
19:19:49 hostapd: * vht_enabled=0
19:19:49 hostapd: * he_enabled=0
19:19:49 hostapd: * eht_enabled=0
19:19:49 hostapd: * freq=5640
19:19:49 hostapd: nl80211: assocresp_ies - hexdump(len=15): 7f 08 04 00 00 88 00 00 01 40 f4 03 02 00 20
19:19:49 hostapd: nl80211: proberesp_ies - hexdump(len=36): 45 11 02 ea 07 01 0a 11 18 16 00 00 00 00 00 00 00 00 00 7f 08 04 00 00 88 00 00 01 40 6b 01 10 6c 02 7f 00
19:19:49 hostapd: nl80211: beacon_ies - hexdump(len=36): 45 11 02 ea 07 01 0a 11 18 16 00 00 00 00 00 00 00 00 00 7f 08 04 00 00 88 00 00 01 40 6b 01 10 6c 02 7f 00
19:19:49 hostapd: nl80211: group_cipher=0x10
19:19:49 hostapd: nl80211: pairwise_ciphers=0x10
19:19:49 hostapd: nl80211: Not enough room for all AKM suites (num_suites=3 > 2)
19:19:49 hostapd: nl80211: key_mgmt_suites=0x502
19:19:49 hostapd: nl80211: wpa_version=0x2
19:19:49 hostapd: nl80211: auth_algs=0x1
19:19:49 hostapd: nl80211: privacy=2
19:19:49 hostapd: nl80211: hidden SSID not in use
19:19:49 hostapd: * dtim_period=2
19:19:49 hostapd: * beacon_int=100
19:19:49 hostapd: nl80211: ssid=WB_OL
19:19:49 hostapd: nl80211: dtim_period=2
19:19:49 hostapd: nl80211: rate_type=0
19:19:49 hostapd: nl80211: beacon_rate=0
19:19:49 hostapd: nl80211: beacon_int=100
19:19:49 hostapd: nl80211: ifindex=5
19:19:49 hostapd: nl80211: Beacon tail - hexdump(len=176): 07 12 44 45 49 24 04 17 34 04 14 64 0b 1a 90 01 00 95 07 0d 20 01 03 30 1c 01 00 00 0f ac 04 01 00 00 0f ac 04 03 00 00 0f ac 02 00 0f ac 06 00 0f ac 08 0c 00 3b 02 79 00 2d 1a ef 09 1b ff ff 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 3d 16 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7f 08 04 00 00 88 00 00 01 40 45 11 02 ea 07 01 0a 11 18 16 00 00 00 00 00 00 00 00 00 6b 01 10 6c 02 7f 00 f4 03 02 00 20 dd 18 00 50 f2 02 01 01 01 00 03 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00
19:19:49 hostapd: nl80211: Beacon head - hexdump(len=53): 80 00 00 00 ff ff ff ff ff ff 04 f0 21 41 90 07 04 f0 21 41 90 07 00 00 00 00 00 00 00 00 00 00 64 00 11 01 00 05 57 42 5f 4f 4c 01 08 8c 12 98 24 b0 48 60 6c
19:19:49 hostapd: nl80211: Set beacon (beacon_set=1)
19:19:49 hostapd: hostapd_ht_operation_update new operation mode=0x0 changes=1
19:19:49 hostapd: hostapd_ht_operation_update current operation mode=0x4
19:19:49 hostapd: nl80211: Set STA flags - ifname=blue0 addr=ac:5a:fc:ad:e9:45 total_flags=0x62 flags_or=0x2 flags_and=0xfffffff2 authorized=0
19:19:49 hostapd: blue0: AP-STA-DISCONNECTED ac:5a:fc:ad:e9:45
19:19:49 hostapd: Removing station ac:5a:fc:ad:e9:45
19:19:49 hostapd: hostapd_bss_deinit: deinit bss blue0
19:19:49 hostapd: blue0: interface state ENABLED->DISABLED
19:19:49 hostapd: hostapd_interface_deinit(0x3f277880)
19:19:49 hostapd: hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1
19:19:49 hostapd: hostapd_interface_deinit_free(0x3f277880)
19:19:49 hostapd: Signal 15 received - terminating
19:17:55 hostapd: STA 76:d4:df:f3:54:20 sent probe request for broadcast SSID
19:17:55 hostapd: nl80211: Frame TX command accepted (no ACK); cookie 0x0
19:17:55 hostapd: CMD_FRAME - hexdump(len=229): 50 00 00 00 76 d4 df f3 54 20 04 f0 21 41 90 07 04 f0 21 41 90 07 00 00 00 00 00 00 00 00 00 00 64 00 11 01 00 05 57 42 5f 4f 4c 01 08 8c 12 98 24 b0 48 60 6c 07 12 44 45 49 24 04 17 34 04 14 64 0b 1a 90 01 00 95 07 0d 20 01 03 30 1c 01 00 00 0f ac 04 01 00 00 0f ac 04 03 00 00 0f ac 02 00 0f ac 06 00 0f ac 08 0c 00 3b 02 79 00 2d 1a ef 09 1b ff ff 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 3d 16 80 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7f 08 04 00 00 88 00 00 01 40 45 11 02 ea 07 01 0a 11 18 16 00 00 00 00 00 00 00 00 00 6b 01 10 6c 02 7f 00 f4 03 02 00 20 dd 18 00 50 f2 02 01 01 01 00 03 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00
6

I installed CU 199 on my Raspberry Pi 4 and tested hostapd; I was able to connect without any problems.

Capture d'écran 2026-01-10 195450
Capture d'écran 2026-01-10 1954501508×1070 67.7 KB

7

I don’t really understand your comment here. Version f747ae0-70 was the version that came with CU199. It was added into CU199 back in September 22nd 2025. There has been no other version since then.

The cause for this issue is not yet identified. It is still being investigated and therefore no fix has yet been identified.

1 Like
8

Interesting, so the problem is not a completely systemic issue affecting all users.

Unfortunately that means that we will need to identify what the setup conditions need to be to trigger the problem so we can investigate it.

9

I’m totally confused now! Pakfire showed the update today, so I installed it on top of version …-68, which had been running on my system until now. I had the impression that this would be a quick fix. I cannot remember how the CU199 installation went. I only remember three packages for my system. The main product, hostapd and tor.

10

Maybe I have misunderstood what you were saying.

In your first post you said that you had the hostapd problem since updating to CU199. That update would have installed hostapd-f747ae0-70

Then after doing that CU199 update my understanding is that in post 5 of this thread you indicated that you had updated hostapd to the latest version hostapd-f747ae0-70 but that is the same version as was installed with CU199.

Have I misunderstood your description of the sequence of things.

A fix can only be quickly implemented once the reason for the problem has been identified. That has not yet been achieved.
Also in post 6 @pscar13 has mentioned that the update worked fully on the RPi4.

Maybe there is some issue in the hostapd package update that is working differently for x86_64 versus aarch64.

1 Like
11

Thank you for the information. I will wait for the fix. For now, I’m using my old Fritz!Box Wi-Fi. This is not perfect, but it’s a workaround.

12

You can also restore the backup made before the CU199 upgrade and then reinstall CU198 using that backup.

13

Did you report a bug on Bugzilla? What is there to be fixed?

You AP seems to be running fine and has been successfully started:

You even have a client that has connected to it:

So either the client has not been asking for an IP address or the DHCP server has crashed? I doesn’t seem to be hostapd.

14

The hostapd page of the opening post shows the WUI from CU198/the associated hostapd.
Means CU and hostapd don’t match. This shows the change of behaviour ( including the log flooding ) after install of hostapd-f747ae0-70.

15

Michael Tremer Did you report a bug on Bugzilla? What is there to be fixed?

You AP seems to be running fine and has been successfully started:

I’m referering to @bonnietwin’s comment about the known bug in hostapd.

Michael Tremer So either the client has not been asking for an IP address or the DHCP server has crashed? I doesn’t seem to be hostapd.

The LAN-connected clients receive DHCP addresses. I’ve tried with different clients (iOS, Windows and Linux) via the WiFi port, but they abort because they don’t receive an requested IP address. As mentioned above, the AP is only visible when I select 802.11an; I cannot start the AP if I select 802.11ac. In my opinion, this is at least partly due to hostapd. There are other reports of excessive log files as well; this also happens with my configuration.

16

My comment was meaning someone else had already mentioned about excessive logs.
If what you were experiencing was not excessive logs then i missed that.
Unfortunately there were 3 or 4 different posts about problems with hostapd and maybe i added my note incorrectly on some of them.

17

Obviously, my first upgrade to CU199 didn’t go perfectly. I could see the different packages in Packfire, and it seemed as though they had been installed. However, several hours later, the hostapd update ‘hostapd-f747ae0-70’ appeared (again?), and I installed it. It exhibits the same poor performance with regard to client access and the log flodding started.

WIFI AP 2
WIFI AP 2908×899 121 KB

1 Like
18

@bonnietwin In addition to the logging problem, I cannot access the AP at all, as mentioned in my initial post. The LAN (green) works perfectly, but the WiFi (blue) doesn’t. I haven’t reported this on Bugzilla yet.

19

I’ve had the same problem since updating to version 199; my access point is no longer functional. Same motherboard, same Wi-Fi model (WLE600VX).

1 Like
20

Hallo, IPFire Team,

Have installed today updates:
IPFire 2.29 (x86_64) - Core-Update 199
hostapd-f747ae0-70

Systeminformation:
IPFire-Version IPFire 2.29 (x86_64) - core199
Pakfire-Version 2.29-x86_64
Kernelversion Linux c78r.almoa 6.12.58-ipfire #1 SMP PREEMPT_DYNAMIC Sat Jan 10 19:05:51 GMT 2026 x86_64 GNU/Linux

My clients can’t connect to AP.

The LAN (green) works perfectly.

I’m using:
APU.2C4 system board
WLAN-modul is Compex WLE200NX (802.11 abgn, 2x2 MIMO)

Thanks for help.

1 Like