Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NetworkManager |
Confirmed
|
Medium
|
|||
network-manager (Ubuntu) |
Triaged
|
High
|
Unassigned |
Bug Description
Hello,
since update to Bionic Beaver I can't connect to my WPA2-Entertrise EAP TLS network. Running Freeradius 2.29 on a DDWRT router. In 16.04 it worked, in the dual boot Windows 10 environment it is still working with the same certificates.
It is a hidden network, adding it by "connect to a hidden network" entering SSID, UserID, ca.pem as CA cert, user cert xxx.p12 file and user certificate password.
Tried a lot not getting it working. The password entry dialog for the network is always popping up upon connection trials. The password is for sure the correct one, checked it very often.
If I'm able to I'll attach a syslog and kern.log of error occurense.
Thanks for investigation and inputs.
Best regards
Kitsab
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Apr 3 23:52:23 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2015-02-14 (1144 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: gnome-control-
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in network-manager (Ubuntu): | |
status: | New → Triaged |
Changed in network-manager: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https:/ /wiki.ubuntu. com/Bugs/ Upstream/ GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.