[Tfug] Xsupplicant woes -- setup misery (now wpa_supplicant woes)

[Wafa Hakim Orman]

Jeremy D Rogers said:


First, i would recommend wpasupplicant. It seems to be a little easier
to deal with than xsupplicant, and you should be able to apt-get it.


--> I didn't realize I could use wpa_supplicant with a WEP network,
but I googled it & I realized you're right. So I tried it.

Unsuccessfully. I've pasted all the output it spat out at me below:

wafa at Hitchhiker:~$ sudo  wpa_supplicant -ieth1
-c/etc/wpa_supplicant.conf -d -Dndiswrapper
Initializing interface 'eth1' conf '/etc/wpa_supplicant.conf' driver
'ndiswrapper' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='0' (DEPRECATED)
eapol_version=1
ap_scan=2
fast_reauth=1
Priority group 5
   id=0 ssid='AIRBEAR'
   id=1 ssid='SomeOpenSSID'
   id=2 ssid='WPASSID'
Initializing interface (2) 'eth1'
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
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=21 WE(source)=18 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:0c:e5:51:07:1d
Driver does not support 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
Setting scan request: 0 sec 100000 usec
Using existing control interface directory.
ctrl_interface_group=0
bind(PF_UNIX): Address already in use
ctrl_iface exists, but does not allow connections - assuming it was
leftover from forced program termination
Successfully replaced leftover ctrl_iface socket '/var/run/wpa_supplicant/eth1'
Added interface eth1
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'AIRBEAR'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
Overriding auth_alg selection: 0x2
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
*** stack smashing detected ***: wpa_supplicant terminated
Aborted (core dumped)




(Note: I do now have the key all set up as a PEM file & in the right
location -- I think. So what else would I need to do to configure the
keys?)

Also, below is the relevant section of my wpa_supplicant.conf file:



network={
        ssid="AIRBEAR"
        scan_ssid=0
        mode=0
        key_mgmt=IEEE8021X
        auth_alg=OPEN
        eapol_flags=3
        #wep_key0=F53DB57797912DDC52A21A5592
        #wep_tx_keyidx=0
        #eap=MSCHAPV2
        identity="me at baylor.edu"
        password="mybaylorpassword"
        priority=5
        ca_cert="/etc/ssl/certs/airbearcert.pem"
        ca_path="/etc/ssl/certs"
        client_cert="/home/wafa/airbearcert.pem"
        private_key="/home/wafa/airbearcert.pem"
        auth_alg=SHARED
}


What am I doing wrong this time? I'm starting to feel a little stupid.

Thanks a ton,

Wafa.
-- 
"So be it."
                  --Kurt Vonnegut