Summary: | WiFi hotspot with WPA/WPA2 Personal security doesn't work with Windows 10 client | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Horst Schirmeier <horst> |
Component: | kcm_networkmanagement | Assignee: | 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
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? (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. 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? 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. |