SUMMARY *** Can not connect any device to WAP/WAP2/WAP3 shared network created through plasma-nm *** STEPS TO REPRODUCE 1. Create a shared wifi network with any of the above security protocol 2. Try to connect another device by entering the password for above network, or scanning the QR code OBSERVED RESULT Device cannot connect to the network and displays error for incorrect password EXPECTED RESULT Plasma-nm should create a shared wifi network such that other devices can connect to it SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.16 (available in About System) KDE Plasma Version: 5.23 KDE Frameworks Version: 5.90 Qt Version: 5.15 ADDITIONAL INFORMATION Shared wifi network created through other means (like linux-wifi-hotspot utility) can be connected by other devices. Bug has been present for as long as I can remember
What distribution does this happen on for you? I have a feeling this bug depends heavily on non-KDE components. Also to be clear, unencrypted hotspot works, right?
(In reply to Alois Wohlschlager from comment #1) > What distribution does this happen on for you? I have a feeling this bug At present, I can confirm it on manjaro and kde neon installed on seperate hardware. I have also had this issue in ubuntu but that was many years before. > depends heavily on non-KDE components. Also to be clear, unencrypted hotspot > works, right? Yes, unencrypted hotspot works. Also encrypted hotspots created through utilities like linux-wifi-hotspot also work
I think this is wpa_supplicant somehow failing to create a WPA3 hotspot properly. To confirm, can you please try the following (adjust <interface> and <passphrase> appropriately): $ cat > hostapd.conf <<EOF interface=<interface> ssid=hotspot wpa=2 wpa_key_mgmt=SAE wpa_passphrase=<passphrase> EOF $ sudo hostapd hostapd.conf Then try to connect to the hotspot using a different device after the AP-ENABLED message appears. Then, please report whether hostapd prints anything else.
I got this error: ACS: Automatic channel selection started, this may take a bit wlp0s29u1u5: interface state UNINITIALIZED->ACS wlp0s29u1u5: ACS-STARTED ACS: Unable to collect survey data ACS: All study options have failed Interface initialization failed wlp0s29u1u5: interface state ACS->DISABLED wlp0s29u1u5: AP-DISABLED ACS: Possibly channel configuration is invalid, please report this along with your config file. ACS: Failed to start wlp0s29u1u5: AP-DISABLED hostapd_free_hapd_data: Interface wlp0s29u1u5 wasn't started nl80211: deinit ifname=wlp0s29u1u5 disabled_11b_rates=0 wlp0s29u1u5: interface state DISABLED->DISABLED wlp0s29u1u5: interface state DISABLED->DISABLED wlp0s29u1u5: AP-DISABLED wlp0s29u1u5: CTRL-EVENT-TERMINATING hostapd_free_hapd_data: Interface wlp0s29u1u5 wasn't started
This is likely unrelated, try running on a fixed channel by adding a line "channel=1" (without quotes) to the hostapd.conf.
(In reply to Alois Wohlschlager from comment #5) > This is likely unrelated, try running on a fixed channel by adding a line > "channel=1" (without quotes) to the hostapd.conf. It worked after putting channel=1. However, the hotspot so created still can't be connected by any device and shows incorrect password (the same error as with plasma-nm)
Anything I should report further? Still have the error in 5.27
My adapter broke, and I cannot reproduce the bug with the new device any more. Since we already figured out the bug is likely not in Plasma, I'd try the hostap mailing list. The problem appears to be that some device/driver/wpa_supplicant combinations fail to set up a WPA3 access point properly.
(In reply to Alois Wohlschlager from comment #8) > My adapter broke, and I cannot reproduce the bug with the new device any > more. Since we already figured out the bug is likely not in Plasma, I'd try > the hostap mailing list. The problem appears to be that some > device/driver/wpa_supplicant combinations fail to set up a WPA3 access point > properly. Thanks a lot. I tried to mail hostap but it keeps blocking my mail for some reason and I couldn't figure out where I should report them the bug. Also, I have issue with both WPA2 and WPA3 encryption.
> Thanks a lot. I tried to mail hostap but it keeps blocking my mail for some > reason and I couldn't figure out where I should report them the bug. I have no experience with this list in particular, but it is likely that the first message sent from a new email address needs moderator approval (this is a common process to prevent spam). > Also, I have issue with both WPA2 and WPA3 encryption. You actually don't. When you tell NetworkManager to create a WPA2 access point, it actually creates a hybrid WPA2/WPA3 access point. Your other device prefers to connect to WPA3 and subsequently fails.
For what it's worth, I found a workaround for my connection from a comment on Red Hat Bugzilla bug 2057352. I had to use the interactive mode of nmcli to set the Protected Management Frames (802.11w) off: $ nmcli connection edit My_Hotspot > set wifi-sec.pmf 1 > save > quit 0 means "global default", 1 means "disable", etc. The command lspci shows my adapter as "Intel Corporation Wireless 8265 / 8275 (rev 78)".
(In reply to Simo Sutela from comment #11) > For what it's worth, I found a workaround for my connection from a comment > on Red Hat Bugzilla bug 2057352. I had to use the interactive mode of nmcli > to set the Protected Management Frames (802.11w) off: > > $ nmcli connection edit My_Hotspot > > set wifi-sec.pmf 1 > > save > > quit > > 0 means "global default", 1 means "disable", etc. The command lspci shows my > adapter as "Intel Corporation Wireless 8265 / 8275 (rev 78)". I tried it too but it did not solve the issue in my case