aims team mailing list archive
-
aims team
-
Mailing list archive
-
Message #00609
[Bug 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate
I'm having the same problem.
I do NOT have system-ca-certs in the NetworkManager connection file. I
turned off power saving and ipv6. Still get
Dec 19 23:57:06 desktop kernel: [ 110.811108] wlan0: send auth to 00:19:cb:58:f6:b9 (try 1/3)
Dec 19 23:57:06 desktop kernel: [ 110.813360] wlan0: authenticated
Dec 19 23:57:06 desktop kernel: [ 110.813531] rt2800usb 2-1.5:1.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
Dec 19 23:57:06 desktop kernel: [ 110.813536] rt2800usb 2-1.5:1.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
Dec 19 23:57:06 desktop kernel: [ 110.813718] wlan0: associate with 00:19:cb:58:f6:b9 (try 1/3)
Dec 19 23:57:06 desktop NetworkManager[935]: <info> (wlan0): supplicant interface state: authenticating -> associating
Dec 19 23:57:06 desktop kernel: [ 110.829841] wlan0: RX AssocResp from 00:19:cb:58:f6:b9 (capab=0x411 status=0 aid=3)
Dec 19 23:57:06 desktop wpa_supplicant[1348]: wlan0: Associated with 00:19:cb:58:f6:b9
Dec 19 23:57:06 desktop kernel: [ 110.836913] wlan0: associated
Dec 19 23:57:06 desktop kernel: [ 110.836925] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Dec 19 23:57:06 desktop NetworkManager[935]: <info> (wlan0): supplicant interface state: associating -> associated
Dec 19 23:57:07 desktop avahi-daemon[944]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::f27d:68ff:fe15:5756.
Dec 19 23:57:07 desktop avahi-daemon[944]: New relevant interface wlan0.IPv6 for mDNS.
Dec 19 23:57:07 desktop avahi-daemon[944]: Registering new address record for fe80::f27d:68ff:fe15:5756 on wlan0.*.
Dec 19 23:57:11 desktop wpa_supplicant[1348]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:19:cb:58:f6:b9 reason=4
Dec 19 23:57:11 desktop kernel: [ 115.755373] cfg80211: Calling CRDA to update world regulatory domain
Dec 19 23:57:11 desktop kernel: [ 115.758863] cfg80211: World regulatory domain updated:
Dec 19 23:57:11 desktop kernel: [ 115.758867] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Dec 19 23:57:11 desktop kernel: [ 115.758869] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec 19 23:57:11 desktop kernel: [ 115.758872] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec 19 23:57:11 desktop kernel: [ 115.758874] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec 19 23:57:11 desktop kernel: [ 115.758876] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec 19 23:57:11 desktop kernel: [ 115.758878] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec 19 23:57:11 desktop NetworkManager[935]: <info> (wlan0): supplicant interface state: associated -> disconnected
Needless to say, it used to work and all other devices still work, only
13.04 has issues.
--
You received this bug notification because you are a member of AIMS,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1104476
Title:
Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without
CA_Certificate
Status in NetworkManager:
Fix Released
Status in Release Notes for Ubuntu:
Fix Released
Status in “network-manager” package in Ubuntu:
Triaged
Bug description:
=== Release Notes Text ===
When connecting to MPA2/PEAP/MSCHAPv2 wifi networks which do not have
a CA Certificate network manager may incorrectly mark the CA
certificate as needing verification and fail that verification. See
the bug for workarounds.
===
I can connect to Eduroam in 12.10 and any other previous release, but
not in 13.04. I checked, my name and password are correct, all
settings are the same as in 12.10.
Network properties:
security: WPA - WPA2 enterprise
authentication: protected EAP (PEAP)
CA certificate: none
PEAP version: automatic
inner autentication: MSCHAPv2
username: (required)
password: (required)
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: network-manager 0.9.6.0+git201301021750.e78c3e8-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
Uname: Linux 3.8.0-1-generic i686
ApportVersion: 2.8-0ubuntu2
Architecture: i386
CasperVersion: 1.330
Date: Thu Jan 24 21:32:25 2013
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IpRoute:
default via 192.168.43.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.149 metric 9
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130123)
MarkForUpload: True
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
AndroidAP 978da457-563b-4c59-a894-45eb0f74fcb7 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTC yes no /org/freedesktop/NetworkManager/Settings/2
Wired connection 1 6703fabc-9519-49bd-a4af-45fbfb7d660e 802-3-ethernet 1359062570 Thu 24 Jan 2013 09:22:50 PM UTC yes no /org/freedesktop/NetworkManager/Settings/1
eduroam 00f69a95-4a1b-436c-b462-a284f45fbaa1 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTC yes no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1
eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.7.0 connected enabled enabled enabled enabled disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1104476/+subscriptions
