wpa_supplicant problem - Networking

This is a discussion on wpa_supplicant problem - Networking ; Hello Here is my config: network={ #mode=1 scan_ssid=1 ssid="A-WPA" key_mgmt=WPA-PSK #proto=WPA #pairwise=NONE #group=TKIP #hex of my secret passphrase psk=dfc0de6dbfc4c1c54e336d2b20150f9551cdfaef5c8722 3006040e65a6ef50b6 } when i launched wpa_supplicant i received: ............... IEEE 802.1X RX: version=1 type=3 length=159 EAPOL-Key type=2 key_info 0x13c9 (ver=1 keyidx=0 ...

+ Reply to Thread
Results 1 to 7 of 7

Thread: wpa_supplicant problem

  1. wpa_supplicant problem

    Hello

    Here is my config:
    network={
    #mode=1
    scan_ssid=1
    ssid="A-WPA"
    key_mgmt=WPA-PSK
    #proto=WPA
    #pairwise=NONE
    #group=TKIP
    #hex of my secret passphrase
    psk=dfc0de6dbfc4c1c54e336d2b20150f9551cdfaef5c8722 3006040e65a6ef50b6
    }

    when i launched wpa_supplicant i received:

    ...............
    IEEE 802.1X RX: version=1 type=3 length=159
    EAPOL-Key type=2
    key_info 0x13c9 (ver=1 keyidx=0 rsvd=0 Pairwise Install Ack MICSecure
    Encr)
    key_length=32 key_data_length=64
    replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 01
    key_nonce - hexdump(len=32): 9c a5 7a 2b 88 21 46 07 34 5d d2 a3 a059
    1e ff cc 15 2a 1b b8 91 f6 f7 64 cd 82 93 d0 c9 cf 07
    key_iv - hexdump(len=16): 02 13 50 49 4e 6f 7c 05 5a 8b 68 81 26 6714 bd
    key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
    key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
    key_mic - hexdump(len=16): eb f9 41 95 b8 e6 26 a7 6d ac 0c b2 18 6c 57
    35
    WPA: RX EAPOL-Key - hexdump(len=163): 01 03 00 9f 02 13 c9 00 20 00 0000
    00 00 00 00 01 9c a5 7a 2b 88 21 46 07 34 5d d2 a3 a0 59 1e ff cc 15 2a 1b
    b8 91 f6 f7 64 cd 82 93 d0 c9 cf 07 02 13 50 49 4e 6f 7c 05 5a 8b 68 81 26
    67 14 bd 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 eb f9 41 95 b8 e6
    26 a7 6d ac 0c b2 18 6c 57 35 00 40 56 19 9b 6e 89 0b 79 85 dc 2e c2 da dc
    d4 8f fd e8 b4 83 a7 93 c3 5b 59 7b df 92 99 47 9a 3e 36 2f 9d fa 50 07 85
    e9 d0 0e 45 5f ce d2 bc c0 9b 96 be 3f c7 16 0c f3 4e 4a d1 51 8a bd 4b e0
    bf
    RSN: encrypted key data - hexdump(len=64): 56 19 9b 6e 89 0b 79 85 dc 2e
    c2 da dc d4 8f fd e8 b4 83 a7 93 c3 5b 59 7b df 92 99 47 9a 3e 36 2f 9d fa
    50 07 85 e9 d0 0e 45 5f ce d2 bc c0 9b 96 be 3f c7 16 0c f3 4e 4a d1 51 8a
    bd 4b e0 bf
    WPA: decrypted EAPOL-Key key data - hexdump(len=64): [REMOVED]
    State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
    WPA: RX message 3 of 4-Way Handshake from 00:19:e1:af:5d:c0 (ver=1)
    WPA: IE KeyData - hexdump(len=64): 30 14 01 00 00 0f ac 02 01 00 00 0fac
    02 01 00 00 0f ac 02 00 00 dd 26 00 0f ac 01 01 00 b0 29 ae 4f dc e5 ba 6b
    c8 61 86 47 74 9d 12 e3 e0 99 5e 3f 0c 55 6a 5b f8 d1 36 37 a4 0d c2 d3 dd
    00
    WPA: Sending EAPOL-Key 4/4
    WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f 02 03 09 00 00 00 00 00
    00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0 c6 d4 56 f2 aa
    15 1d 4c ef c8 2e 85 be 7e b4 00 00
    WPA: Installing PTK to the driver.
    wpa_driver_wext_set_key: alg=2 key_idx=0 set_tx=1 seq_len=6 key_len=32
    ioctl[SIOCSIWENCODEEXT]: Invalid argument
    Driver did not support SIOCSIWENCODEEXT
    WPA: Failed to set PTK to the driver.

    i have: Intel Corporation PRO/Wireless 3945ABG
    I use current drivers: ipw3945-1.2.2
    Under windows it works fine.

    What's wrong ? Is it possible that this drivers does not support simple
    WPA/TKIP with PSK ?
    has anybody launched WPA using this card on linux ?

    Thanx

  2. Re: wpa_supplicant problem

    The ipw3945 driver works fine with the Intel 3945 wireless card.
    The problem is not the driver. The problem is your setup.
    (Note that publishing your passphrase on the net makes it pretty useless.)

    a) First set up your modem/wireless router not to use any authentication.
    Connect with no authentication to make sure everything is working and that
    there is not some stupid mistake, such as using the wrong ssid (your ssid
    looks weird)

    vertigo writes:FTR you have gotten the system to
    work with no security, then switch on wpa on the modem and try again.



    >Hello


    >Here is my config:
    >network=3D{
    > #mode=3D1
    > scan_ssid=3D1
    > ssid=3D"A-WPA"
    > key_mgmt=3DWPA-PSK
    > #proto=3DWPA
    > #pairwise=3DNONE
    > #group=3DTKIP
    > #hex of my secret passphrase
    > psk=3Ddfc0de6dbfc4c1c54e336d2b20150f9551cdfaef5c87 223006040e65a6ef5=
    >0b6
    >}


    >when i launched wpa_supplicant i received:


    >..............
    >IEEE 802.1X RX: version=3D1 type=3D3 length=3D159
    > EAPOL-Key type=3D2
    > key_info 0x13c9 (ver=3D1 keyidx=3D0 rsvd=3D0 Pairwise Install Ack MIC=
    > Secure =


    >Encr)
    > key_length=3D32 key_data_length=3D64
    > replay_counter - hexdump(len=3D8): 00 00 00 00 00 00 00 01
    > key_nonce - hexdump(len=3D32): 9c a5 7a 2b 88 21 46 07 34 5d d2 a3 a0=
    > 59 =


    >1e ff cc 15 2a 1b b8 91 f6 f7 64 cd 82 93 d0 c9 cf 07
    > key_iv - hexdump(len=3D16): 02 13 50 49 4e 6f 7c 05 5a 8b 68 81 26 67=
    > 14 bd
    > key_rsc - hexdump(len=3D8): 00 00 00 00 00 00 00 00
    > key_id (reserved) - hexdump(len=3D8): 00 00 00 00 00 00 00 00
    > key_mic - hexdump(len=3D16): eb f9 41 95 b8 e6 26 a7 6d ac 0c b2 18 6=
    >c 57 =


    >35
    >WPA: RX EAPOL-Key - hexdump(len=3D163): 01 03 00 9f 02 13 c9 00 20 00 00=
    > 00 =


    >00 00 00 00 01 9c a5 7a 2b 88 21 46 07 34 5d d2 a3 a0 59 1e ff cc 15 2a =
    >1b =


    >b8 91 f6 f7 64 cd 82 93 d0 c9 cf 07 02 13 50 49 4e 6f 7c 05 5a 8b 68 81 =
    >26 =


    >67 14 bd 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 eb f9 41 95 b8 =
    >e6 =


    >26 a7 6d ac 0c b2 18 6c 57 35 00 40 56 19 9b 6e 89 0b 79 85 dc 2e c2 da =
    >dc =


    >d4 8f fd e8 b4 83 a7 93 c3 5b 59 7b df 92 99 47 9a 3e 36 2f 9d fa 50 07 =
    >85 =


    >e9 d0 0e 45 5f ce d2 bc c0 9b 96 be 3f c7 16 0c f3 4e 4a d1 51 8a bd 4b =
    >e0 =


    >bf
    >RSN: encrypted key data - hexdump(len=3D64): 56 19 9b 6e 89 0b 79 85 dc =
    >2e =


    >c2 da dc d4 8f fd e8 b4 83 a7 93 c3 5b 59 7b df 92 99 47 9a 3e 36 2f 9d =
    >fa =


    >50 07 85 e9 d0 0e 45 5f ce d2 bc c0 9b 96 be 3f c7 16 0c f3 4e 4a d1 51 =
    >8a =


    >bd 4b e0 bf
    >WPA: decrypted EAPOL-Key key data - hexdump(len=3D64): [REMOVED]
    >State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
    >WPA: RX message 3 of 4-Way Handshake from 00:19:e1:af:5d:c0 (ver=3D1)
    >WPA: IE KeyData - hexdump(len=3D64): 30 14 01 00 00 0f ac 02 01 00 00 0f=
    > ac =


    >02 01 00 00 0f ac 02 00 00 dd 26 00 0f ac 01 01 00 b0 29 ae 4f dc e5 ba =
    >6b =


    >c8 61 86 47 74 9d 12 e3 e0 99 5e 3f 0c 55 6a 5b f8 d1 36 37 a4 0d c2 d3 =
    >dd =


    >00
    >WPA: Sending EAPOL-Key 4/4
    >WPA: TX EAPOL-Key - hexdump(len=3D99): 01 03 00 5f 02 03 09 00 00 00 00 =
    >00 =


    >00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =
    >00 =


    >00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =
    >00 =


    >00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0 c6 d4 56 f2 =
    >aa =


    >15 1d 4c ef c8 2e 85 be 7e b4 00 00
    >WPA: Installing PTK to the driver.
    >wpa_driver_wext_set_key: alg=3D2 key_idx=3D0 set_tx=3D1 seq_len=3D6 key_=
    >len=3D32
    >ioctl[SIOCSIWENCODEEXT]: Invalid argument
    >Driver did not support SIOCSIWENCODEEXT
    >WPA: Failed to set PTK to the driver.


    >i have: Intel Corporation PRO/Wireless 3945ABG
    >I use current drivers: ipw3945-1.2.2
    >Under windows it works fine.


    >What's wrong ? Is it possible that this drivers does not support simple =
    > =


    >WPA/TKIP with PSK ?
    >has anybody launched WPA using this card on linux ?



  3. Re: wpa_supplicant problem

    hello, i've tested it without authentication
    and with WEP authentication. It works fine.

    But it does not work with WPA.
    I tested the same computer from windows system and it uses WPA without
    problem.

    Is it possible that linux drivers does not support WPA ?

    Thanx

    > The ipw3945 driver works fine with the Intel 3945 wireless card.
    > The problem is not the driver. The problem is your setup.
    > (Note that publishing your passphrase on the net makes it pretty
    > useless.)
    >
    > a) First set up your modem/wireless router not to use any authentication.
    > Connect with no authentication to make sure everything is working and
    > that
    > there is not some stupid mistake, such as using the wrong ssid (your
    > ssid
    > looks weird)
    >
    > vertigo writes:FTR you have gotten the systemto
    > work with no security, then switch on wpa on the modem and try again.
    >
    >
    >
    >> Hello

    >
    >> Here is my config:
    >> network=3D{
    >> #mode=3D1
    >> scan_ssid=3D1
    >> ssid=3D"A-WPA"
    >> key_mgmt=3DWPA-PSK
    >> #proto=3DWPA
    >> #pairwise=3DNONE
    >> #group=3DTKIP
    >> #hex of my secret passphrase
    >> psk=3Ddfc0de6dbfc4c1c54e336d2b20150f9551cdfaef5c87 223006040e65a6ef5=
    >> 0b6
    >> }

    >
    >> when i launched wpa_supplicant i received:

    >
    >> ..............
    >> IEEE 802.1X RX: version=3D1 type=3D3 length=3D159
    >> EAPOL-Key type=3D2
    >> key_info 0x13c9 (ver=3D1 keyidx=3D0 rsvd=3D0 Pairwise InstallAck MIC=
    >> Secure =

    >
    >> Encr)
    >> key_length=3D32 key_data_length=3D64
    >> replay_counter - hexdump(len=3D8): 00 00 00 00 00 00 00 01
    >> key_nonce - hexdump(len=3D32): 9c a5 7a 2b 88 21 46 07 34 5d d2 a3 a0=
    >> 59 =

    >
    >> 1e ff cc 15 2a 1b b8 91 f6 f7 64 cd 82 93 d0 c9 cf 07
    >> key_iv - hexdump(len=3D16): 02 13 50 49 4e 6f 7c 05 5a 8b 68 81 26 67=
    >> 14 bd
    >> key_rsc - hexdump(len=3D8): 00 00 00 00 00 00 00 00
    >> key_id (reserved) - hexdump(len=3D8): 00 00 00 00 00 00 00 00
    >> key_mic - hexdump(len=3D16): eb f9 41 95 b8 e6 26 a7 6d ac 0c b2 18 6=
    >> c 57 =

    >
    >> 35
    >> WPA: RX EAPOL-Key - hexdump(len=3D163): 01 03 00 9f 02 13 c9 00 20 00
    >> 00=
    >> 00 =

    >
    >> 00 00 00 00 01 9c a5 7a 2b 88 21 46 07 34 5d d2 a3 a0 59 1e ff cc 15 2a
    >> =
    >> 1b =

    >
    >> b8 91 f6 f7 64 cd 82 93 d0 c9 cf 07 02 13 50 49 4e 6f 7c 05 5a 8b 68 81
    >> =
    >> 26 =

    >
    >> 67 14 bd 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 eb f9 41 95 b8
    >> =
    >> e6 =

    >
    >> 26 a7 6d ac 0c b2 18 6c 57 35 00 40 56 19 9b 6e 89 0b 79 85 dc 2e c2 da
    >> =
    >> dc =

    >
    >> d4 8f fd e8 b4 83 a7 93 c3 5b 59 7b df 92 99 47 9a 3e 36 2f 9d fa 50 07
    >> =
    >> 85 =

    >
    >> e9 d0 0e 45 5f ce d2 bc c0 9b 96 be 3f c7 16 0c f3 4e 4a d1 51 8a bd 4b
    >> =
    >> e0 =

    >
    >> bf
    >> RSN: encrypted key data - hexdump(len=3D64): 56 19 9b 6e 89 0b 79 85 dc
    >> =
    >> 2e =

    >
    >> c2 da dc d4 8f fd e8 b4 83 a7 93 c3 5b 59 7b df 92 99 47 9a 3e 36 2f 9d
    >> =
    >> fa =

    >
    >> 50 07 85 e9 d0 0e 45 5f ce d2 bc c0 9b 96 be 3f c7 16 0c f3 4e 4a d1 51
    >> =
    >> 8a =

    >
    >> bd 4b e0 bf
    >> WPA: decrypted EAPOL-Key key data - hexdump(len=3D64): [REMOVED]
    >> State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
    >> WPA: RX message 3 of 4-Way Handshake from 00:19:e1:af:5d:c0 (ver=3D1)
    >> WPA: IE KeyData - hexdump(len=3D64): 30 14 01 00 00 0f ac 02 01 00 00
    >> 0f=
    >> ac =

    >
    >> 02 01 00 00 0f ac 02 00 00 dd 26 00 0f ac 01 01 00 b0 29 ae 4f dc e5 ba
    >> =
    >> 6b =

    >
    >> c8 61 86 47 74 9d 12 e3 e0 99 5e 3f 0c 55 6a 5b f8 d1 36 37 a4 0d c2 d3
    >> =
    >> dd =

    >
    >> 00
    >> WPA: Sending EAPOL-Key 4/4
    >> WPA: TX EAPOL-Key - hexdump(len=3D99): 01 03 00 5f 02 03 09 00 00 00 00
    >> =
    >> 00 =

    >
    >> 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    >> =
    >> 00 =

    >
    >> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    >> =
    >> 00 =

    >
    >> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0 c6 d4 56 f2
    >> =
    >> aa =

    >
    >> 15 1d 4c ef c8 2e 85 be 7e b4 00 00
    >> WPA: Installing PTK to the driver.
    >> wpa_driver_wext_set_key: alg=3D2 key_idx=3D0 set_tx=3D1 seq_len=3D6
    >> key_=
    >> len=3D32
    >> ioctl[SIOCSIWENCODEEXT]: Invalid argument
    >> Driver did not support SIOCSIWENCODEEXT
    >> WPA: Failed to set PTK to the driver.

    >
    >> i have: Intel Corporation PRO/Wireless 3945ABG
    >> I use current drivers: ipw3945-1.2.2
    >> Under windows it works fine.

    >
    >> What's wrong ? Is it possible that this drivers does not support simple
    >> =
    >> =

    >
    >> WPA/TKIP with PSK ?
    >> has anybody launched WPA using this card on linux ?

    >




    --
    Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

  4. Re: wpa_supplicant problem

    vertigo wrote:
    > hello, i've tested it without authentication
    > and with WEP authentication. It works fine.
    >
    > But it does not work with WPA.
    > I tested the same computer from windows system and it uses WPA without
    > problem.
    >
    > Is it possible that linux drivers does not support WPA ?


    Most Linux drivers do indeed support WPA. AFAIK, ipw3945 does.

    In wpa_supplicant.conf, you need to list the passphrase, not the hex code.

    Larry


  5. Re: wpa_supplicant problem

    Larry Finger writes:

    >vertigo wrote:
    >> hello, i've tested it without authentication
    >> and with WEP authentication. It works fine.
    >>
    >> But it does not work with WPA.
    >> I tested the same computer from windows system and it uses WPA without
    >> problem.
    >>
    >> Is it possible that linux drivers does not support WPA ?


    >Most Linux drivers do indeed support WPA. AFAIK, ipw3945 does.


    >In wpa_supplicant.conf, you need to list the passphrase, not the hex code.


    >Larry


    This (passphrase in ASCII) was my 1st thought too, but the man page
    says:

    psk WPA preshared key used in WPA-PSK mode. The key is specified as
    64 hex digits or as an 8-63 character ASCII passphrase. ASCII
    passphrases are converted to a 256-bit key using the network
    SSID.

    I have it in my wpa_supplicant.conf as psk="blablabla" and it
    works fine for me (but mine is PRO/Wireless 2200BG in FreeBSD 6.2)

    matthias


  6. Re: wpa_supplicant problem

    Matthias Apitz wrote:
    >
    > This (passphrase in ASCII) was my 1st thought too, but the man page
    > says:
    >
    > psk WPA preshared key used in WPA-PSK mode. The key is specified as
    > 64 hex digits or as an 8-63 character ASCII passphrase. ASCII
    > passphrases are converted to a 256-bit key using the network
    > SSID.
    >
    > I have it in my wpa_supplicant.conf as psk="blablabla" and it
    > works fine for me (but mine is PRO/Wireless 2200BG in FreeBSD 6.2)


    I have only use the passphrase, but I would expect that one would need to prefix the hex key with a
    0x if you wanted to use it. At least, there needs to be some indication that you are using the hex,
    and not an ASCII phrase.

    Larry

  7. Re: wpa_supplicant problem

    Larry Finger writes:

    >Matthias Apitz wrote:
    >>
    >> This (passphrase in ASCII) was my 1st thought too, but the man page
    >> says:
    >>
    >> psk WPA preshared key used in WPA-PSK mode. The key is specified as
    >> 64 hex digits or as an 8-63 character ASCII passphrase. ASCII
    >> passphrases are converted to a 256-bit key using the network
    >> SSID.
    >>
    >> I have it in my wpa_supplicant.conf as psk="blablabla" and it
    >> works fine for me (but mine is PRO/Wireless 2200BG in FreeBSD 6.2)


    >I have only use the passphrase, but I would expect that one would need to prefix the hex key with a
    >0x if you wanted to use it. At least, there needs to be some indication that you are using the hex,
    >and not an ASCII phrase.


    Without looking into the source of /usr/sbin/wpa_supplicant, it
    could be differentiate a hex key from ASCII as well from the fact
    that a hex key must consist of exactly 64 hex digits, while an ASCII
    passphrase is limited to 63 and allows any ASCII char.
    I never used hex keys until now.

    matthias

+ Reply to Thread