This bug seems to be fixed in kubuntu Trusty/14.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246992
Title:
WiFi does not connect to WPA2-Enterprise network with TTLS and PAP
auth
To manage
As of last week, the bug was not fixed in Ubuntu 14.04 x64, at least for
me. I can't test it anymore though, since I'm not on campus for the summer.
Good to know Kubuntu works though!
On May 9, 2014 11:25 AM, pfoo 1246...@bugs.launchpad.net wrote:
This bug seems to be fixed in kubuntu
I'd been having trouble connecting to our campus WPA2-Enterprise
(EAP/PEAP) WiFi network using Ubuntu 13.10. The workaround here [1, 2]
worked for me--thanks for sharing @pfoo.
In addition, this [3] thread helped me understand what was going on.
[1]
Until this bug is fixed, here is what you have to do in order to connect
to your ttls/pap wifi network :
- disable network management
- create wpa_supplicant.conf containing :
ctrl_interface=/var/run/wpa_supplicant
#ctrl_interface_group=wheel.
ctrl_interface_group=0
eapol_version=1
ap_scan=1
[edit last comment]
wpa_supplicant.conf must be created in /etc/wpa_supplicant.conf
You'll also need to change ssid= to your wifi network ssid in
/etc/wpa_supplicant.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246992
I might be experiencing the same issue while trying to connect to eduroam (TTLS
/ PAP with no certificate).
I'm running kubuntu and tried kde and gnome nm applet, both failed to connect.
Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless
Network Adapter (rev 01)
--
You
The attachment WifiSyslog.txt that was automatically added to this bug
report doesn't appear to demonstrate the bug. The connection log doesn't
have any attempts to get onto the campus network in it. If someone wants
it, I will post a better log example with a connection attempt to the
campus net.
