Fwd: prolem connecting via wpa_supplicant

[JD]

On 06/07/2011 06:23 AM, Mike Martin wrote:
> Hi
>
> I have been trying to connect via wpa_supplicant
>
> this is wpa_supplicant
>
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=wheel
> eapol_version=1
> ap_scan=0
> fast_reauth=1
> network={
> ssid="npower2"
> scan_ssid=1
> #bssid=00:19:5b:4c:1e:59
> proto=WPA RSN
> key_mgmt=WPA-PSK
> pairwise=CCMP TKIP
> group=CCMP TKIP
> psk=008c0ea5d7244b9f2c944e4a4472bf4e040296f4b8c28c6e5b3d8c9da84b3fee
> priority=5
> }
>
> command
>
> wpa_supplicant -iwlan1 -c /etc/wpa_supplicant/wpa_supplicant.conf -B -dd
>
> resulting in output
>
> Initializing interface 'wlan1' conf
> '/etc/wpa_supplicant/wpa_supplicant.conf' driver 'default'
> ctrl_interface 'N/A' bridge 'N/A'
> Configuration file '/etc/wpa_supplicant/wpa_supplicant.conf' ->
> '/etc/wpa_supplicant/wpa_supplicant.conf'
> Reading configuration file '/etc/wpa_supplicant/wpa_supplicant.conf'
> ctrl_interface='/var/run/wpa_supplicant'
> ctrl_interface_group='wheel'
> eapol_version=1
> ap_scan=0
> fast_reauth=1
> Line: 6 - start of a new network block
> ssid - hexdump_ascii(len=7):
>      6e 70 6f 77 65 72 32                              npower2
> scan_ssid=1 (0x1)
> proto: 0x3
> key_mgmt: 0x2
> pairwise: 0x18
> group: 0x18
> PSK - hexdump(len=32): [REMOVED]
> priority=5 (0x5)
> Priority group 5
>    id=0 ssid='npower2'
> Initializing interface (2) 'wlan1'
> 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:60:b3:a5:ce:78
> 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
> ctrl_interface_group=10 (from group name 'wheel')
> Added interface wlan1
> Daemonize..
>
> resulting in no AP being associated
>
> I must be missing something simple
>
> anyone any ideas?
>
> BTW I can can connect via Network manager but that has its own issues
I hope you change your passphrase right away and
change to:
         key_mgmt=WPA-PSK
         proto=WPA2
         pairwise=CCMP
         group=CCMP
TKP has been broken with great ease in about 1 minute on a PC!!
See
http://www.dailywireless.org/2009/08/27/wpa-encryption-broken-in-60-seconds/