Bug 419745

Summary: WiFi hotspot with WPA/WPA2 Personal security doesn't work with Windows 10 client
Product: [Applications] systemsettings Reporter: Horst Schirmeier <horst>
Component: kcm_networkmanagementAssignee: Jan Grulich <jgrulich>
Status: REPORTED ---    
Severity: normal CC: jakieschneider13, jgrulich, plasma-bugs
Priority: NOR    
Version: 5.18.4   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Horst Schirmeier 2020-04-06 17:58:48 UTC
When I create a shared WiFi ("hotspot") in the "Connections - System Settings Module" with enabled WPA/WPA2 security, I cannot get Windows 10 clients to connect.  Android 10 connects to this shared WiFi without problems.  Using the "Hotspot" button behind the system-tray network icon works with Windows 10 clients (but creates an open/unencrypted WiFi).

STEPS TO REPRODUCE
1. Go to System Settings -> Network / Connections
2. Add a new network ("+"), Connection Type: "Wi-Fi (shared)"
3. Pick an appropriate connection and SSID name (e.g. "xyz", "xyz").
4. "Security" tab: Security "WPA/WPA2 Personal", pick a password. Save.
5. "Connect" to this newly created network, enabling the Wi-Fi access point.
6. Try to connect to this AP with a Windows 10 client.

OBSERVED RESULT
1. When clicking on the "xyz" Wi-Fi, Windows 10 (EDU, Version 1909, Build 18363.418) asks for an eight-digit PIN instead of a password, unlike for other WiFis. It is, however, also possible to click a link below and enter the previously set AP password.
2. Windows 10's Wi-Fi dialog reports that it cannot connect to this network ("Keine Verbindung mit diesem Netzwerk möglich").  This is reproducible with different Windows 10 machines.
3. A Sony Xperia XZ2 Compact with Android 10 connects to the "xyz" AP without problems.

EXPECTED RESULT
Windows 10 should connect to the AP without problems, just like Android 10 does, or just as Windows 10 does to the unencrypted AP.

SOFTWARE/OS VERSIONS
Windows: Windows 10 Education, 1909, Build 18363.418
macOS: 
Linux: Kubuntu 20.04
KDE Plasma Version: 5.18.4 (4:5.18.4.1-0ubuntu1)
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.5
Comment 1 Jan Grulich 2020-04-06 19:26:00 UTC
What is the mode set to in the "Wi-Fi" tab when configuring the connection? Do you use Access Point or Adhoc? Can you change it to the other one, like to Access Point when using Adhoc and vice versa and try if it makes a difference?
Comment 2 Horst Schirmeier 2020-04-07 06:36:43 UTC
(In reply to Jan Grulich from comment #1)
> What is the mode set to in the "Wi-Fi" tab when configuring the connection?
> Do you use Access Point or Adhoc?

Access Point.

> Can you change it to the other one, like to Access Point when using Adhoc and
> vice versa and try if it makes a difference?

After switching to Adhoc, the "WLAN Hotspot" connection doesn't come up at all; it remains in the "Configuring Interface" state and times out after a few seconds.  I don't get to the stage where I can try connecting WiFi clients.
Comment 3 Horst Schirmeier 2020-04-09 15:18:44 UTC
Is systemsettings / kcm_networkmanagement the right component to file against? In the Ubuntu bug tracker I filed against network-manager (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1871710), and someone suggested to "report it upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager"; does that make sense?
Comment 4 Jacob S. 2023-06-15 16:34:07 UTC
I'm experiencing similar symptoms although mine are more general. When specifying hotspot SSID, as long as the password is blank, my devices connect, but once the password is set, it seems to reject the device outright immediately.