This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

wl1271 + ThreadX having problem with WEP Authentication

Other Parts Discussed in Thread: WL1271

Hi,

We are porting wl1271 driver into a ThreadX based project. It is currently able to connect with no security option, however, we meet some problem in WEP authentication:

 

============================================================================

run "wlan_cu -b

user_main, start
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt
coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
p


.../Privacy> Authentication, encRyption, pskPassphrase, Wep/
r 1
MainSec SM: config, authProtocol = 0, keyExchangeProtocol=1, unicastSuite=1, broadcastSuite=1
MAIN_SEC_SM: successful configuration SM
Setting privacy encryption to 1

.../Privacy> Authentication, encRyption, pskPassphrase, Wep/
w
.../Wep> Add, Remove, Get default key id
a B19227EF6E 1 1 hex
/
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt
coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
c

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list
c linksys
cmdMbox_SendCommand(): Command length isn't 32bit aligned! CmdId=49
MLME_PARSER: recieved PROBE_RESPONSE message
MLME_PARSER: recieved PROBE_RESPONSE message

  Link Speed = 0x0009b078
cmdInterpret_Event: DEFAULT, type=2

  Link Speed = 0x00083d60
cmdInterpret_Event: DEFAULT, type=2
MainSec SM: config, authProtocol = 0, keyExchangeProtocol=1, unicastSuite=1, broadcastSuite=1
MAIN_SEC_SM: successful configuration SM
OPEN_AUTH_SM: DEBUG Authentication status is 0
ASSOC_SM: DEBUG Success associating to AP
cmdInterpret_Event: IPC_EVENT_ASSOCIATED
ASSOC_SM: DEBUG - Association Information Get: 
ASSOC_SM: DEBUG - Association Information Get: 
MAIN_SEC_SM: mainSecKeysOnly_StartIdle...
MAIN_SEC_SM: mainSecKeysOnly_KeysCompleteAuthenticated...

  Auth Succ Event from Driver to another BSSID.
cmdInterpret_Event: DEFAULT, type=3
************ NEW CONNECTION ************
-- BSSID = 00000000-00000018-00000039-0000003b-00000051-0000005c
-- SSID  = linksys
****************************************

====================================================================================

We are able to connect to AP by using WEP security, however, it seems like wl1271 failed to receive incoming data packet after that

We did observer wl1271 module does trigger WL IRQ and call rsn_pairwiseReKeyTimeout() function, it seems like there is a timeout event which failed WEP connection.

Do you have any ideas on this issue? Many thanks!

 

Regards,

Han Sian

  • Hi Han,

    can you try the following:

    1) Set the Management mode to manual (1).

    2) Set the authentication to open (0).

    3) Set the encryption as WEP.

    The complete script for these actions is shown below:

    / d s
    / m d 1
    / p a 0
    / p w a 88f2c58643 1 1 hex
    

     

    Below are some of the logs associated with the script above.

    \> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, 
    Bt coexsistence/, Report/, dEbug/, biT/, aboUt, Quit
    m
    .../Management> connect moDe, Channel, Rate, Mode, Frag, rTs, prEamble, sLot, rAdio on/off, 
    Info, siGnal, snr ratiO, tX_power_table, tx_power_dBm_div10, tx_poWer_level, 802_11d_h/, beacoN/, adVanced/
    d 1
    .../Management> connect moDe, Channel, Rate, Mode, Frag, rTs, prEamble, sLot, rAdio on/off, 
    Info, siGnal, snr ratiO, tX_power_table, tx_power_dBm_div10, tx_poWer_level, 802_11d_h/, beacoN/, adVanced/
    d
    Current mode = SME Manual
    0 - SME Auto, 1 - SME Manual
    .../Privacy> Authentication, Eap, encRyption, Keytype, Mixedmode, aNywpamode, Credentials, pskPassph
    rase, cerTificate, Supplicant/, Wep/
    a 0
    
    Setting privacy authentication to 0
    .../Privacy> Authentication, Eap, encRyption, Keytype, Mixedmode, aNywpamode, Credentials, pskPassph
    rase, cerTificate, Supplicant/, Wep/
    r
    0 - None, 1 - WEP, 2 - TKIP, 3 – AES
    
    .../Privacy> Authentication, Eap, encRyption, Keytype, Mixedmode, aNywpamode, Credentials, pskPassph
    rase, cerTificate, Supplicant/, Wep/
    r 1
    
    Setting privacy encryption to 1
    
    .../Privacy> Authentication, Eap, encRyption, Keytype, Mixedmode, aNywpamode, Credentials, pskPassph
    rase, cerTificate, Supplicant/, Wep/
    w
    
    .../Wep> Add, Remove, Get default key id
    a
    
    Add WEP: Add <Key Value (0..64 chars)>
    <Tx Key Index)>
    <Default Key (yes - 1 /no - 0)>
    [key type (hex | text) [hex] (0..5 chars)]
    
    .../Wep> Add, Remove, Get default key id
    a 88f2c58643 1 1 hex
    
    .../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
    c peterpan
    
    14
    Trying to associate with SSID ’peterpan’
    OK
    ************ NEW CONNECTION ************
    -- SSID  = peterpan
    -- BSSID = 0-f-b5-e6-ed-fc
    ****************************************
    Associated with 00:0f:b5:e6:ed:fc
    CTRL-EVENT-CONNECTED - Connection to 00:0f:b5:e6:ed:fc completed (reauth) [id=14 id_str=]
    

     

  • Hi Eyal,

    Thanks for your help on this! We found out that we are missed out authentication setting in wilink driver (since our project doesn't include wpa_supplicant).

    Our board currently able to receive data from wl1271 module through WL IRQ. However, we observe some error message:

     

    =========================================================

    rxData_ReceivePacket: Received Packet with RX_DESC_DECRYPT_FAIL

    =========================================================

     

    Any chance that you have idea on this issue? Many thanks.

     

    Regards,

    Han Sian

  • Hi Han Sian,

    It means that there is a decryption error in the receive path. How often do you see it? Is it for every packet or is it randomly appears ?

    Thanks,

    Eyal

  • Hi Eyal,

    Yes, it show this message for every packet which sent through ping command from PC. We suspects that there is some wrong setting for WEP in our project (I don't have the detail information in hand now, I shall provided it in next few days)

    Do you have any idea on this issue? Thanks.

     

    Regards,

    Han Sian

  • Hi Han,

    it should work with no issue, can you send me the key command you are using on the CLI, as well the key setting of the Access point yuo are using? keep in mind that in wep there is an option to define up to 4 keys and use one of them and the configuration of the Station and the Access point should match.

     

    Regards,

    Eyal

  • Hi Eyal,

     

    We found that the WEP key was mis-matched while the firmware sent it to driver through WEXT interface. Once fix this, wl1271 is able to receive data after connected to WEP security network.

    Thanks lots for your help :)

     

    Regards,

    Han Sian

  • Hi Han,

    thanks for the update, good luck with the project n general.

    Regards,

    Eyal