Arch Linux

jwhendy

Member

Registered: 2010-04-01

Posts: 621

Wicd stopped connecting to company WPA2 network

I've changed nothing in my setup, yet my computer has recently behaved oddly in two ways:
-- I can no longer connect to my WPA2 network via the same wicd settings
-- This afternoon after having internet on Win7 during an all-day class, I rebooted into Arch and wicd-client couldn't see any networks at all (no matter how many refreshes/disconnect alls)

I'll let the second issue go for now. I just want to know what happened with connecting. My settings have remained the same in terms of user/password, and the encryption type has been PEAP-GTC.

In looking through some other threads, it seems that the suggestion has been to go manually via wpa_supplicant to figure out the exact problem. I've not been able to do this yet. Here's my attempt at a config:

nnetwork={
   ssid="NetworkName"
   key_mgmt=WPA-EAP
   eap=PEAP
   identity="DOMAIN\username"
   password="password"
   phase2="auth=GTC"
}

This fails with:

Trying to associate with 00:15:c6:29:01:50 (SSID='NetworkName' freq=2412 MHz)
Associated with 00:15:c6:29:01:50
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
SSL: SSL3 alert: read (remote end reported an error):fatal:bad certificate
OpenSSL: openssl_handshake - SSL_connect error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
CTRL-EVENT-EAP-FAILURE EAP authentication failed
Authentication with 00:15:c6:29:01:50 timed out.

My computer is usually docked, which delayed me realizing the problem. The last time I see a successful wireless connection in my wicd log files is March 18th (~2 weeks ago).

Any suggestions?

---

Edit: If it's of help, here's the output of =sudo iwlist wlan0 scan=. As stated above, typically I've been using wicd set on PEAP-GTC for the encryption protocol... I'm not familiar enough with protocols to know if that matches up with the below or not.

wlan0     Scan completed :
          Cell 01 - Address: 00:15:C6:29:01:50
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=56/70  Signal level=-54 dBm  
                    Encryption key:on
                    ESSID:"NetworkName"
                    Bit Rates:11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=000000636dcf00ed
                    Extra: Last beacon: 13ms ago
                    IE: Unknown: 000C476C6F62616C536563757265
                    IE: Unknown: 01071698243048606C
                    IE: Unknown: 030101
                    IE: Unknown: 0706555320010B1E
                    IE: Unknown: 0B050000028D5B
                    IE: Unknown: 2A0100
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : 802.1x
                    IE: Unknown: 851E04008F000F00FF03590075732D7761702D6D6E2D7374702D620000000025
                    IE: Unknown: 9606004096001D00
                    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
                    IE: Unknown: DD06004096010104
                    IE: Unknown: DD050040960305
                    IE: Unknown: DD050040960B09
                    IE: Unknown: DD050040961401

Also, I found wicd's repo of configs used and diffed all of the ones that had an edited date in March 2012 (there were 5). They were all the same:

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
network={
	ssid="NetworkName"
	proto=RSN
	key_mgmt=WPA-EAP
	pairwise=CCMP
	eap=PEAP
	identity="DOMAIN\username"
	password="password"
}

I get this error, which repeats again and again as it tries:

Trying to associate with 00:15:c6:29:01:50 (SSID='NetworkName' freq=2412 MHz)
Associated with 00:15:c6:29:01:50
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
SSL: SSL3 alert: read (remote end reported an error):fatal:bad certificate
OpenSSL: openssl_handshake - SSL_connect error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
CTRL-EVENT-EAP-FAILURE EAP authentication failed
Authentication with 00:15:c6:29:01:50 timed out.
CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0

This Ubuntu bug looks similar.

Thanks again.

Last edited by jwhendy (2012-04-03 03:52:14)

jwhendy

Member

Registered: 2010-04-01

Posts: 621

Re: Wicd stopped connecting to company WPA2 network

Reverting to openssl-1.0.0.h-1 solved this for me.

poliocertes

Member

From: Poland

Registered: 2010-02-19

Posts: 29

Re: Wicd stopped connecting to company WPA2 network

Where can I download this openssl version?

jwhendy

Member

Registered: 2010-04-01

Posts: 621

Re: Wicd stopped connecting to company WPA2 network

@poliocertes: I used the Arch Rollback Machine. I just kept checking dates in March until I found 1.0.0.h. March 16th works for me (pick your architecture, then search the page for "openssl" and download openssl-1.0.0.h-1-architecture.pkg.tar.xz).

poliocertes

Member

From: Poland

Registered: 2010-02-19

Posts: 29

Re: Wicd stopped connecting to company WPA2 network

Doesn't work for me. Ethernet works fine but wifi still has problem with "bad password".

jwhendy

Member

Registered: 2010-04-01

Posts: 621

Re: Wicd stopped connecting to company WPA2 network

Can you run wpasupplicant manually and post the error? You should be able to find a config in /usr/lib/wicd/configurations or something similar. You can then compare with my error above. Wht protocol do you use? My network is peap-gtc for what it's worth. Good luck.

poliocertes

Member

From: Poland

Registered: 2010-02-19

Posts: 29

Re: Wicd stopped connecting to company WPA2 network

After downgrading kernel to previous version wifi under wicd works fine.

sunwei

Member

Registered: 2012-04-11

Posts: 1

Re: Wicd stopped connecting to company WPA2 network

I met the same issue. I tried the openssl 1.0.0.h and still could not connect to our wireless network.
Which kernel version that you downgraded to?

poliocertes

Member

From: Poland

Registered: 2010-02-19

Posts: 29

Re: Wicd stopped connecting to company WPA2 network

With kernel 3.2.14-1 wifi works fine.

lgeek

Member

From: Europe, Portugal

Registered: 2012-03-09

Posts: 70

Re: Wicd stopped connecting to company WPA2 network

With kernel 3.3.1 try this: https://bbs.archlinux.org/viewtopic.php?id=139365
You need to install  linux-headers.

Last edited by lgeek (2012-04-11 17:12:02)