You are not logged in.
wpa_supplicant 2.12 started including `CONFIG_NAN_USD=y` where 2.11 did not. Since upgrading to 2.12 I have an issue where after approximately 5 minutes packets are lost and the state is never recovered leading to a 50% speed drop on WiFi until the stack is reset. Through testing I have narrowed this down to `CONFIG_NAN_USD` but have not bisected the code to determine exactly where this is occurring. I am hoping someone more familiar with the code would know or at least reduce the amount of work I'd need to do to find out as I'm disabled and this kind of thing takes me a very long time.
I've been waiting for account approval on gitlab to be able to report this directly to the package maintainer but think it's important it is addressed sooner rather than later. Also please excuse the use of AI to generate this summary - I have only done so due to accessibility requirements.
On a Dell XPS 9575 laptop using a Qualcomm Atheros QCA6174 Wi-Fi adapter (`ath10k_pci`), Wi-Fi performance can degrade after a short period after the connection is established. The degradation can persist until the wireless interface is reset by toggling the laptop's wireless hardware switch, but inevitably reoccurs again after several minutes.
The problem is reproducible with the distribution's `wpa_supplicant` 2.12 package and does not occur in the same persistent form with version 2.11.
Testing custom builds of hostap/wpa_supplicant 2.12 has isolated `CONFIG_NAN_USD=y` as a sufficient trigger for the problem in the tested build configuration. Disabling this option avoids the failure under otherwise matching build settings.
I have not yet identified the exact source-code change or mechanism responsible.
- Laptop: Dell XPS 9575 2-in-1
- Wireless adapter: Qualcomm Atheros QCA6174, PCI ID `168c:003e`, revision 32
- Subsystem: Rivet Networks / Killer 1435, ID `1a56:143a`
- Kernel driver: `ath10k_pci`
- Interface: `wlp2s0`
- Distribution: Manjaro Linux Testing (Also confirmed on Archlinux)
- Kernel versions tested: 6.18, 6.19 and 7.3; the issue was not resolved by changing kernels
- Affected supplicant package: `wpa_supplicant` 2:2.12-1
- Comparison working package: `wpa_supplicant` 2:2.11-3
- Network management: NetworkManager, using the D-Bus/systemd-managed wpa_supplicant service
The wireless network is 5 GHz, using an 80 MHz channel. Signal strength during testing was approximately -48 dBm.
After the Wi-Fi connection has been established in approximately two minutes network performance always deteriorates. Downloads and external speed tests show substantially reduced throughput related to packet loss that persists rather than recovering normally.
Toggling the laptop's wireless hardware switch off and then back on restores normal performance. As does issuing `nmcli connection up "wifi_name"`.
The failure is not limited to one kernel version. Downgrading NetworkManager alone did not resolve it.
The `ath10k` firmware crash counter remained at zero during the investigation.
The issue is reproducible with the distribution's wpa_supplicant 2.12 package and was not observed in the same persistent form with version 2.11.
To isolate the cause, I built hostap/wpa_supplicant 2.12 from source and tested different compile-time configurations. The tests used the same test setup and otherwise matching configuration settings, with the relevant option changed between builds.
The following results were observed:
Build configuration
1. Minimal test configuration with the additional features disabled = No persistent degradation observed
2. `CONFIG_NAN_USD=y`, with `CONFIG_PASN=y` and `CONFIG_PR=y` retained = Original degradation reproduced
3. `CONFIG_NAN_USD` disabled again, with the other settings unchanged = No persistent degradation observed
The `CONFIG_NAN_USD=y` build had SHA-256:
`d9238ce22c43cb4752fbbef0e731048c8e6b584121014874a2f2cc7e11a05d03`
The otherwise matching build with `CONFIG_NAN_USD` disabled had SHA-256:
`2004011ae88a7a77c6b470e8a596fd7fa871540db9095bce6533735734b35acb`
Additional tests individually enabling `CONFIG_SAE_PK`, `CONFIG_DPP3`, `CONFIG_HE_OVERRIDES`, `CONFIG_IEEE80211AX` and `CONFIG_IEEE80211BE` did not reproduce the persistent degradation when `CONFIG_NAN_USD` was disabled in the tested configurations.
The tests do not establish whether the problem is in NAN USD code itself, a shared code path affected by this build option, or an interaction with the driver.
Could the maintainers investigate why enabling `CONFIG_NAN_USD` in wpa_supplicant 2.12 appears to trigger this Wi-Fi performance regression with the QCA6174 / ath10k driver?
I can provide the custom build configurations, source revisions, test binaries' hashes, and further diagnostic output if useful.
I have not yet completed a source-level bisect of the changes related to NAN USD between hostap 2.11 and 2.12.
Offline
On archlinux the last 2.11 version of hostapd was 2.11-4 while wpa_supplicant was 2:2.11-6 .
Have you tested with those exact versions on an archlinux installation ?
Please post logs of your tests on an uptodate archlinux installation.
Moderator Note
Moving to Networking, Server, and Protection
Last edited by Lone_Wolf (2026-10-25 11:38:07)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
> On archlinux the last 2.11 version of hostapd was 2.11-4 while wpa_supplicant was 2:2.11-6 .
> Have you tested with those exact versions on an archlinux installation ?
No, I tested with wpa_supplicant 2.11-3 because that was my last known working version and I had that version cached, and and 2.12-1 because that is the version I had currently installed when I determined the problem was with wpa_supplicant. Additionally, no 2.11 version included CONFIG_NAN or CONFIG_NAN_USD in the build configuration so testing 2.11-6 is likely a waste of time. It's taken me weeks to get this far because of accessibility reasons but wanted to report the issue as early as possible.
I'll keep working to pinpoint the exact change but it will likely take me months without help.
Last edited by smash (Today 10:18:24)
Offline
Similar issue caused by different config changes in 2.12 reported here: https://bbs.archlinux.org/viewtopic.php?pid=2310979
Offline
I'll keep working to pinpoint the exact change but it will likely take me months without help.
Why would it take months? Can you not git bisect the issue? You have not provided any details on what would speed the process up that others could provide.
Offline
smash wrote:I'll keep working to pinpoint the exact change but it will likely take me months without help.
Why would it take months? Can you not git bisect the issue? You have not provided any details on what would speed the process up that others could provide.
I'm significantly disabled with extensive accessibility requirements and have limited access to spare hardware (I only have the 1 laptop and no means to buy another machine) so while I'm happy to test where I can someone (anyone) with a better understanding of the codebase and Arch packaging would hopefully be able to give me more specific instruction on exactly what to test and how because for me to work that out or test by trial and error is extremely difficult and takes a very long time.
Offline
Does wpa_supplicant 2.11 with Arch's current config also produce the issue? If so is the reverse also true wpa_supplicant 2.12 with Arch's 2.11 config does not reproduce the issue. I used to report issues to gitlab that forum users suffered but I have had too much of my time and good will wasted by https://gitlab.archlinux.org/archlinux/ … ote_591686 so I will no longer do it.
Offline
Importantly, does this also happen w/ only wpa_supplicant and w/o networkmanager?
Do you have a journal covering the package losses?
Are there related warning or status reports?
Ftr, Manjaro isn't supported here but I intend to ignore that for now.
@loqs, don't allow that to touch you.
I get that this is frustrating but so are many things atm and basically all pre-coordinated efforts are wasted until they're not (and a 4k+ LOC patch is kinda insane anyway)
You could adopt a fire-and-forget approach to things that are not your immediate responsibility and only invest considerable resources on explicit feedback.
And don't forget to https://www.youtube.com/watch?v=uAzwji5Cfmk
Offline
@seth that is why I no longer do upstream work for Arch or any work work on that core developers projects and require an explicit Arch maintainer response to any bug report before authoring a fix. If core developers can class working with upstream as out of scope it would be hypocritical for the project to expect it to fall under my scope.
Offline
Hmm… I couldn't actually find any comment from Maxime (dotnet maintainer) in that entire saga.
I can't speak to the relation and whether Pierre is in any position to approve dotnet patches but understood him to claim only that (ie. dotnet specifically) out of *his* scope, not upstream cooperation in general (let alone for other PMs)?
Whatever the resolution for anyone involved, I'd ask you to do me a favor and watch 6 black and white movies of your choice (nothing produced after 1960, ideally stuff before 1950) of the next month (forcing yourself to have make that choices and time) and around Christmas check just with yourself whether you're still feeling frustrated or angry.
Offline
I think we can agree wither way that my attempting to help Arch with upstream is not beneficial to either me or Arch same with me creating patches before maintainers have responded they want them. I did check on Pierre interacting with all upstream projects for the OpenSSL 4 upgrade only trace was in one response to an upstream issue I opened. Pierre would not take over my opened issues or open merge requests so they were all closed. I do not see how it is possible to coordinate with anyone who manages to loose all traces of my work due to being overloaded rendering all my efforts futile. There is no point in me going through the process of getting an openssl patch merged upstream if the openssl maintainer then picks a Debian patch instead.
Last edited by loqs (Today 20:23:56)
Offline