Your message dated Tue, 26 Aug 2014 11:17:02 -0700
with message-id <[email protected]>
and subject line Re: Bug#759357: Acknowledgement (network-manager:
CTRL-EVENT-EAP-FAILURE EAP authentication failed)
has caused the Debian Bug report #759357,
regarding network-manager: CTRL-EVENT-EAP-FAILURE EAP authentication failed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
759357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759357
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 0.9.10.0-1.1
Severity: important
While trying to connect to an "eduroam" WPA2 access point, I
continually get the following CTRL-EVENT-EAP-FAILURE EAP
authentication failure:
Aug 25 16:15:59 servo wpa_supplicant[1386]: wlan0: SME: Trying to authenticate
with 6c:50:4d:b7:07:41 (SSID='eduroam' freq=2462 MHz)
Aug 25 16:15:59 servo kernel: [ 1463.556138] wlan0: authenticate with
6c:50:4d:b7:07:41
Aug 25 16:15:59 servo kernel: [ 1463.561659] wlan0: send auth to
6c:50:4d:b7:07:41 (try 1/3)
Aug 25 16:15:59 servo wpa_supplicant[1386]: wlan0: Trying to associate with
6c:50:4d:b7:07:41 (SSID='eduroam' freq=2462 MHz)
Aug 25 16:15:59 servo kernel: [ 1463.565276] wlan0: authenticated
Aug 25 16:15:59 servo kernel: [ 1463.566276] wlan0: waiting for beacon from
6c:50:4d:b7:07:41
Aug 25 16:15:59 servo NetworkManager[4447]: <info> (wlan0): supplicant
interface state: scanning -> authenticating
Aug 25 16:15:59 servo NetworkManager[4447]: <info> (wlan0): supplicant
interface state: authenticating -> associating
Aug 25 16:16:00 servo kernel: [ 1463.629646] wlan0: associate with
6c:50:4d:b7:07:41 (try 1/3)
Aug 25 16:16:00 servo kernel: [ 1463.632614] wlan0: RX AssocResp from
6c:50:4d:b7:07:41 (capab=0x431 status=0 aid=11)
Aug 25 16:16:00 servo wpa_supplicant[1386]: wlan0: Associated with
6c:50:4d:b7:07:41
Aug 25 16:16:00 servo wpa_supplicant[1386]: wlan0: CTRL-EVENT-EAP-STARTED EAP
authentication started
Aug 25 16:16:00 servo kernel: [ 1463.635186] wlan0: associated
Aug 25 16:16:00 servo NetworkManager[4447]: <info> (wlan0): supplicant
interface state: associating -> associated
Aug 25 16:16:00 servo wpa_supplicant[1386]: wlan0:
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=26 -> NAK
Aug 25 16:16:02 servo wpa_supplicant[1386]: wlan0: CTRL-EVENT-EAP-FAILURE EAP
authentication failed
Aug 25 16:16:04 servo wpa_supplicant[1386]: wlan0: Authentication with
6c:50:4d:b7:07:41 timed out.
Aug 25 16:16:04 servo kernel: [ 1467.945466] wlan0: disassociating from
6c:50:4d:b7:07:41 by local choice (reason=3)
Aug 25 16:16:04 servo wpa_supplicant[1386]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=00:00:00:00:00:00 reason=3
Aug 25 16:16:04 servo kernel: [ 1467.953075] wlan0: deauthenticating from
6c:50:4d:b7:07:41 by local choice (reason=3)
Aug 25 16:16:04 servo kernel: [ 1467.953411] cfg80211: Calling CRDA to update
world regulatory domain
I've tried everything to fix this. I get the same failure with PEAP
or TTLS, whether I specify a CA certificate or not, regardless of
inner authentication.
I'm sure my authentication credentials are correct. I also used the
credentials of a friend of my who *can* connect from his Ubuntu laptop
and it also failed with the same log.
I've tried just using wpa_supplicant on it's own and it also fails.
Maybe this is a wpa_supplicant issue?
I'm at a loss. Please help!
jamie.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (600, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages network-manager depends on:
ii adduser 3.113+nmu3
ii dbus 1.8.6-1
ii init-system-helpers 1.20
ii isc-dhcp-client 4.3.0+dfsg-2
ii libc6 2.19-7
ii libdbus-1-3 1.8.6-1
ii libdbus-glib-1-2 0.102-1
ii libgcrypt11 1.5.4-2
ii libglib2.0-0 2.40.0-4
ii libgnutls-deb0-28 3.2.16-1
ii libgudev-1.0-0 208-6
ii libmm-glib0 1.2.0-1
ii libndp0 1.4-1
ii libnewt0.52 0.52.17-1
ii libnl-3-200 3.2.24-2
ii libnl-genl-3-200 3.2.24-2
ii libnl-route-3-200 3.2.24-2
ii libnm-glib4 0.9.10.0-1
ii libnm-util2 0.9.10.0-1
ii libpam-systemd 208-6
ii libpolkit-gobject-1-0 0.105-6.1
ii libreadline6 6.3-8
ii libsoup2.4-1 2.46.0-2
ii libsystemd-daemon0 208-6
ii libsystemd-login0 208-6
ii libuuid1 2.20.1-5.8
ii lsb-base 4.1+Debian13
ii policykit-1 0.105-6.1
ii udev 208-6
ii wpasupplicant 1.1-1
Versions of packages network-manager recommends:
pn crda <none>
pn dnsmasq-base <none>
ii iptables 1.4.21-2
pn modemmanager <none>
pn ppp <none>
Versions of packages network-manager suggests:
ii avahi-autoipd 0.6.31-4
-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:
[main]
plugins=ifupdown,keyfile
no-auto-default=02:52:02:0D:33:31,F0:DE:F1:18:C6:6A,
[ifupdown]
managed=true
-- no debconf information
--- End Message ---
--- Begin Message ---
Sorry, I think the problem here was actually an authentication issue
with the server, and not a problem with NetworkManager. Once I resolved
the problem with the server I was able to connect. Thanks, and sorry
for the spam.
jamie.
pgptIkoaIJ0pn.pgp
Description: PGP signature
--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
