Slackware 13 - Wicd WPA PEAP TKIP MSCHAPV2

Do7AN · 09-11-2009, 09:41 AM

For the last couple of months I have been using rc.inet1, rc.inet1.conf and wpa_supplicant to connect to wireless at work. I would like to which to wicd because I am using a laptop that I take to meetings. Wireless uses WPA PEAP TKIP MSCHAPV2 and authenticates against Radius using only username and password. The ssid is not broadcast. The following are my configs. I have been trying to get wicd working but have not been able to authenticate. I have set rc.inet1.conf to default settings and wpa_supplicant to default settings.

Is there something I'm missing?

iwlist scanning

Code:

ESSID:""                                             
                    Mode:Master                                                
                    Channel:48                                                 
                    Frequency:5.24 GHz (Channel 48)                            
                    Quality=62/100  Signal level:-70 dBm  Noise level=-127 dBm 
                    Encryption key:on                                          
                    IE: Unknown: 000100                                        
                    IE: Unknown: 01088C129824B048606C                          
                    IE: Unknown: 050400010000                                  
                    IE: Unknown: 0712555320240414340414640514840314950414      
                    IE: IEEE 802.11i/WPA2 Version 1                            
                        Group Cipher : TKIP                                    
                        Pairwise Ciphers (1) : CCMP                            
                        Authentication Suites (1) : 802.1x                     
                    IE: Unknown: 9606004096000B00                              
                    IE: WPA Version 1                                          
                        Group Cipher : TKIP                                    
                        Pairwise Ciphers (1) : TKIP                            
                        Authentication Suites (1) : 802.1x                     
                    IE: Unknown: DD06004096010104                              
                    IE: Unknown: DD050040960305                                
                    IE: Unknown: DD050040960B09                                
                    IE: Unknown: DD080040961301003401                          
                    IE: Unknown: DD050040961405                                
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s        
                              36 Mb/s; 48 Mb/s; 54 Mb/s                        
                    Extra:tsf=000000f8cfe2e044                                 
                    Extra: Last beacon: 1049ms ago

wicd template

Code:

require identity *Identity password *Password
------
ctrl_interface=/var/run/wpa_supplicant
network={
        ssid="$_ESSID"
        scan_ssid=$_SCAN
        proto=WPA
        key_mgmt=WPA-EAP
        pairwise=TKIP
        group=TKIP
        eap=PEAP
        phase1="peaplabel=0"
        phase2="auth=MSCHAPV2"
        identity="$_IDENTITY"
        password="$_PASSWORD"
}

wpa_supplicant (I was using this and it worked)

Code:

#ctrl_interface=/var/run/wpa_supplicant
#ctrl_interface_group=wheel            
#eapol_version=1                       
#ap_scan=1                             
#fast_reauth=1                         
#network={                             
#        ssid="hidden"               
#       scan_ssid=1                    
#       key_mgmt=WPA-EAP               
#        eap=PEAP                      
#        pairwise=TKIP                 
#       phase1="peaplabel=0"           
#        phase2="auth=MSCHAPV2"        
#        identity="my username"             
#        password="my password"       
#}

wicd.log

Code:

2009/09/11 10:18:44 :: Connecting to wireless network <hidden>
2009/09/11 10:18:44 :: Putting interface down
2009/09/11 10:18:44 :: Releasing DHCP leases...
2009/09/11 10:18:44 :: Setting false IP...
2009/09/11 10:18:45 :: Stopping wpa_supplicant
2009/09/11 10:18:45 :: Flushing the routing table...
2009/09/11 10:18:45 :: Putting interface up...
2009/09/11 10:18:45 :: Attempting to authenticate...
2009/09/11 10:19:20 :: wpa_supplicant authentication may have failed.
2009/09/11 10:19:20 :: Running DHCP
2009/09/11 10:19:40 :: err, wlan0: timed out
2009/09/11 10:19:40 ::
2009/09/11 10:19:40 :: DHCP connection failed
2009/09/11 10:19:40 :: exiting connection thread

onebuck · 09-11-2009, 09:52 AM

Hi,

What about using 'wicd-curses' from the console to configure?

Do7AN · 09-11-2009, 10:07 AM

does wicd-curses give me any different configuration options than configuring it in using the gui?

onebuck · 09-11-2009, 04:44 PM

Hi,

In the past I have found the KDE system configuration interfaces not reliable to initialize network or system configurations. I've found success with using console tools whenever configuring system devices. Try the 'wicd-curses' and see if it works to initially setup the network devices.

It's your system to do as you desire or need.

black hole sun · 09-23-2009, 01:05 AM

Except that wicd is not a kde program.

To the OP, I've been having the same problem. Did you ever solve this?

H_TeXMeX_H · 09-23-2009, 02:20 AM

What wifi card do you have ? and what drivers are you using ? Maybe wpa_supplicant was not compiled with support for the driver.

easuter · 09-23-2009, 05:20 AM

If the network has a hidden ESSID, then it is possible that Wicd is trying to associate with the AP using an ESSID called "<hidden>", which of course won't work.
I use a similar setup for accessing the Eduroam wireless network at college, and I have to add this command to be executed before connecting (under the Wicd "Scripts" section, in the pre-connection text area)

Code:

/sbin/iwconfig wlan0 essid eduroam

This way the correct ESSID is set and I can connect (most of the time anyway, sometimes is takes a few tries :P)

onebuck · 09-23-2009, 06:41 AM

Hi,

Quote:

Originally Posted by black hole sun

Except that wicd is not a kde program.

To the OP, I've been having the same problem. Did you ever solve this?

'wicd' has a user interface that can be used for GNOME, KDE, Xfce, Fluxbox. Sure whenever using 'wicd' to make system changes the user must provide a username along with password when attempting configuration from the desktop.

The 'API' for system configuration via a 'GUI' adds another layer whenever the user needs to make changes. This layer is not always reliable. You will find the 'curses' based configuration tool closer to the 'cli' because of the control through scripting is solid. May not be as pretty or convenient as a desktop 'GUI' but you will have a reliable configuration thus less chance of error.

cmiranda · 09-23-2009, 07:29 AM

I just recently installed Slackware64 13 on my work laptop (Dell Latitude D630) which uses Intel PRO/Wireless 3945ABG and I am also experiencing this problem. I have a feeling that this is a problem with wicd because I used wpa_gui to connect to my wireless network which not only was hidden but also encrypted using WPA2-PSK.

I did notice that wicd did work when connecting to an unsecured network, but when connecting to a secure wireless network (regardless of whether the SSID is hidden or not) it can't seem to connect. It acts as though it associates fine, but then fails to grab an IP. And before anyone brings it up, I doubt it's dhcpcd/dhclient since it will grab an IP just fine with unsecured wifi networks. Wpa_gui gave me no problems whatsoever, which leads me to believe this version of wicd is the cause of the problem.

rvdboom · 09-23-2009, 07:52 AM

In the wicd graphic interface, when clicking on the Network button, you can have a Find a hidden network option.
When clicking it, you are asked the ESSID of the hidden network.
Have you tried using this?

cmiranda · 09-23-2009, 08:08 AM

Quote:

Originally Posted by rvdboom

In the wicd graphic interface, when clicking on the Network button, you can have a Find a hidden network option.
When clicking it, you are asked the ESSID of the hidden network.
Have you tried using this?

Yes, I have. Still does not work. I have even shutdown the wicd daemon, edited the wireless-settings.conf file and manually inserted the SSID name, and restarted the wicd daemon to no avail.

cmiranda · 09-23-2009, 08:21 AM

Just to add to my situation, I disabled execution of the rc.wireless script in the event that it was conflicting with rc.wicd and rebooted my laptop. It still cannot connect through wicd-curses or through the GUI interface.

quanta · 09-23-2009, 09:04 AM

Quote:

Originally Posted by cmiranda

Just to add to my situation, I disabled execution of the rc.wireless script in the event that it was conflicting with rc.wicd and rebooted my laptop. It still cannot connect through wicd-curses or through the GUI interface.

Did you try connect from command line? iwconfig, iwpriv, dhclient (or dhcpcd)...

cmiranda · 09-23-2009, 09:13 AM

Quote:

Originally Posted by quanta

Did you try connect from command line? iwconfig, iwpriv, dhclient (or dhcpcd)...

As mentioned, Wpa_gui worked for me. I can only assume that if wpa_gui (which is the GUI for wpa_supplicant) worked that the commands you mentioned would have worked as well since they work in tandem to get the connection going. The only time I had an issue connecting to secured wireless network (hidden or not) was with wicd.

2Gnu · 09-23-2009, 09:27 AM

In this thread, an updated version of wicd fixed the problem:
http://www.linuxquestions.org/questi...sid...-752873/