[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP (Enterprise) network (disassociating by local choice (reason=3) )

Can confirm this with two different WPA-networks at my university. Similar hardware, worked under Gutsy for me (I skipped Hardy so fast that I did not get to try). Works with wicd under Intrepid.

please restart your system in range of that network. reproduce the connect failure twice, and attach the complete syslog taken afterwards.

Same problem, Intel 3945ABG hardware. Work perfectly under 8.04.1

Here is the requested file.

Same here,
up-to-date Intrepid,
with /etc/ssl/certs/class3.pem.
Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)

Is a duplicate of Bug #264881 ???

I also have trouble connecting to the Enterprise WPA network (PEAP MS-CHAP v2) at my University.
It's really rather hit and miss if the network connects or not. Sometimes it tales several attempts at entering in the auth details before I can get it to connect generally associated with lots of 'NetworkManager: <info> wlan0: link timed out.' in the syslog. (Once connected it works quite happily. I'm using it for a connection now)

I'm using a Intel Wireless WiFi Link 4965AGN with the iwlagn driver. I was having the same issue with NM from the Hardy NM 0.7 PPA using the iwl4965 driver in Hardy. Had wondered if it was either the older driver or using NM 0.7 on Hardy. Unfortunately the problem does persist. I'm planning to try using just wpasupplicant without NM to see if I can get that to associate (and thus see if it's a NM related issue)

And conveniently it just happened to me as I went to the next building. This is just after waking the laptop up from suspend and letting it try and auto-connect. First time failed. Only had to enter in the authentication once this time to get it working. Attached is the syslog from the attempt showing both a unsuccessful and successful connection.

I'm having the same (or similar) problem.

After upgrading from 8.04 to Intrepid beta, I can not connect to my campus wireless network (WPA enterprise EAP-TLS) using network manager. The connection always fails. Before the upgrade, this worked flawlessly.

I can connect if I use wpa_supplicant from the command line, but only if I stop network-manager first (/etc/init.d/NetworkManager stop).

Also, network manager works fine on my home wireless network (WPA-PSK).

I'm attaching a portion of my syslog (beginning when I start network manager, and including a failed attempt to connect). My wireless card is an Intel 3945ABG.

I am also having trouble. For the sake of other user's searching, this is at University of Illinois (uiuc), trying to connect to UIWpa2.

Running up-to-date Intrepid beta. I'll try to get some logs up later.

Same problem here. Attached you will find the portion of syslog regarding network manager

NIC: 0c:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)
Uname: Linux callisto 2.6.27-5-generic #1 SMP Fri Oct 3 00:36:38 UTC 2008 x86_64 GNU/Linux
System version: Ubuntu 8.10 Beta

Same problem here since upgrading to intrepid (over a month). Attached a chunk of syslog.

NIC: 0b:02.0 Network controller: Intel Corporation PRO/Wireless 2915ABG Network Connection (rev 05)
Uname: Linux euler 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC 2008 i686 GNU/Linux

Ding ding ding.

Works flawlessly if I use wpa_supplicant, not so much if I try network-mangler.
Network-mangler 0.7~~svn20080928t225540+eni0-0ubuntu2
NIC: 03:00.0 Ethernet controller: Atheros Communications Inc. AR5212 802.11abg NIC (rev 01)
Uname: Linux eris 2.6.27-4-generic #1 SMP Wed Sep 24 01:29:06 UTC 2008 x86_64 GNU/Linux

I'm going to go compile 0.6 and see what I get.

could you please try to load your iwl3945 or iwl4965 driver with disable_hw_scan=1 like:

 modprobe -v -r iwl3945
 modprobe -v iwl3945 disable_hw_scan=1

or

 modprobe -v -r iwl4965
 modprobe -v iwl4965 disable_hw_scan=1

Should this generalize to ipw2200 drivers as well?

No change for me loading modprobe -v iwl3945 disable_hw_scan=1.

doing the modprobe -v... didn't have any effect either.

I think this bug was inappropriately changed to iwl3945 + iwl4965. This is affecting ipw2200 users and I tried it on an atheros card earlier with similar results.

It affects at least iwl4965 since this is my case!

I tried reloading the iwl3945 using the disable_hw_scan=1 option:

 modprobe -v -r iwl3945
 modprobe -v iwl3945 disable_hw_scan=1

This didn't help at all.

Also, I don't think this bug has any specific relation to the Intel wireless card (iwl3945/iwl4965): I have reproduced the bug using a USB wireless interface (Zydas 1211 chipset). I set the kill switch for the built in Intel card, and plugged in my USB card; syslog showed Network Manager failing with the same errors: link time out, association took too long, disassociating by local choice (reason=3), etc.

Both devices work fine if I kill NetworkManager and run wpa_supplication manually.

I'm attaching syslog excerpts for failed connections when using both devices.

Also affects prism54 chipsets too.

I have attempted to downgrade several packages to hardy level including network-manager, network-manager-gnome, dhcdbd, libnm, wpa-supplicant etc., but all have exhibited the same behaviour of attempting to connect, and then doing the local disconnect=3 message

Problems with 2.6.27 kernels.
And not only iwl2945, tested with a usb zd1211 chip (3com)

I've tested with 2.6.24-19 and it's working well.

Now I'm testing with 2.6.22-14 and iwl3945 is not working, same behavior as 2.6.27-6 (today's updates). BUT zd1211 is Working like a charm.

I don't know how else can aport to debug. I'll atach my 2.6.22-14 dmesg for debugging pourposes.

Reloading the module did not help me at all.
This problem is getting more and more annoying...

This is looking more like an NM issue, however I don't have an AP capable of WPA Enterprise in order to conclusively prove it.

I did get connected with Tunnel TLS instead of PEAP, which the NOC group on my campus told me should not be compatible with there system

I would like to tell that the todays update of NetworkManager did not solve the issue. Same problem, same logs!

http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1629

the user there reports it without using NM at all. reopening linux task, adding wpasupplicant task until we know whats going on.

not in progress for NM until we know what causes this.

I'm here to give any additional information that might be useful, just ask.

In my opinion, it looks like something more related to the kernel or driver rather than NM.

On my system this is clearly a Network Manger bug, not a kernel/driver bug.

I have two kernels installed, 2.6.24-21-generic and 2.6.27-4-generic. When I boot the older 2.6.24 kernel I cannot connect using Network Manger, but I connect right away using wpa_supplicant from the command line. When I boot the newer 2.6.27 kernel, I am also unable to connect using Network Manger, but once again wpa_supplicant connects right away from the command line.

I am attaching four files showing syslog during attempts to connect using NM and wpa_supplicant on the 2.6.24 kernel, and attempts to connect using NM and wpa_supplicant on the 2.6.27 kernel.

could you also please attach a tail on /var/log/wpa_supplicant.log?

This is happening for me too with ndsiwrapper and BCM4328. It worked great yesterday (October 15) and after aptitide dist-upgrade it won't work at all today. WPA Personal networks work perfectly. I can't connect using wpa_supplicant alone either.

I got new output from wpa_supplicant after rebooting to use the new wl driver instead of ndiswrapper. The logging in daemon.log is the same, and the wpa_supplicant logging is the same after reverting back to ndiswrapper.

I'm attaching two pieces of wpa_supplicant.log. Both are from connection attempts using Network manager. The first log file seems to show two errors:

TLS: Certificate verification failed, error 19 (self signed certificate in certificate chain) depth 2 for '/DC=edu/DC=marshall/CN=Marshall University Root CA'
SSL: SSL3 alert: write (local SSL3 detected an error):fatal:unknown CA

SSL: SSL3 alert: write (local SSL3 detected an error):fatal:unknown CA
OpenSSL: tls_connection_handshake - SSL_connect error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

The first error looks like a red herring: I removed the CA cert from the nm-applet configuration, and tried again, but the connection still failed with:

OpenSSL: tls_connection_handshake - SSL_connect error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

bug 284409 ... is about TLS over wired. Looks similar.

No, 284409 is also over wireless.

LarryGrover, can you try to add the CA certificate to /etc/ssl/certs and then rehash it. I.e after putting the CA in for example /etc/ssl/certs/myUniversityCA.pem, run 'update-ca-certificates --fresh', and then try again. Without the CA certificate specified in nm.

actually it seems to work for me when i use fluxbox instead of gnome

This started working for me this morning again. Not sure why, nothing that was updated last night (for me anyway) was drivers, NM, wpa_supplicant, or kernel.

this morning it stopped working for me again, (but vpn started working)

I also have this issue and I am using the iwl4965 driver as well. I can get my wireless connection to work through Network Manager, but I need to mess around with it each time I boot the machine. This is definitely not a solution but hopefully it can help in the diagnostics of the bug. Here are the steps I take:
Left click the NM icon and select Connect to Other Wireless Network. Enter all the information for my WPA network and hit okay. At this point, NM shows that I am connected to my network, but it will not give me an IP address through dhcp. I then left click on NM and select manual configurations. Here I choose to set a static ip address since dhcp will not work. After setting a static ip address, I am able to use my network again. Every time I reboot, I have to go through these steps again.

And, my wireless network worked fine with Ubuntu for months before this. I believe this started happening after installing some updates within the last 2 months.

what you could try is to use gnutls and not nss for the applet/nm-daemon.

For that change debian/rules as follows:

1. for network-manager: --with-crypto=nss -> --with-crypto=gnutls
2. for network-manager-applet: --without-gnutls -> --with-gnutls AND --with-nss -> --without-nss

of course as build-dependency that also requires libgnutls-dev installed on top of apt-get build-dep network-manager and apt-get build-dep network-manager-gnome

I will see if I can get a package somewhere. But if you know how to build a package, go ahead like described above.

duped bug 284409 in which author has outlined a workaround. Consider to test if that works for you too.

Thanks,
 - Alexander

This has just started working for me. It appears to have been fixed sometime in the last week.

I've got a trick to solve the problem.
Just kill NetworkManager with sudo killall nm-applet, press Alt+F2 and type nm-applet, now the connection should work!

Tell me if it works even for you

nm-applet isn't present in KDE.

For me, it's a 3945ABG with WPA2 and enterprise security, i. e. TLS with certificates.Hardware and basic stuff seems ok, if I use wpa_supplicant directly, I can connect just fine.

Whenever I configure this network through KNetworkManager, the certificate information is apparently not saved. It doesn't end up in .kde/share/config/knetworkmanagerrc, and it isn't shown when I re-edit the connection.

This may be a general problem with saving certificates in KDE4, Konqueror for instance doesn't remember root certificates I installed either.

how is the filename for your cert?

user cert is eduroam.crt
root cert is rootcert.crt
user key is eduroam.key

Nothing egregiously stupid here it seems.
It makes no difference if I give relative or absolute paths.

I should add that this used to work in [K]Ubuntu 8.04 (Hardy Heron GNOME and KDE) and fails in Intrepid Ibex beta KDE4 (didn't try GNOME).

Please test if the following applet helps:

(i386): https://edge.launchpad.net/%7Enetwork-manager/+archive/+files/network-manager-gnome_0.7~~svn20081020t000444-0ubuntu1~nm1_i386.deb

(amd64): https://edge.launchpad.net/%7Enetwork-manager/+archive/+files/network-manager-gnome_0.7~~svn20081020t000444-0ubuntu1~nm1_amd64.deb

I can confirm that this new version fixed the problem for me. Now it works as soon as I log in!!! Hope that it works too at home.

Thanks a lot,

Giorgio

OK. lets assume that we nailed this issue then. The fix will go to nm-applet. reassigning package. Also setting fix committed as the fix is already on the bzr branch (see related branches section of this bug)

openvpn is also affected

not a kernel bug then.

The "doesn't work with KNetworkManager" issue is still open though.

This bug was fixed in the package network-manager-applet - 0.7~~svn20081020t000444-0ubuntu1

---------------
network-manager-applet (0.7~~svn20081020t000444-0ubuntu1) intrepid; urgency=low

  New upstream snapshot Mon 2008-10-20 00:04:44 +0000 (rev 819)
  * support .cer and .crt extensions for wpa-eap (LP: #272185)
    - update src/wireless-security/eap-method.c
  * Don't translate widget labels
    - update src/connection-editor/ce-page-ip4.glade
  * updated translations for sv, es, hu, sk, nb, be, he

 -- Alexander Sack <email address hidden> Mon, 20 Oct 2008 16:30:10 +0200

Not for me.

I've installed the fixed package and my wireless still echoing the "disassociating by local choice (reason=3)" message.

I've tested with zd1211 usb wireless adapter too for debuggin pourposes.

Dmesg attached.

XaRz, could you please follow the build instructions i gave to test gnutls instead of nss as crypto library:

 https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/272185/comments/48

also please attach the output of tail -n0 /var/log/wpa_supplicant.log when experiences the "by local choice" disconnects.

Same results building the packages following your instructions.

I attach dmesg and tail wpa_suplicant (with -n0 no output)

dmesg

your wpa_supplicant.log doesnt include a disconnect. does it?

This still doesn't seem to be fixed for me in the latest updates. Same behavior as before. Just updated to the new network-manager-gnome.

Alexander,

Yes It has a disconnect: "CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys" in wpa_supplcant.

I attach the dmesg and wpa log from at work, where the wpa is working like a charm as always.

nm-connection-editor from network-manager-gnome 0.7~~svn20081020t000444-0ubuntu1 STILL does not work for me.

Settings are:

TAB: Wireless Security
Security: WPA & WPA2 Enterprise
Authentication: TLS
Identity: (as given by NOC)
User Certificate: eduroam.crt
CA Certificate: rootcert.crt
Private Key: eduroam.key
Private Key Password: (as configured for key)

I also tried renaming them to .pem, to no avail.

I know the settings are correct since I can pass them to wpa_supplicant and it will work.

While editing the settings (even after completion), I get these console messages:

** (nm-connection-editor:13164): CRITICAL **: convert_iv: assertion `src != NULL' failed

** (nm-connection-editor:13164): WARNING **: Invalid setting Wireless Security:Invalid wireless security

Matthias,

Just out of interest, have you tried removing the existing configurations and creating a new one from scratch? I found that mine didn't start working until I did this for some reason.

The today update of network-manager has broken another time nm-applet. Was this packet suppose to solve the issue?

Even after updating to new network-manager and network-manager-gnome, I'm still having problems using a CA certificate. If I add my University's certificate (through the nm-applet dialog) then I get and error in wpa_supplicant.log, and the connection fails:

CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
TLS: Certificate verification failed, error 19 (self signed certificate in certificate chain) depth 2 for '/DC=edu/DC=marshall/CN=Marshall University Root CA'
SSL: SSL3 alert: write (local SSL3 detected an error):fatal:unknown CA
OpenSSL: tls_connection_handshake - SSL_connect error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
CTRL-EVENT-EAP-FAILURE EAP authentication failed

If I delete the CA cert from the applet setup, then I get a pop-up window warning that not using a CA certificate can result in connections to insecure networks, etc, but if I click through the warning (click the Ignore button), then I do connect successfully, and wpa_supplicant.log shows:

Trying to associate with 00:16:9c:93:c9:b0 (SSID='MU WiFi' freq=2462 MHz)
CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully (based on lower layer success)
WPA: EAPOL-Key Replay Counter did not increase - dropping packet
Associated with 00:16:9c:93:c9:b0
WPA: Key negotiation completed with 00:16:9c:93:c9:b0 [PTK=CCMP GTK=CCMP]
CTRL-EVENT-CONNECTED - Connection to 00:16:9c:93:c9:b0 completed (reauth) [id=0 id_str=]

So it's working, sort of, but I can't use the CA cert from my University.

I tried Björn Torkelsson's suggestion (add CA cert to /etc/ssl/certs/ and run 'update-ca-certificates --fresh') but that didn't seem to make any difference.

Ok... Latest update broke this again.

This set up does work:
network-manager_0.7~~svn20081015t224738-0ubuntu1_i386
network-manager-gnome_0.7~~svn20081015t194645-0ubuntu1_i386

This set up does not:
network-manager_0.7~~svn20081018t105859-0ubuntu1_i386
network-manager-gnome_0.7~~svn20081018t105859-0ubuntu1_i386

I may have a quick diff between them and see if I can't figure something out...

I'm connecting to my school WiFi network and encounter the same problem with intrepid up-to-date as of today. The WiFi network is actually composed of two networks, one is WPA Entreprise and the other WPA2 Entreprise. Both are using MSCHAP v2 and PEAP authentication, and I don't need to specify a CA certificate, only login and password.

Sometimes, the connection to the WiFi network will only lasts a few seconds, then I won't be able to connect during minutes. Here is the output of dmesg after an attempt has failed :
[ 2776.852101] wlan0: deauthenticated
[ 2777.849277] wlan0: authenticate with AP 00:12:cf:54:7b:60
[ 2777.851214] wlan0: authenticated
[ 2777.851229] wlan0: associate with AP 00:12:cf:54:7b:60
[ 2777.854944] wlan0: RX ReassocResp from 00:12:cf:54:7b:60 (capab=0x31 status=0 aid=4)
[ 2777.854957] wlan0: associated
[ 2778.587209] wlan0: disassociating by local choice (reason=3)

I'm also having trouble connecting to our Eduroam WPA/Enterprise in Intrepid Xubuntu. It works fine with wpa_supplicant, and worked fine in Hardy & network-manager 0.6. dmesg output is similar to Matthieu's above, and wpa_supplicant.log contains entries like:

CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:1a:1e:bc:43:60 (SSID='eduroam' freq=2437 MHz)
Associated with 00:1a:1e:bc:43:60
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

Killing off nm-applet and running it from a console, I noticed:

** (nm-applet:5449): WARNING **: Unhandled setting secret type (write) '802-1x/private-key' : 'GArray_guchar_'

** (nm-applet:5449): WARNING **: Unhandled setting secret type (write) '802-1x/phase2-private-key' : 'GArray_guchar_'
** Message: <info> New secrets for Auto eduroam/802-1x requested; ask the user

every time I submitted credentials.

Authentication should work via EAP-TTLS/PAP or PEAP/MSCHAPv2.

Looking at our RADIUS logs, it seems that network-manager isn't responding properly; we get a Packet-Type = Access-Request followed immediately by an Access-Challenge, but no further traffic, whereas a successful negotiation generates several Access-Challenge/Access-Request pairs followed by Access-Accept.

Again no CA certificate specified (the TLS cert is properly signed) and no anonymous-identity provided (it still fails if I provide one).

Hmm! I got it work by being somewhat closer to the access point (though I've tried being nearer equivalent access points before). Perhaps network-manager 0.7 is more susceptible to marginal reception during the WPA[2]/Enterprise negotiation? Is there a timeout value that can be tweaked?

I should also have said that my network card is bc43xx-based and the machine is a rather old Sony laptop with extra memory.

I'm repeating that It seems a kernel problem: 2.6.27 is not working well with wpa or encryption. Please all people having issues: Can u try with 2.6.24 or 2.6.22 or 2.6.20?

I've working great with 2.6.22 and 2.6.20. In 2.6.24 I've one kernel package missing and I can't check it right now,

Regards,

On Sun, 26 Oct 2008, XaRz wrote:

> I'm repeating that It seems a kernel problem: 2.6.27 is not working well
> with wpa or encryption. Please all people having issues: Can u try with
> 2.6.24 or 2.6.22 or 2.6.20?

Why would it be a kernel issue if you can get it to work with the most
current Intrepid kernel + "manual" setup with wpa_supplicant + DHCP client?
Not quite clear to me.

If it's an incompatibility, NetworkManager is likely the piece to be
fixed, it's a 0.x version and has always had one issue or another...

--
Matthias Andree

This seems to be a timing thing.

I'm having the same problem and my log lists

NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2
NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 0
NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2
NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 0
NetworkManager: <info> wlan0: link timed out.
NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2
NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 0
NetworkManager: <info> Activation (wlan0/wireless): association took too long.
NetworkManager: <info> (wlan0): device state change: 5 -> 6
NetworkManager: <info> Activation (wlan0/wireless): asking for new secrets

Sometime, very occasionally, it will authenticate and then it seems to stay authenticated. I'm sat about 6 feet from the AP aerial so I get something like 97% signal strength according to nm-tool. But, this looks a little strange as they seem to be the same MAC (unless I'm misunderstanding what the output of nm-tool gives)

  Wireless Access Points
    <Network Name>: Infra, 00:1B:90:57:36:40, Freq 2422 MHz, Rate 54 Mb/s, Strength 98
    <Network Name>: Infra, 00:1B:90:57:36:40, Freq 2422 MHz, Rate 54 Mb/s, Strength 95
    <Network Name>: Infra, 00:1B:90:57:36:40, Freq 2422 MHz, Rate 54 Mb/s, Strength 92
    <Network Name>: Infra, 00:1B:90:57:36:40, Freq 2422 MHz, Rate 54 Mb/s, Strength 93
    <Network Name>: Infra, 00:1B:90:57:36:40, Freq 2422 MHz, Rate 54 Mb/s, Strength 91
    <Network Name>: Infra, 00:1B:90:57:36:40, Freq 2422 MHz, Rate 54 Mb/s, Strength 93
    <Network Name>: Infra, 00:1B:90:57:36:40, Freq 2422 MHz, Rate 54 Mb/s, Strength 99
    <Network Name>: Infra, 00:1B:90:57:36:40, Freq 2422 MHz, Rate 54 Mb/s, Strength 98
    <Network Name>: Infra, 00:1B:90:57:36:40, Freq 2422 MHz, Rate 54 Mb/s, Strength 98
    <Network Name>: Infra, 00:1B:90:57:36:40, Freq 2422 MHz, Rate 54 Mb/s, Strength 97
    <Network Name>: Infra, 00:1B:90:57:36:40, Freq 2422 MHz, Rate 54 Mb/s, Strength 97
    <Network Name>: Infra, 00:1B:90:57:36:40, Freq 2422 MHz, Rate 54 Mb/s, Strength 97

I sometimes had this issue with 8.04 as well but the 8.10 RC seems to be worse.

Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
Linux xxxxxxxxx 2.6.27-7-generic #1 SMP Fri Oct 24 06:40:41 UTC 2008 x86_64 GNU/Linux
Samsung X65 laptop.

I uploaded 0.7~~svn20081018t105859-0ubuntu2~nm3 to network-manager ppa (intrepid) with an increased supplicant timeout. please test that package.

PPA is: https://edge.launchpad.net/~network-manager/+archive

PPA doesn't seem to have helped. Still get the "Association took too long" errors. Surely another issue is that if the error is this "took too long" then prompting for access credential is not the thing to do.

I also tested the ppa, and it doesn't work for me either. Here is my syslog during a connection attempt.

I also tried the 0.7~~svn20081018t105859-0ubuntu2~nm3 network-manager PPA packages and saw no improvement.

If I try to connect with my CA cert included in the configuration, wpa_supplicant.log shows the same error message as before, but this time its repeated 3 times, so I guess NM is at least trying more than once, but still not succeeding:

CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:18:74:c7:da:31 (SSID='MU WiFi' freq=2462 MHz)
Authentication with 00:18:74:c7:da:31 timed out.
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:18:74:c7:da:31 (SSID='MU WiFi' freq=2462 MHz)
Associated with 00:18:74:c7:da:31
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
TLS: Certificate verification failed, error 19 (self signed certificate in certificate chain) depth 2 for '/DC=edu/DC=marshall/CN=Marshall University Root CA'
SSL: SSL3 alert: write (local SSL3 detected an error):fatal:unknown CA
OpenSSL: tls_connection_handshake - SSL_connect error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
CTRL-EVENT-EAP-FAILURE EAP authentication failed
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
TLS: Certificate verification failed, error 19 (self signed certificate in certificate chain) depth 2 for '/DC=edu/DC=marshall/CN=Marshall University Root CA'
SSL: SSL3 alert: write (local SSL3 detected an error):fatal:unknown CA
OpenSSL: tls_connection_handshake - SSL_connect error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
CTRL-EVENT-EAP-FAILURE EAP authentication failed
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
TLS: Certificate verification failed, error 19 (self signed certificate in certificate chain) depth 2 for '/DC=edu/DC=marshall/CN=Marshall University Root CA'
SSL: SSL3 alert: write (local SSL3 detected an error):fatal:unknown CA
OpenSSL: tls_connection_handshake - SSL_connect error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
CTRL-EVENT-EAP-FAILURE EAP authentication failed
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

Also, the syslog continues to show the same errors: "link timed out" and "disassociating by local choice (reason=3)"

Once again, if I remove the CA cert from the NM configuration, then it connects just fine, and if I use the CA cert with wpa_supplicant from the command line, it also works just fine.

I am also seeing the same issues with disassociating by local choice. I have been checking everything out on the backend and the system isn't even attempting to auth at all. I have checked the logs on our radius server. I can provide any additional information. I have verified that there is not a problem with the driver as I can connect with wpa_supplicant when NetworkManager has been disabled. Also, I did run into a couple of issues with the modules. If I attempt to load wpa_supplicant then disconnect it, I am unable to reassociate until I unload the entire wireless stack then reload them. Also, I am running all of the latest updates to the RC for ibex

hardware: IBM T61
Card: iwl4965
driver: iwlagn

frooky, are you using the latest PPA packages i posted?

also, if you see the "Activation (eth1/wireless): association took too long." in syslog, please use the wpasupplicant manually and let me know how long it takes for you until wpasupplicant connects.

LarryGrover, I really think your bug is unrelated to what the majority of reporters see here. lets open a new bug for your certificate verification issue. Please do that and post your bug id here. Thanks!

ok, one more try: i uploaded 0.7~~svn20081018t105859-0ubuntu2~nm4 to the same PPA. That one gives you _3_ minutes time to associate. if its really just super-slow for you that should be enough. Please test and post your syslog in case it still fails.

oh also tail -n0 -f /var/log/wpa_supplicant.log | tee /tmp/wpa.txt

while doing such a connect attempt. Please attach the output too.

uploading a fail Eduroam Wifi EAP TTLS PAP try

I guess I should update this with my latest findings!

We have multiple access points with the same ssids on each, eduroam (WPA/WPA2 Enterprise) and eduroam-web (unsecured) and generally the same channel numbers.

I can always connect to eduroam-web with network-manager in both Intrepid (installed, and using the ppa nm3 version above) and Hardy (booted off a Xubuntu Live CD). I can sometimes connect to eduroam with network-manager if I am near a single access point.

There are places (say 35% strength) where I can connect with wpa_supplicant that don't work with network-manager.

Where there are two fairly nearby access points (say 60% strength) neither wpa_supplicant or network-manager seem to work in either version of Ubuntu.

I'm suspecting there may be more than one issue, with the Broadcom b43 driver maybe not handling the multiple access points well (as in bug 111502?) and network-manager not doing so well generally in marginal reception.

I'll give the ppa nm4 build a go tomorrow and hopefully upload some logs. I may also be able to beg/borrow another wireless card for comparison.

This doesn't seem like an issue of speed for me. The key difference in the log for me is

with NetworkManager:

Associated with 00:0f:34:79:53:01
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
EAP-PEAP: Failed to select forced PEAP version 1

without NetworkManager (manual config):
Associated with 00:0f:34:79:4e:31
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
OpenSSL: tls_connection_handshake - Failed to read possible Application Data error:00000000:lib(0):func(0):reason(0)
EAP-MSCHAPV2: Authentication succeeded
EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed
CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
WPA: Key negotiation completed with 00:0f:34:79:4e:31 [PTK=CCMP GTK=CCMP]
CTRL-EVENT-CONNECTED - Connection to 00:0f:34:79:4e:31 completed (auth) [id=0 id_str=]

I agree that this is not a timing issue. When I connect manually to my WPA2 access point with wpa_supplicant, it connects almost instantly.

I just updated and tested with the latest gnome applet as well as main app. Still no go.

I have the logs and will upload them in a bit. (probably later this afternoon when I get a wired connection on that system)

Couple things that I found interesting was that once it showed associated in the logs, it imeadiatly did the disassociated by choice. This was within a second of the association message. It then asked me for the settings again and then sat for the 3 min. After the third time it finally connected. I was able to connect easily after that. I then rebooted and it's showing the same issues.

Another note, if I attempt to force it to start over a couple of times (selecting the network from the applet) it will connect and auth.

Here is the logs from boot to the failed to the logins

if you look at the syslog you see the wpasupplicant config values used. an example below.

If you are one of the lucky ones that can connect manually please try the config values from your NM connect attempt from syslog and see if you can use those in wpasupplicant.conf.

If that doesnt work, compare with the manual config that works and play around until you find what is wrong in the config.

Thanks!

here the example snippt where you can see the wpasupplicant.conf keys and how they are set by NM:

Oct 31 12:26:16 clotho NetworkManager: <info> Config: added 'ssid' value '<removed for security>'
Oct 31 12:26:16 clotho NetworkManager: <info> Config: added 'scan_ssid' value '1'
Oct 31 12:26:16 clotho NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-EAP'
Oct 31 12:26:16 clotho NetworkManager: <info> Config: added 'proto' value 'WPA RSN'
Oct 31 12:26:16 clotho NetworkManager: <info> Config: added 'pairwise' value 'TKIP CCMP'
Oct 31 12:26:16 clotho NetworkManager: <info> Config: added 'group' value 'WEP40 WEP104 TKIP CCMP'
Oct 31 12:26:16 clotho NetworkManager: <info> Config: added 'eap' value 'TLS'
Oct 31 12:26:16 clotho NetworkManager: <info> Config: added 'fragment_size' value '1300'
Oct 31 12:26:16 clotho NetworkManager: <info> Config: added 'ca_cert' value 'blob://-org-freedesktop-NetworkManagerSettings-0-ca_cert'
Oct 31 12:26:16 clotho NetworkManager: <info> Config: added 'client_cert' value 'blob://-org-freedesktop-NetworkManagerSettings-0-client_cert'
Oct 31 12:26:16 clotho NetworkManager: <info> Config: added 'private_key' value 'blob://-org-freedesktop-NetworkManagerSettings-0-private_key'
Oct 31 12:26:16 clotho NetworkManager: <info> Config: added 'identity' value '<removed for security>'

I also have the same problem.
Before upgrading to Intrepid (from Hardy Heron), it was working fine. Now it keeps poping for the passkey.

My hardware:

1 - Laptop
Toshiba U300-130
04:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)

2 - Router
Fon with WPA2

Software:
Fresh install of Ubuntu 8.10 32bits with the latest upgrades including backports
Linux jmachado-ubuntu 2.6.27-7-generic #1 SMP Thu Oct 30 04:18:38 UTC 2008 i686 GNU/Linux

I also subscribed to Bug #263963 on NetworkManager, but they seem to come to the conclusion that the issue is here.

Having the same problem.

Just did a clean install of Intrepid; this entire setup worked in Hardy. I *can* occasionally connect to the WPA2 Enterprise wireless, but it will disconnect me within about 3-5 minutes with the reason=3 line popping up in dmesg.

Using a Dell XPS M1210, 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)

Arrdee, the latest packages in https://edge.launchpad.net/~network-manager/+archive should fix you most likely. Could you please try and tell us how long an average connect attempt takes for you?

Hi,
I am a complete noob when it comes to networking.
I just upgraded to 8.10 from 8.04 and I can not connect to WPA2 on my university's network anymore. Before (on 8.04) it used to work seamlessly.
Just in case other ppl are looking ... this is the WPA2 network of UIUC (University of Ilinois, urbana-champaign).

The wireless card that I am using is: Intel 4965AGN on a thinkpad T61.
As I said before, I do not know much about networking, so you would have to tell me what all details you would like to know from my side.

The config for Vista as posted on the university website are:
Network name: UIwpa2
Security type: WPA2-Enterprise
Encryption type: AES
Don't check "Connect even if the network is not broadcasting"
Choose a network authentication method: Protected EAP (PEAP)
Uncheck Cache user information for subsequent connections to the network.
 In the Protected EAP Properties window, enter the following information:
Check "Validate server certificate"
Check "Connect to these servers"
In the servers text box, enter the following (without spaces): neauth1.cites.uiuc.edu;neauth2.cites.uiuc.edu
Trusted Root Certification Authorities: Check "Thawte Premium Server CA"
Check "Do not prompt user to authorize new servers or trusted certificate authorities"
Authentication method: Secured password (EAP-MSCHAPv2)
Check "Enable fast reconnect"
Don't check "Enable quarantine checks"
Don't check "Disconnect if server does not present cryptobinding TLV

thanks,
Rahul

swiftrahul, please check the latest packages from https://edge.launchpad.net/~network-manager/+archive

Hi!

I'm having the same issue as most people here; connecting to a WPA2 Enterprise network with PEAP and MS-CHAPv2.

I have tried the latest packages to no avail. Posting dmesg output here and syslog below.

// Mike

I checked out the latest package and updated the packages, but that didnt help.
Is there any way, I could use the older package (0.6.x) that was used in ubuntu hardy 8.04 ?
I am currently using 8.10.

thanks,

no, but you could try booting the hardy kernel (which you probably havent removed). not sure what would break but would surely be worth a try.

Alexander, I installed on a new system (Lenovo T500 with the intel 5100 wireless card) the base install and was unable to get connected. Also there was a large amount of failures with wpa_supplicant (would take 5 min to get connected). I updated the network-manager files from the ppa and rebooted. after the reboot I was automatically connected with out issue. I will give you any updates that I come across with my testing.

Alexander Sack wrote on 2008-10-30:
LarryGrover, I really think your bug is unrelated to what the majority of reporters see here. lets open a new bug for your certificate verification issue. Please do that and post your bug id here. Thanks!

New bug for CA cert issue: Bug #293238: network manager (WPA-EAP TLS) fails - can't use CA certificate

Rahul,

I also go to UIUC and have the same problem as you (8.10 NetworkManager not connecting to the WPA2 network, but 8.04 works fine). I am able to connect via wpa_supplicant. Here is my wpa_supplicant.conf file:

ctrl_interface=/var/run/wpa_supplicant
eapol_version=1

network={
 ssid="UIwpa2"
 scan_ssid=1
 key_mgmt=WPA-EAP
 eap=PEAP
 identity="identity"
 password="password"
 phase2="auth=MSCHAPV2"
}

I forgot to mention, I am using the latest PPA packages, and that does not fix the problem. Only wpa_supplicant works for the time being.

Hey Albert,
Thanks for the wpa_supplicant conf file.

Just a quick question to raise really quick due to the situation that I experienced between the two laptops that I have:

Could this problem be related to drivers
   I know that things work with wpa_supplicant (I have verified this with two intel chips: 3945 and the 5100)
   With the 5100 the fix worked flawlessly, on the other hand the 3945 did not. It would only connect every 5 attempts and only for a
       couple of min (All on the same network with the same settings, same AP, same certs, etc. The only thing that changed was the
       laptop hardware)

Just a possibility that there is something driver related in addition to the NM problems or possibly the interface there with wpa_supplicant, NM, and drivers. Just a thought

Albert,
I tried using the conf file and getting connection to work using wpa-supplicant.
For some reason, I am failing to get it working.
I am using Intel 4695 AGN Wireless card.

If you are using the same wireless card, would it be possible for u to also make a post/"how to" for using wpa_supplicant.

Albert,
I tried using the conf file to get the connection working using wpa-supplicant.
For some reason, I am failing to get it working.
I am using Intel 4695 AGN Wireless card.

If you are using the same wireless card, would it be possible for u to also make a post/"how to" for using wpa_supplicant.

Alexander --

Using the packages from https://edge.launchpad.net/~network-manager/+archive , the secure network connects immediately, just like it used to in Hardy. Seems that fixed it. I've had a solid connection now for around 20 minutes, and no disconnects.

And it looks like I spoke too soon. Still disconnected, but the packages in the PPA certainly seemed to allow me to connect for much longer.

If you have a wpa_supplicant.conf file for your wireless network, here is how you can work around this problem.

# put the following in a script, and run with sudo
# shutdown network manager, and connect to network manually
set -x
/etc/init.d/NetworkManager stop
/etc/init.d/wpa-ifupdown stop
iwconfig eth1 essid YourWirelessNetworkName
ifconfig eth1 up
wpa_supplicant -ieth1 -c /etc/wpa_supplicant/your_wpa_config.conf -d -f /var/log/wpa_supplicant.log&
dhclient eth1

# To start Network Manager up again, run the following (in a separate script)
killall wap_supplicant
/etc/init.d/wpa-ifupdown start
/etc/init.d/NetworkManager start

Obviously, you will not be able to use any of the other features of network manager while it is shut down, and you will have no signal strength checking, etc. Only do this if you know what you are doing. If all else fails, reboot and you will be back to where you were before.

EDIT:
in the above startup script, change wap_supplicant to wpa_supplicant.

if wpasupplicant manually appears to work better for you please produce a log like what is suggested by jasonmartens and attach that. would be curious to see how long it really takes until wpa _knows_ that its associated

Please check out my comment https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/292054/comments/7
to see if everyone else agrees with it.
Thanks

I compared my working wpa_supplicant file with the config that networkmanager generates (according to the log) like suggested in comment 101. There are a lot of differences, but I was able to pinpoint on the "phase2" property. My working wpa_supplicant file looks like this (password changed):

ctrl_interface=/var/run/wpa_supplicant
network={
      ssid="NEWTEC_CORP"
      mode=managed
      proto=WPA
      key_mgmt=WPA-EAP
      auth_alg=OPEN
      pairwise=TKIP
      eap=PEAP
      phase2="auth=EAP-GTC"
      identity="jvb"
      password="mypassword"
}

When I add the phase2 value like networkmanager generates it, it no longer works:

ctrl_interface=/var/run/wpa_supplicant
network={
      ssid="NEWTEC_CORP"
      mode=managed
      proto=WPA
      key_mgmt=WPA-EAP
      auth_alg=OPEN
      pairwise=TKIP
      eap=PEAP
      phase2="auth=EAP-GTC"
      identity="jvb"
      password="mypassword"
      phase2="auth=MSCHAPV2"
}

auth=MD5 doesn't work either.

Attached is the log of wpa_supplicant with the config file that doesn't work (with phase2 parameter)

be careful, you have _two_ phase2 keys in your conf now ;)

Ouch indeed... I guess I was a bit to enthusiastic.

Anyways, leaving out the first phase2 key, and thus only keeping the one from networkmanager, doesn't work either.

ctrl_interface=/var/run/wpa_supplicant
network={
      ssid="NEWTEC_CORP"
      mode=managed
      proto=WPA
      key_mgmt=WPA-EAP
      auth_alg=OPEN
      pairwise=TKIP
      eap=PEAP
      identity="jvb"
      password="mypassword"
      phase2="auth=MSCHAPV2"
}

auth=MD5 doesn't work either.

Leaving out the phase2 key completely also seems to work.

Why does network manager only offer those two possibilities? It seems that I need phase2="auth=EAP-GTC" to get it to work correctly.

Here is my wpa_supplicant log for a manual connection. Unfortunately, it does not have timestamps, but the connection happens almost instantaneously for me ( certainly < 1 second).

I can confirm that in my case at least the following wpa_supplicant conf file works as expected without chnaging anything else other than stopping NetworkManager from running.

ctrl_interface=/var/run/wpa_supplicant
network={
ssid="<essid>"
proto=WPA2
scan_ssid=1
key_mgmt=WPA-EAP
eap=PEAP
identity="domain\user"
password="password"
phase1="peaplabel=0"
}

I get the "disconnecting by local choice (reason=3)" message but on WPA-PSK on a FON router, as other have reported. Very occasionally it will connect but most of the time asks me to re-enter a password.

I have tried using kernel 2.4.24 from hardy as this had the iwl4965 driver, but the results are the same with iwlagn and iwl4965.

However, downgrading to network-manager 0.6.6 from Hardy works flawlessly on either driver, and also associates /quickly/.

I think this is not a kernel issue, not a time out bug, and is not limited to WPA-EAP.

I believe i am suffering from the same bug.
I connect fine to my office WiFi but i loose the connection after 5 or 10 minutes and must reconnect again.
This problem started when i upgraded to Intrepid from Hardy.

It is an Eduroam network
http://www.eduroam.org/

WPA/WPA2, EAP-TTLS, PAP
using driver iwl3945

the problem persists when using the old Hardy 2.6.24 kernel and Intrepid 2.6.27.
The problem persists when using the network-manager PPA mentioned above.

Is their any other info i can submit to help diagnose and solve this bug?

Same here with 2.6.27-7 and iwl3945. I get this error when trying to connect to my wpa-psk or to a completely open wireless network.

But: As soon as i deactivate dhcp and set a static ip & gateway, everything works fine. connection is up. (both the wpa psk and the open one)

I tried this. Setting IP config manually, but it didn't worked.

Workaround: KNetworkManager has an expert settings option in the profile editor. If you play with that, I've seen some success in getting things to connect.

WPA Personal worked fine for me in Hardy, and has ceased to work with the Intrepid upgrade. I tried the PPA repository posted above, but that doesn't make things better.

Kernel: Linux fortrock 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC 2008 i686 GNU/Linux

Wifi chipset: 0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)

Lots of this in dmesg:

[ 193.599589] eth1: associated
[ 203.785117] eth1: disassociating by local choice (reason=3)
[ 207.415441] eth1: authenticate with AP 00:17:9a:f1:06:35
[ 207.417208] eth1: authenticated
[ 207.417218] eth1: associate with AP 00:17:9a:f1:06:35
[ 207.418981] eth1: authenticate with AP 00:17:9a:f1:06:35
[ 207.420705] eth1: authenticated
[ 207.420721] eth1: associate with AP 00:17:9a:f1:06:35
[ 207.423204] eth1: RX ReassocResp from 00:17:9a:f1:06:35 (capab=0x431 status=0 aid=1)
[ 207.423213] eth1: associated
[ 214.097706] eth1: disassociating by local choice (reason=3)

Syslog:

Nov 12 23:54:40 fortrock kernel: [ 138.348143] eth1: authenticated
Nov 12 23:54:40 fortrock kernel: [ 138.348152] eth1: associate with AP 00:17:9a:f1:06:35
Nov 12 23:54:40 fortrock kernel: [ 138.350460] eth1: RX ReassocResp from 00:17:9a:f1:06:35 (capab=0x431 status=0 aid=1)
Nov 12 23:54:40 fortrock kernel: [ 138.350468] eth1: associated
Nov 12 23:54:40 fortrock NetworkManager: <info> (eth1): supplicant connection state change: 3 -> 4
Nov 12 23:54:40 fortrock NetworkManager: <info> (eth1): supplicant connection state change: 4 -> 5
Nov 12 23:54:50 fortrock NetworkManager: <info> (eth1): supplicant connection state change: 5 -> 0
Nov 12 23:54:50 fortrock NetworkManager: <info> (eth1): supplicant connection state change: 0 -> 2
Nov 12 23:54:50 fortrock kernel: [ 148.532151] eth1: disassociating by local choice (reason=3)
Nov 12 23:54:50 fortrock NetworkManager: <info> (eth1): supplicant connection state change: 2 -> 0
Nov 12 23:54:51 fortrock NetworkManager: <info> eth1: link timed out.
Nov 12 23:54:54 fortrock NetworkManager: <info> (eth1): supplicant connection state change: 0 -> 3
Nov 12 23:54:54 fortrock kernel: [ 152.154813] eth1: authenticate with AP 00:17:9a:f1:06:35
Nov 12 23:54:54 fortrock kernel: [ 152.158098] eth1: authenticate with AP 00:17:9a:f1:06:35
Nov 12 23:54:54 fortrock kernel: [ 152.158133] eth1: authenticated
Nov 12 23:54:54 fortrock kernel: [ 152.158136] eth1: associate with AP 00:17:9a:f1:06:35
Nov 12 23:54:54 fortrock NetworkManager: <info> (eth1): supplicant connection state change: 3 -> 4
Nov 12 23:54:54 fortrock kernel: [ 152.164600] eth1: RX ReassocResp from 00:17:9a:f1:06:35 (capab=0x431 status=0 aid=1)
Nov 12 23:54:54 fortrock kernel: [ 152.164607] eth1: associated
Nov 12 23:54:54 fortrock NetworkManager: <info> (eth1): supplicant connection state change: 4 -> 5
Nov 12 23:55:04 fortrock kernel: [ 162.349149] eth1: disassociating by local choice (reason=3)
Nov 12 23:55:04 fortrock NetworkManager: <info> (eth1): supplicant connection state change: 5 -> 0
Nov 12 23:55:04 fortrock NetworkManager: <info> (eth1): supplicant connection state change: 0 -> 2
Nov 12 23:55:04 fortrock NetworkManager: <info> (eth1)...

I tried with wpa supplicant, and was unsuccessful:

network={
      ssid="dedasys"
      key_mgmt=WPA-PSK
      proto=WPA
      psk="not my real super secret phrase"
}

Here are the results with -d enabled:

root@fortrock:~# wpa_supplicant -d -c ./wpa_supplicant.conf -ieth1
Initializing interface 'eth1' conf './wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file './wpa_supplicant.conf' -> '/root/./wpa_supplicant.conf'
Reading configuration file '/root/./wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
Priority group 0
   id=0 ssid='dedasys'
Initializing interface (2) 'eth1'
Interface eth1 set UP - waiting a second for the driver to complete initialization
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1b:77:79:b8:2b
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Added interface eth1
Ignore event for foreign ifindex 3
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
Failed to get scan results
Failed to get scan results - try scanning again
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
EAPOL: disable timer tick
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b19 len=8
Received 1569 bytes of scan results (6 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:19:e0:f8:55:38 ssid='I-Link' wpa_ie_len=26 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
1: 00:17:9a:f1:06:35 ssid='dedasys' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   selected based on WPA IE
   selected WPA AP 00:17:9a:f1:06:35 ssid='dedasys'
Try to find non-WPA AP
Trying to associate with 00:17:9a:f1:06:35 (SSID='dedasys' freq=2437 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using P...

Been informed that using WPA PEAP, try connecting using PEAP v0 instead of v1 - it makes it magically work in some cases [notably, on JHU's Hopkins wireless network].

Odd, but effective.

I have this problem also on my university campus, WPA EAP, we use PEAP and MSCHAPv2 there. It worked fine under hardy, but now under intrepid it works only sometimes... I have to reconnect again and again, till it works, sometimes five minutes, sometimes twenty minutes...

And I use the new iwlagn driver for Intel Wireless 5X00:
03:00.0 Network controller [0280]: Intel Corporation Wireless WiFi Link 5100 [8086:4236]
 Subsystem: Intel Corporation Device [8086:1011]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 2296
 Region 0: Memory at db100000 (64-bit, non-prefetchable) [size=8K]
 Capabilities: <access denied>
 Kernel driver in use: iwlagn
 Kernel modules: iwlagn

I've attached a part of syslog when it happens....

Updated snap-shot worked great for me! Just need to use PEAP v 0

Same here, using intel ipw2915, on hardy it worked perfectly.
Network manager refuses to connect to WPA Enterprise with TKIP and PEAP.
Using a script to deactivate network manager and connect directly via wpa_suplicant works fine.

This was affecting me but after updating to the networkmanager as posted by Alexander it appears resolved. I run a Lenovo T61 with an Atheros AR5212 (IBM device 058a) and my association was timing out to an AP with WPA-Personal ( PSK ) enabled. Thanks Alexander !!!

Is there any progress on the Enterprise aspects of this bug? It seems that NM is trying too hard and specifying more parameters than are required in most cases by wpa_supplicant. Some method of not specifying the phase2 authentication options would be very interesting to see as, at least in my case, wpa_supplicant authenticates perfectly (and quickly) without these options. I'm sure they were added with the best of intentions to support those people that need to specify them but a way of skipping that phase would be good.

For accessing my work network I've now resorted to a script to stop NM, unload and reload the iwlagn driver, start wpa_supplicant and then run dhclient after authentication completes. The entire script execution takes about as long as a single rotation of the connect animation in nm-applet.

Thanks,

Mark.

On Thu, 20 Nov 2008, MarkS wrote:

> quickly) without these options. I'm sure they were added with the best
> of intentions to support those people that need to specify them but a
> way of skipping that phase would be good.

I could set it to None, to no avail.

--
Matthias Andree

Hi,

I had installed Kubuntu 8.10 and was not able to connect to our wireless router which has WPA2-PSK security configuration.

My computer was disconnecting by printing the following debug message:
wlan0: disassociating from by local choice (reason=3)

After installing package
(i386): https://edge.launchpad.net/%7Enetwork-manager/+archive/+files/network-manager-gnome_0.7~~svn20081020t000444-0ubuntu1~nm1_i386.deb

Suggested by Alexander Sack (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/272185/comments/56) I was able to connect.

It may be a dbus problem because "wpa_supplicant -u" fails to connect to dbus, and if it is automatically launched by network-manager, wpa_cli or wpa_gui cannot connect to the supplicant.

I'm using network-manager version 0.7~~svn200810, and I was able to successfully connect to a WPA 2 network today that I could not before. I'll keep my eye on it, but it appears that this problem has been resolved for me.

One additional note, I did change my PEAP version from 1 to 0. Not sure if that's what fixed it, but it's worth trying if you are having trouble connecting to WPA2 networks.

I've something also interesting: on a full patched fresh intrepid
install, I can connect on WPA2 using TTLS and PAP the first time. But
when I disconnect and reconnect using the network applet, it doesn't
work anymore.

--
"Trouble-a-cat limited"

the timeout tuning fix that seems to fix a few cases is now targetted against bug 292054 ... for which the SRU will happen now.

How can i change my PEAP version from 1 to 0.

You change in on the "Wireless Security" tab for the network you are trying to connect to. It's a drop down called "PEAP Version" and the options are "Version 0" or "Version 1".

Using the recent updates from intrepid-proposed the problem seems to be getting even worse.

The packages are
network-manager-gnome version 0.7~~svn20081020t000444-0ubuntu1.8.10.1
network-manager version 0.7~~svn20081018t105859-0ubuntu1.8.10.1

It is an Eduroam network
http://www.eduroam.org/

WPA/WPA2, EAP-TTLS, PAP
using driver iwl3945

Niall, what do you mean by "worse"?

By worse I mean that Network Manager looses the connection more frequently.

Seems to happen most when i use the network intermittently, for example, using IM software, or when browsing the web.
I lost connection 2 times while composing this message.

when the computer is left idle it seems to loose connection less frequently, (or maybe i just dont notice)
when it is left streaming internet radio, it seems to loose connection less frequently also, maybe only once every 20 or 30 mins.

If there is any more information i can give you to help diagnose this problem (or show that its the wifis problem) please tell me. although I will be away from this network for the next 3 weeks.

I'm not sure it's the good place to ask but: is it a way to increase
verbose from wpa_supplicant when used by network manager ? I have the
same problem and I will be happy to help with log and some experiments
;-)

Julien.

On Thu, Dec 4, 2008 at 4:37 PM, Niall Murphy <email address hidden> wrote:
> By worse I mean that Network Manager looses the connection more
> frequently.
>
> Seems to happen most when i use the network intermittently, for example, using IM software, or when browsing the web.
> I lost connection 2 times while composing this message.
>
> when the computer is left idle it seems to loose connection less frequently, (or maybe i just dont notice)
> when it is left streaming internet radio, it seems to loose connection less frequently also, maybe only once every 20 or 30 mins.
>
> If there is any more information i can give you to help diagnose this
> problem (or show that its the wifis problem) please tell me. although I
> will be away from this network for the next 3 weeks.
>
> --
> [Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP (Enterprise) network (disassociating by local choice (reason=3) )
> https://bugs.launchpad.net/bugs/272185
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
"Trouble-a-cat limited"

I think that the following command:

 sudo kill -SIGUSR1 `pidof wpa_supplicant`

Should turn on debugging until you restart.

To make it permenant then you need to change the line in the file
/usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service

from:
Exec=/sbin/wpa_supplicant -u -f /var/log/wpa_supplicant.log

to:
Exec=/sbin/wpa_supplicant -dddt -u -f /var/log/wpa_supplicant.log

Then run

 sudo killall wpa_supplicant

Note for the above:

This is going save a lot of possibly secret info into /var/log/wpa_supplicant.log so after you have finished debugging you probably want to remove that file and also think twice before just posting it online if you value the info in it.

Still not working for me ... WPA/WPA 2 Personal, not Enterprise. Intrepid, uniquely, does not work. The logs are filled with the following:

Dec 10 10:30:58 noel-intrepid kernel: [ 1277.187007] wlan0: authenticate with AP 00:15:c7:82:02:70
Dec 10 10:30:58 noel-intrepid kernel: [ 1277.190341] wlan0: authenticated
Dec 10 10:30:58 noel-intrepid kernel: [ 1277.190356] wlan0: associate with AP 00:15:c7:82:02:70
Dec 10 10:30:58 noel-intrepid kernel: [ 1277.389109] wlan0: associate with AP 00:15:c7:82:02:70
Dec 10 10:30:58 noel-intrepid kernel: [ 1277.390836] wlan0: deauthenticated

over and over and over again. After each failure I am prompted for the password. It is a simple text string, I type it in the entry field with "Show Password" enabled so that I can be sure there are no typos.

ii network-manager 0.7~~svn20081018t105859-0ubuntu1.8.10.1
ii network-manager-gnome 0.7~~svn20081020t000444-0ubuntu1.8.10.1
ii wpasupplicant 0.6.4-2

I tried several experiments, and I think the following comments would be useful:

First, I think several different bugs are present in this bug report.
Some people can resolve their problem with the laster network manager
(from PPA), but it's not working with me.

Second, I am trying to connect to eduroam access, which is the same
problem as some people here.

This is not a wpa_supplicant or driver problem, as I can connect with
my own script. I attach the scripts I have used to connect to my
eduroma point. Can other people with problem with eduroam can try it ?

(Note: please modify your interface in start/stop_fac and the fields
identity, password and ca_cert in wpa_supplicant.conf.)

Julien.

On Wed, Dec 10, 2008 at 4:39 PM, Noel J. Bergman <email address hidden> wrote:
> Still not working for me ... WPA/WPA 2 Personal, not Enterprise.
> Intrepid, uniquely, does not work. The logs are filled with the
> following:
>
> Dec 10 10:30:58 noel-intrepid kernel: [ 1277.187007] wlan0: authenticate with AP 00:15:c7:82:02:70
> Dec 10 10:30:58 noel-intrepid kernel: [ 1277.190341] wlan0: authenticated
> Dec 10 10:30:58 noel-intrepid kernel: [ 1277.190356] wlan0: associate with AP 00:15:c7:82:02:70
> Dec 10 10:30:58 noel-intrepid kernel: [ 1277.389109] wlan0: associate with AP 00:15:c7:82:02:70
> Dec 10 10:30:58 noel-intrepid kernel: [ 1277.390836] wlan0: deauthenticated
>
> over and over and over again. After each failure I am prompted for the
> password. It is a simple text string, I type it in the entry field with
> "Show Password" enabled so that I can be sure there are no typos.
>
> ii network-manager 0.7~~svn20081018t105859-0ubuntu1.8.10.1
> ii network-manager-gnome 0.7~~svn20081020t000444-0ubuntu1.8.10.1
> ii wpasupplicant 0.6.4-2
>
> --
> [Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP (Enterprise) network (disassociating by local choice (reason=3) )
> https://bugs.launchpad.net/bugs/272185
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
"Trouble-a-cat limited"

Kartoch

I tried your eduroam scripts and configs[1] and with only a couple of tweaks it works great.

I had to drop the -Dwext from the wpa_supplicant line in the script.
I also had to change the pap setting to PEAP from TTLS.

Thanks

[1]https://bugs.launchpad.net/ubuntu/+source/linux/+bug/272185/comments/163

An idea: if wpa_supplicant is ok and parameter of network manager is
correct, I think the bug(s) could be how parameters are transmit by
network manager. How network manager communicate the connection
parameters to wpa_supplicant ? I think it used DBUS (as wpa_supplicant
uses the "-u" parameter) but I don't see these parameters using
dbus_monitor...

Julien.

--
"Trouble-a-cat limited"

Please stop adding random "me too"; "this and that" or whatever comments to
the bug report... it's an order of magnitude too large anyways already,
and I have seen few comments add new information. They are more or less
just IRRELEVANT(!) variants of comments already here.

--
Matthias Andree

hello,

I am guessing this isn't resolved yet. My experience is as follows.
Hardware => Gateway M280, intel pro 2200
Connecting to Eduroam => WPA-EAP, TKIP, PEAP, MSCHAPV2 (Uni of York)

NM just doesn't work. I have been attempting off and on for the past month now and it hasn't connected once. I just tried the PPA updates and that didn't work either. Same result, just takes a little longer. Manually starting wpa_supplicant works, but intermittently. A successfull connection, if established, occurs within apprx 2 seconds.

wpa_supplicant.conf :

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="eduroam"
# scan_ssid=1
proto=WPA
key_mgmt=WPA-EAP
pairwise=TKIP
group=TKIP
eap=PEAP MSCHAPV2
identity="xxx"
password="xxx"
# ca_cert="/etc/ssl/certs/ca.pem"
# ca_cert2="/etc/ssl/certs/ca.pem"
# phase1="peaplabel=0"
phase2="auth=MSCHAPV2"
# eapol_flags=0
}

After stopping NM, I connect using :
sudo wpa_cli -i eth1 terminate; sudo wpa_supplicant -i eth1 -dd -B -D wext -c /etc/wpa_supplicant/wpa_supplicant.conf -f /var/log/wpa_supplicant.log

and keep repeating this untill I get a connection - on average once out of 10 attempts.

I have lots of logs for successull and failed attempts. Attaching 2 samples each (with some bits removed)

What I have noticed is that it always get to the phase 2 (MSCHAPV2 succeeds). When the connection fails, the machine seems to repeatedly receive the same packet during the 4-way handshake (Pairwise Install ACK MIC). At other times, it just magically receives the next packet as well. Something wrong with key sync maybe?

Sitting right next to the wireless hub didn't help.

any experiments you want done, just lemme know... I am desperate to get this working. extremely frustrated.

Thanks
Omer

This bug was found in the Intrepid development cycle; removing regression-potential and marking as regression-release.

Ok guyz... this seems like one of those long hauls. In the meantime, I was thinking about rolling back some of the packages to Hardy. NM is probably not it, since i get the problem with command line WPA supplicant as well. Any suggestions? Or should I start the hit and trial method?

Apologies for coming out a little impatient, but I really need a stable network connection.
Thanks
Omer

Niall Murphy wrote:
> I believe i am suffering from the same bug.
> I connect fine to my office WiFi but i loose the connection after 5 or 10 minutes and must reconnect again.
> This problem started when i upgraded to Intrepid from Hardy.
>
>
Is that a A, G or N network where you loose your conneciton?

Omer wrote:
> Ok guyz... this seems like one of those long hauls. In the meantime, I
> was thinking about rolling back some of the packages to Hardy. NM is
> probably not it, since i get the problem with command line WPA
> supplicant as well. Any suggestions? Or should I start the hit and trial
> method?
>
> Apologies for coming out a little impatient, but I really need a stable network connection.
> Thanks
> Omer
>
>
If you do that, please dont post about this in bugs. thanks!

Hello, I'm having an issue that (should) be the same.
When I try to connect to a WPA network the wpa_supplicant.log is:
CTRL-EVENT-SCAN-RESULTS
No network configuration found for the current AP
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
No network configuration found for the current AP
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
No network configuration found for the current AP
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
No network configuration found for the current AP
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
No network configuration found for the current AP
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
No network configuration found for the current AP
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
No network configuration found for the current AP
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
No network configuration found for the current AP
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
No network configuration found for the current AP
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

The password I have works in Windows XP (reception is 82%->95%). Other kinds of wireless connections work (unprotected/WEP/...). My hardware is:
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)

I'm running Ubuntu 8.10.

Cheers,

This simple workaround has been helping with wpa enterprise with tkip that worked in hardy but not in Intrepid.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263963/comments/89

Using gconf-editor to remove the ccmp entries worked for me too. :)

http://ubuntuforums.org/showthread.php?t=1010650

This is the first time I've been able to connect to wpa enterprise with tkip in Intrepid :)

On all the notebooks I've tried wpa enterprise with tkip was working perfectly under Hardy but failed under Intrepid.

First off - this bug is *not* invalid. Don't know why it is marked as such. At any rate I think I've got a simple solution. It's off the wall, but it works on a variety of chipsets (atheros, ipw2200...).

## WARNING: Following these instructions may break your Intrepid installation. They worked great for me on a variety of laptops, but your mileage may vary. Proceed at your own risk. ###

The problem is with how wpa_supplicant and network manager interact. Updating the relevant packages to their jaunty equivalents fixes the problem. Here's the procedure:

0. Run a standard update to make sure you have all relevant Intrepid updates.

1. Add the jaunty repositories to /etc/apt/sources.list. Using your favorite text editor (ex. gksudo gedit /etc/apt/sources.list), add the following lines (we will remove these when all is said and done.)
# Jaunty Sources
deb http://us.archive.ubuntu.com/ubuntu jaunty main restricted
deb-src http://us.archive.ubuntu.com/ubuntu jaunty main restricted

2. Update your sources list by running the following command: sudo apt-get update

** A zillion new updates will show up. Do not run any automatic updaters! Doing so may break your installation. **

3. Open the synaptic package manager (System --> Administration --> Synaptic Package Manager). Search for and upgrade the packages listed below:
* wpasupplicant
* libnm-glib0
* libnm-util0
* libxcb-render-util0
* network-manager
* network-manager-gnome

After you finish - Ubuntu will tell you to restart. Don't restart yet.

4. Go back and remove the lines from step one (1) from your /etc/apt/sources.list. Once the lines are removed -- save the file. After that, do another sudo apt-get update to remove the jaunty sources. Any automatic updaters should go back to normal and say that no updates are available.

5. Now restart your computer. It should all work after that. You may have to delete your existing (broken) associations in order for it to work right.

Tested to work on several atheros chipsets and several Intel chipsets. Special thanks to the College of William and Mary for providing the test equipment.

I hope it works out for you!

Dan

I used the workaround hinted by Dan Bracey. It worked perfectly on a Dell E6400 with Intel 5300 WiFi. I fixed my previous problems connecting to a WPA2 Enterprise access point using PEAP/MSCHAPv2.

I am running kubuntu, however, I was using nm-applet instead of knetworkmanager to connect to the network. Thus, I would expect that ubuntu would behave identical on the same hardware.

In addition to the suggestions made by Dan, I also upgraded knetworkmanager and network-manager-kde, hoping that the KDE-native knetworkmanager would be able to connect as well. Unfortunately, it still fails. Are there any additional KDE libraries that need to be upgraded, or is ubuntu just ahead of kubuntu when it comes to WiFi on jaunty?

Glad to hear it worked for you hasi. I can test the stuff again with KUbuntu on Monday. I'll report back.

Dan

Unfortunately Dan's fix (using the Jaunty networking packages in Intrepid) does not work for me. My laptop is a Lenovo X200s with a 5100 AGN adapter, using iwlagn. My university network uses WPA2, PEAP (ver 0), MS-CHAP2. I have always had erratic connections using Intrepid --- sometimes the laptop connected, sometimes it didn't and I would keep getting the certificate dialog. That pattern persists with the Jaunty packages. Just now I had a connection, I took the laptop to a new location and it refused to connect. The probability of making a connection may be a little higher, but it's hard to tell and it is still not reliable.

Let me ask a question that would help in debugging: Is there any way to force network-manager to try to connect wirelessly? Sometimes wireless is activated (wlan0 is up) and I am in range of a node, but the "wireless network" selection is grayed out in the NM dialog box (from the panel) and I am don't know how to force NM to try to connect. Restarting NM doesn't help. Any thoughts about what to do? Maybe I'm missing something obvious. Thanks.

As far as KDE goes, I couldn't get that to work right using the latest KUbuntu. There were some knetworking packages that I could have updated, but those depended on a lot of other packages. I didn't want to get Jaunty stuff and Intrepid stuff too intertwined, so I left it alone...

It's interesting that it doesn't work for you rmcd -- as we are using the same setup for the server side (WPA2, PEAPv0 and MSCHAPv2.) Are you sure you are using the correct certificate? I would try it without providing a certificate file in the gui. To clear out any certificate files that might be listed, you have to network manager and delete the encrypted wireless association.

If that still doesn't work -- I suspect its a driver issue...

Dan

Oh I forgot to mention -- if you are required to provide a certificate, it must be an *.pem file in /etc/ssl/certs. Make sure you update your certificate cache (see directions earlier in this thread.)

Dan

Following posted directions for Windows (http://www.it.northwestern.edu/oncampus/wireless/wireless-connections/wireless-win.html), wireless is 802.1x/WPA2, PEAP, MSCHAPv2. I figured out PEAPv0 while getting wpa_supplicant to work under Puppy Linux (it worked flawlessly, but on a different laptop, so the driver and networking hardware may be an issue). I've never had to deal with certificates in Ubuntu at the times when the connection worked. When it doesn't work, I am presented with the dialog box asking for a certificate. I don't believe I'm supposed to need a certificate. Under Windows, the procedure is that I am asked to authenticate myself with a password and then I'm connected. (Actually, even Windows sometimes has trouble connecting. I have found Lenovo's Access Connections to work reliably as does wpa_supplicant in Puppy Linux.)

I'm not a networking guru and I'm not a Ubuntu expert so I may miss something. The important thing from my perspective is that some of the time the wireless connection just works, and it works for hours, and it reconnects if I click on the GUI. Other times it will not connect no matter what I try.

It would help if you attached your /var/log/wpa_supplicant.log file to this bug report. Try and get connected a few times and then also see if you can get a few failures in there. If you have intermittent connections -- it really sounds like a driver thing (or a thing on northwestern's end.)

From the link you posted, it doesnt look like you need a cert. It might be worth trying PEAPv1 -- just to see if it works.

Dan

Network-manager still does not connect. With a connection set up as described above (wpa2, peapv0, mschapv2) I still get the dialog box asking if I want to select a certificate, followed by no connection. The log (/var/log/wpa_supplicant.log) contains an endless string of the following:

CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

etc.

However, I am now able to connect using wpa_supplicant. I run this on the command line:

sudo wpa_supplicant -c wpa_supplicant_nu.conf -d -iwlan0 -Dwext -B

once it connects I run dhclient3

Here is the config file wpa_supplicant_nu.conf

ctrl_interface=/var/run/wpa_supplicant
update_config=1

network={
 ssid="Northwestern"
 scan_ssid=1
 proto=WPA2
 key_mgmt=WPA-EAP
 pairwise=CCMP TKIP
       group=CCMP TKIP
 eap=PEAP
 identity="myidentity"
 password="xxxxx"
 phase1="peaplabel=0"
 phase2="auth=MSCHAPV2"
}

So given this result I am guessing that this is *not* a driver problem and that there is still some error in the way that network-manager is interacting with wpa_supplicant.

It could still be a driver issue -- as you manually specified the wext driver in that command...

Out of curiosity, what version of network manager are you running? Maybe the jaunty sources got updated (and re-broken)? Get the exact version # from synaptic (should be kinda weird with some ~~ things).

Dan

NM version is 0.7~~svn20081018t105859-0ubuntu2

Good point about the driver. If I try to specify iwlagn wpa_supplicant doesn't know what that is.

One more weird thing to mention. I can use wpa_supplicant manually to connect right after rebooting. If I bring down wlan0 and then try to reconnect, it seems to work once or twice and then I can't reconnect without rebooting. Each time I am deleting /var/run/wpa_supplicant/* . I don't know networking well enough to understand what rebooting changes.

Try running wpa_supplicant again without the -D setting eg:

sudo wpa_supplicant -c wpa_supplicant_nu.conf -d -iwlan0 -B

Can you get the versions of all the packages in my initial post?

Thanks

Dan

Based on two tries -Dwext seems to be necessary.

Here are the versions from aptitude show:

wpasupplicant 0.6.6-2
libnm-glib0 0.7~~svn20081018t105859-0ubuntu2
libnm-util0 0.7~~svn20081018t105859-0ubuntu2
libxcb-render-util0 0.2.1+git1-1
network-manager 0.7~~svn20081018t105859-0ubuntu2
network-manager-gnome 0.7~~svn20081020t000444-0ubuntu2

Those packages are ok.... I'm officially out of ideas ... :-/

On Tue, Jan 13, 2009 at 7:29 PM, Dan Bracey <email address hidden> wrote:

> Those packages are ok.... I'm officially out of ideas ... :-/
>
>

Is there a way to tell network-manager to use a different wireless driver?
(Since wext seems to work, at least some of the time.)

Sure, I didnt think that about that... Try adding this line to /etc/network/interfaces:

wpa-driver wext

You need to be root to edit that file. Ex. gksudo gedit /etc/network/interfaces. You'll probably need to reboot after editing the file.

Dan

Unfortunately changing the driver isn't the answer. And despite my initial
flurry of success, wpa_supplicant on the command line isn't the answer
either. It may connect with a slightly higher probability, but most of the
time I don't connect however I try.

On Tue, Jan 13, 2009 at 10:31 PM, Dan Bracey <email address hidden> wrote:

> Sure, I didnt think that about that... Try adding this line to
> /etc/network/interfaces:
>
> wpa-driver wext
>
> You need to be root to edit that file. Ex. gksudo gedit
> /etc/network/interfaces. You'll probably need to reboot after editing
> the file.
>
> Dan
>
> --
> [Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA
> EAP (Enterprise) network (disassociating by local choice (reason=3) )
> https://bugs.launchpad.net/bugs/272185
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "knetworkmanager" source package in Ubuntu: Invalid
> Status in "linux" source package in Ubuntu: Invalid
> Status in "network-manager" source package in Ubuntu: Triaged
> Status in "network-manager-applet" source package in Ubuntu: Fix Released
> Status in "network-manager-openvpn" source package in Ubuntu: Triaged
> Status in "wpasupplicant" source package in Ubuntu: Triaged
> Status in knetworkmanager in Ubuntu Intrepid: New
> Status in linux in Ubuntu Intrepid: Triaged
> Status in network-manager in Ubuntu Intrepid: Triaged
> Status in network-manager-applet in Ubuntu Intrepid: Fix Released
> Status in network-manager-openvpn in Ubuntu Intrepid: Triaged
> Status in wpasupplicant in Ubuntu Intrepid: Triaged
>
> Bug description:
> Proposed fix-packages:
> https://edge.launchpad.net/~network-manager/+archive<https://edge.launchpad.net/%7Enetwork-manager/+archive>
>
> Binary package hint: network-manager
>
> I'm having troubles connecting to my campus wireless network with Intrepid
> Ibex (updated 19 Sept 2008). I have a Dell XPS m1330 laptop with ipw3945
> card. This laptop connects fine under Ubuntu 8.04.
>
> Here are the setting my campus suggests I use.
>
> SSID: uconnect.utah.edu
> Encryption: WPA Enterprise
> Encryption Type or Key: TKIP
> EAP Method: PEAP
> CA Server Certificate: Entrust.net (do not need to enter under Network
> Manager under Ubuntu 8.04)
> Authentication Method: MS-CHAP v2
> Username: *****
> Password: *****
>

Dan asked earlier for a log of a successful connection. Here are both (these are using the default driver, which I believe is iwlagn). Successful connections remain sporadic.

Successful:

CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:11:92:3e:79:80 (SSID='Northwestern' freq=2447 MHz)
Associated with 00:11:92:3e:79:80
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
OpenSSL: tls_connection_handshake - Failed to read possible Application Data error:00000000:lib(0):func(0):reason(0)
EAP-MSCHAPV2: Authentication succeeded
EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed
CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
WPA: Key negotiation completed with 00:11:92:3e:79:80 [PTK=CCMP GTK=CCMP]
CTRL-EVENT-CONNECTED - Connection to 00:11:92:3e:79:80 completed (auth) [id=3 id_str=]
CTRL-EVENT-SCAN-RESULTS
WPA: Group rekeying completed with 00:11:92:3e:79:80 [GTK=CCMP]
CTRL-EVENT-SCAN-RESULTS
WPA: Group rekeying completed with 00:11:92:3e:79:80 [GTK=CCMP]
CTRL-EVENT-SCAN-RESULTS
WPA: Group rekeying completed with 00:11:92:3e:79:80 [GTK=CCMP]
CTRL-EVENT-SCAN-RESULTS
etc.

Unsuccessful:

CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:11:92:3e:79:80 (SSID='Northwestern' freq=2447 MHz)
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Authentication with 00:00:00:00:00:00 timed out.

I think I'm also affected by this bug.
I'm running Ubuntu 8.10 with all repositories enabled (means I run kernel 2.6.27-11-generic (uname -r)).
>lspci |grep 3945
02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)

At home, I can connect to my WPA Personal network.
On the university, I have a WPA2 Enterprise/TTLS/PAP authentication. Here, I often cannot connect. If, after several retries, I'm connected, the connection drops in no time: sometimes after 10 seconds, sometimes after some minutes.

I noticed that after uninstalling the package linux-backports-modules-intrepid, the connection success rate raised a little bit (so I needed less retries before I am connected). However, this is still not usable.

Ernst -- did you try my fix?

Dan

Yes, I tried installing the jaunty packages. After updating my repositories, updating and selecting the packages, Synaptic forced me to install some other (dependent) packages. However, it did not solve my problems with WPA2/TTLS/PAP; I still had trouble connecting and took a lot of tries before it was connected.

After that, I did encounter a new problem: I occasionally got a "Authentication with 00:00:00:00:00:00 timed out." message in my wpa_supplicant log, resulting in a long reconnect time to a 'regular' WPA access point. Before the Jaunty packages, I never had problems with this access point (no reconnects or whatever).

I think I solved the time-out problem by running 'sudo aptitude reinstall'. At first, it gave errors, because there was no installation candidate for some of the packages (they only exist in jaunty?). After downgrading those packages (a solution offered by aptitude after trying to remove those packages) and reinstalling all packages again, I think I restored my system to the state before the jaunty packages.

Thanks for your help! Hopefully, my report helps to solve this bug

Hey so first thing, I also tried installing the packages from the Jaunty repo that were suggested but that didn't help at all. Mine is a WPA PEAP wireless lan. I can connect instantly with wpa_supplicant but not with network manager.

my wpa_supplicant.conf looks like this (I've tried to remove everything that isn't absolutely necessary):

ctrl_interface=/var/run/wpa_supplicant
network={
 ssid="WLAN-TWDC"
 proto=WPA
 key_mgmt=WPA-EAP
 eap=PEAP
 identity="xxx"
 password="xxx"
 phase1="peaplabel=0"
# phase2="auth=MSCHAPV2"
}

I think the problem I'm seeing is pretty much exactly what Jan above described (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/272185/comments/131). Including the phase2 line prevents me from connecting, but when I leave it out I connect pretty much instantly.

I'm attaching the wpa_supplicant output from a failed connection. It seems the problems are happening around line 389. I'll also attach a successful one just for the heck of it.

Here's a successful connection

I seem to be able to connect if, using the CLI, I issue the command "iwconfig wlan0 essid northwestern". Is it apparent to anyone why this command would help NM connect?

I'm not sure the sequence matters, but if NM fails to connect automatically, (I keep getting the certificate dialog), I click
"cancel" on the dialog and run the iwconfig command. Sometimes it then connects automatically, other times I need to click on the NM icon for the connection, after which it connects. If I issue the command before I get the certificate dialog, it just connects. So far I have had no failures with this method, but I am reluctant to claim victory. I hope that others still having problems can try this out.

My previous reports are around here:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/272185/comments/182

Please let me know if there's something I can try to help pin down what's going on.

Here is a successful connection:

CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:15:f9:47:24:70 (SSID='Northwestern' freq=2462 MHz)
CTRL-EVENT-SCAN-RESULTS
Associated with 00:15:f9:47:24:70
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
OpenSSL: tls_connection_handshake - Failed to read possible Application Data error:00000000:lib(0):func(0):reason(0)
EAP-MSCHAPV2: Authentication succeeded
EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed
CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
WPA: Key negotiation completed with 00:15:f9:47:24:70 [PTK=CCMP GTK=CCMP]
CTRL-EVENT-CONNECTED - Connection to 00:15:f9:47:24:70 completed (auth) [id=0 id_str=]
CTRL-EVENT-SCAN-RESULTS
WPA: Group rekeying completed with 00:15:f9:47:24:70 [GTK=CCMP]

hey, had the same issue that chris walkelin describes at comment #79 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/272185/comments/79 ) while connection to the wireless network at my university (also using eduroam)
i'm not using ubuntu, but it seems that is the same error.

using archlinux 2.6.28
first i tried to connect via network-manager 0.7, but it keeps asking for password.
checked the loaded modules for my usb-wlan-stick (linksys WUSB54GC) and it was rt73usb.

so i blacklisted that module and loaded the linksys with ndiswrapper and windows-drivers from the linksys-homepage.

--> result: works perfectly with that configuration. (connection over nm-applet takes a bit longer, but then connection is stable and fast)

maybe that information can help you solving that problem.

Thanks for the suggestion, but I'm pretty sure what I'm seeing is this
bug in Network Manager:
http://bugzilla.gnome.org/show_bug.cgi?id=565065

Uri

On Mon, Mar 2, 2009 at 4:34 AM, LHM <email address hidden> wrote:
> hey, had the same issue that chris walkelin describes at comment #79 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/272185/comments/79 ) while connection to the wireless network at my university (also using eduroam)
> i'm not using ubuntu, but it seems that is the same error.
>
> using archlinux 2.6.28
> first i tried to connect via network-manager 0.7, but it keeps asking for password.
> checked the loaded modules for my usb-wlan-stick (linksys WUSB54GC) and it was rt73usb.
>
> so i blacklisted that module and loaded the linksys with ndiswrapper and
> windows-drivers from the linksys-homepage.
>
> --> result: works perfectly with that configuration. (connection over
> nm-applet takes a bit longer, but then connection is stable and fast)
>
> maybe that information can help you solving that problem.
>
> --
> [Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP (Enterprise) network (disassociating by local choice (reason=3) )
> https://bugs.launchpad.net/bugs/272185
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I'm in aup-to-date Jaunty Alpha 6 and i'm experiencing this on multiple machines (32-bit and 64-bit), across multiple networks WPA and WPA 2 personal.

Danny, have you tried my suggestion to run in a terminal "iwconfig wlan0 essid ssid_name"? (substitute for wlan0 and ssid_name as appropriate). I have no idea why this works, but I have had a 100% connection success rate over the last 6 weeks. I find it works either a) to issue the command once NM starts trying to connect, or b) to issue it after the WPA2 password dialog pops up. If (b), I sometimes have to click on the NM icon and then click on the particular connection I'm trying to make. But I have been connecting daily with no failures since I first discovered this workaround.

If a networking guru has any clue why this might work, I would love to hear an explanation.

Danny, you might also want to check out bug #347572: iwl3945 unable to connect to WPA personal without linux-backports-modules being installed

Having updated to Janty Beta this morning, things appear much improved. The connection disconnects but reconnects itself without intervention. Running NetworkManager with --no-daemon I see the following errors listed, not sure if these relate to all the disconnects but are probably at least some of them.

NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
NetworkManager: <info> (wlan0): device state change: 8 -> 3
NetworkManager: <info> (wlan0): deactivating device (reason: 0).
NetworkManager: <info> wlan0: canceled DHCP transaction, dhcp client pid 19201
NetworkManager: <info> (wlan0): removing resolv.conf from /sbin/resolvconf
-- Error received: Numerical result out of range
-- Original message: type=0x19 length=56 flags=<REQUEST,ACK> sequence-nr=1238157499 pid=4204341
NetworkManager: <WARN> check_one_route(): (wlan0) error -34 returned from rtnl_route_del(): Sucess

NetworkManager: <info> Activation (wlan0) starting connection '<ESSID>'

I don't see any similar issues if I use wpa_supplicant and dhclient directly.

What is the status on this bug? I was suffering from this problem on Intrepid for quite long time, but now using the kernel "2.6.27-11-generic" and the iwl3495 from compat wireless (http://linuxwireless.org/en/users/Download) dated of 2009-03-31 I do not have any problem.

I am now connected in my university WLAN which uses WPA2 (TTLS + PAP) using the NetworkManager.

If I reboot (sometimes a few times) or log out (also a few times) it will reconnect on my Updated Beta jaunty on my asus 1000HE.

At the moment, on Jaunty 32-bit, all repo's enabled, I can connect on every place at my university. However, after 15 minutes or so, the connection is dropped and I have to manually select the wireless network again.

Using wpa_supplicant, everything works fine.

Can anyone reproduce this using the latest Karmic? Network Manager in Karmic is substantially improved from Jaunty and earlier.

Indeed, my severe problems with connecting to WPA2-PEAP (MSChapV2) went completely away with the newer Karmic versions. (Intel 5300 WiFi card here, 32bit OS.)

I can't test anymore. I am no longer working at the company that had it.

On Mon, Oct 5, 2009 at 3:29 PM, hasi <email address hidden> wrote:

> Indeed, my severe problems with connecting to WPA2-PEAP (MSChapV2) went
> completely away with the newer Karmic versions. (Intel 5300 WiFi card
> here, 32bit OS.)
>
> --
> [Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA
> EAP (Enterprise) network (disassociating by local choice (reason=3) )
> https://bugs.launchpad.net/bugs/272185
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Jeffery Rash

I face this problem after upgrading to Karmic today. ATM I've no idea if it's kernel or network-manager caused, but my wifi-commection is flapping constantly and the only error I see is: "disassociating by local choice (reason=3)"
btw: I'm using a BCM4318 with the b43 driver.

This bug is not about issues with OpenVPN.