So I have a weird issue that I get disconnect from fedora cockpit and samba share after the initial login. This issue only happens after I upgraded to fedora 43. I check my logs and its seems like wpa_supplicant is having an error?
Symptom:
Fedora Cockpit (Workstation)
After initial login, Once I navigate to other views. I get disconnect from cockpit
Samba share
After downloading or uploading one file. I get disconnect from the server
Log error message:
This happens after I login to fedora cockpit or access a file in my samba drive
Nov 16 11:15:58 fedora wpa_supplicant[1621]: nl80211: kernel reports: key addition failed
Nov 16 11:15:58 fedora wpa_supplicant[1621]: TDLS: Failed to set TPK to the driver
Software info
OS: Fedora Linux 43 (Workstation Edition)
Kernel: Linux 6.17.7-300.fc43.x86_64
cockpit.x86_64 351-1.fc43
samba.x86_64 2:4.23.3-1.fc43
wpa_supplicant.x86_64 1:2.11-7.fc43
NetworkManager: 1.54.0-2.fc43
Fix that I deployed
Turn off power save for wifi using network manager (Does not fix the issue)
Update cockpit (I think that fixes it a while ago but randomly today it got broken again)
I had never heard of TDLS but was curious, so googled it. AI jumped in and said the following, which I find interesting:
TDLS: This feature allows two devices on the same Wi-Fi network to exchange data directly, bypassing the router. This is often used to speed up local network transfers for applications like KDE Connect, Chromecast, or local file sharing.
• TDLS: Failed to set TPK to the driver: The “TPK” (TDLS Peer Key) is the encryption key for this direct link. Your system failed to set this key in your Wi-Fi driver.
• nl80211: kernel reports: key addition failed: This is the kernel (the core of the OS) confirming the failure. The nl80211 layer, which is how wpa_supplicant talks to the kernel, reports that it couldn’t add the security key as requested.
This error is often just “noise” if you don’t use direct-link features and your Wi-Fi is otherwise working. However, it can sometimes cause network instability or freezes, especially when triggered by apps like KDE Connect.
———————
Try a wired ethernet connection and see if that fixes the issue
Confirm you have a router in that network and not only ad-hoc wifi