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.

Connecting to Enterprise network takes longer time most of the time and sometimes does not connect at all

Other Parts Discussed in Thread: WL1271

Jorjin wl1273 Module running on a Linux based embedded system. 

The Wifi driver is taken from WL1271 Linux SDK v3.0.01.06-WL6.1.6.3. 

Wpa Supplicant version 0.5.7 

WE do not see any issues when connecting to personal networks. 

When we try to connect to PEAP enabled Enterprise network, it take a couple of minutes to get connected. And some times does not connect at all

WE have narrowed the where the maximum time is taken and the it is listed below. 

Step 1 --> Auth done and Associated

Step 2 --> EAPOL - Start ( Wl1273 station to AP )

Step 3 --> EAP-Request ( Identity AP --> Station )

The next step is the problem 

Step 4 --> WPA Supplicant does send the response Identity. This data is also sent to Wl1273 hardware. However, when we capture with wireshark sniffer, we do not see the response going to AP. AP and station are placed very close to each other. Also, we checked the logs in the Access Point and it has not received this response. We are unable to confirm whether wl1273 FW is sending out the response. 

At this stage, WPA-Supplicant timesout after 30 secs and starts the Auth and Association process again. 

This continues for 2 -3 times and then 3rd or 4th time, connection succeeds. 

We are simply clueless on the above. We also not sure how to confirm that wl1273 firmware is indeed sending out the response. 

I was referring through the Known issues for this release and I came across the below 

Headline Connection establishment may delay up to 60 seconds when working with AES/TLS/PEAP/CCKM.
Internal numbering MCS00079615
Description/Scenario Connection establishment may delay up to 60 seconds when working with

AES/TLS/PEAP/CCKM.


Is the issue what we are seeing today related to the above bug .

Would greatly appreciate if we can get help on how to resolve this. We are having enough Wireless sniffer and Wpa_supplicant logs. I can attach if it would help. 

  • Hi Siva,

    Which AP are you working on? And which FW version are you working on? Can you share WLAN log here?

    The reason I'm asking those question is that I have encountered the exact same problem. After lots of investigation, it was an IOP with Cisco AP. The problem (actually Cisco is to blame) is that the AP stores the full last packet and the sequence number. In each new assocation, TI FW reset all TIDs sequence numbers, so the first EAPOL is send with sequence number 0. Somehow the Cisco duplication detection sometimes thought it already got the EAPOL and throw it without even logging about it.

    The fix we did there was to change the FW and set all TIDs  to use the same global sequence number generator which hasn't been reset per connection.

    - Elad

  • Hi Elad

    The WLAN Driver and Firmware version is as below

    TIWLAN: 77.020890: --------------------------------------------------------------------
    TIWLAN: 77.020974: Driver Version  : WiLink_Driver_6.1.0.1.149
    TIWLAN: 77.021036: Firmware Version: Rev 6.1.0.1.349
    TIWLAN: 77.021108: Station ID      : 08-00-28-12-34-56
    TIWLAN: 77.021166: ----------------------------------------

    The routers we used for testing are below. We are seeing problems in both these routers.

    Cisco Aeronet--> Model Number is AIR AP - 1252 ag - S - K9

    The behavior for the above router is that for sure first and second attempt is unsuccessful and most of the in third it gets connected. However, 10-15 % of the time connection does not happen at all

    Dlink Router --> DIR 615 --> For this router 2nd or 3rd attempt is successful.

    I have attached three logs here. This log is captured while connecting to DLINK router.

    wlan_logs_Device_Router_Failure_then_Success.txt --> Wifi Driver log --> we enabled INIT, INFORMATION, WARNING and ERROR traces in tiwlan.ini

    Device_Router_Failure_then_Success.pcap  --> Airpcap sniffer logs ( Please rename the txt extension to pcap extension. This forum is not allowing to attach pcap files)

    wlan.addr==08:00:28:12:34:56 . Please use this address to filter

     Router_Server_Failure_then_Success.pcap  --> Dlink Router to Radius server logs ( Please rename the txt extension to pcap extension. This forum is not allowing to attach pcap files)
    ip.addr==172.22.40.172 && ip.addr==172.22.43.167

    172.22.43.167 - Router WLAN IP address.
    172.22.40.172 - Radius server IP address.

    CGU: Get clock id:20 freq:45000000
    lpc313x_mmc lpc313x_mmc.0: LPC313x MMC controller at irq 26
    mmc0: card claims to support voltages below the defined range. These will be ignored.
    mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
    mmc0: queuing CIS tuple 0x91 length 3
    mmc0: new SDIO card at address 0001
    sdioDrv_init: Register Platform Device
    WL1271: SDIO controller Detected
    Registering PM platform driver
    tiwl1271_pl_sdio_probe: tiwlan_pm_driver loaded
    platform_driver_register return: 0
    TIWLAN: driver init
    g_drv.claim_host_flag = 0 ... so returning 
    In hPlatform_initInterrupt function
    Request irq sucessfull !!!!!!!
    Returning from wlanDrvIf_Create function
    TIWLAN: 75.526647: wlanDrvIf_Open()
    TIWLAN: 76.497921: AutoDetect = 0
    TIWLAN: 76.727777: mainSecSm               , SM:MainSec SM: config, authProtocol = 0, keyExchangeProtocol=0, unicastSuite=0, broadcastSuite=0
    TIWLAN: 76.728032: mainSecSm               , SM:MAIN_SEC_SM: successful configuration SM
    TIWLAN: 76.728812: pInitParams->RoamingScanning_2_4G_enable 0 
    sdioDrv_ClaimHost successfull !!!!!!!
    TIWLAN: 76.824100: CHIP VERSION... set 1273 chip top registers
    TIWLAN: 76.827345: Working on a 1273 PG 2.0 board.
    TIWLAN: 76.827630: Starting to process NVS...
    TIWLAN: 76.827715: No Nvs, Setting default MAC address
    TIWLAN: 76.827780: pHwInit->uEEPROMCurLen: 1c
    TIWLAN: 76.827840: ERROR: If you are not calibating the device, you will soon get errors !!!
    TIWLAN: 76.829323: Chip ID is 0x4030111.
    TIWLAN: 76.839445: Starting to download firmware...
    TIWLAN: 76.944110: Starting to download firmware...
    TIWLAN: 76.970573: Starting to download firmware...
    TIWLAN: 76.971719: Starting to download firmware...
    TIWLAN: 76.981062: Starting to download firmware...
    TIWLAN: 76.986043: Starting to download firmware...
    TIWLAN: 76.987949: Finished downloading firmware.
    TIWLAN: 76.998871: Firmware running.
    TIWLAN: 77.020791: 
    TIWLAN: 77.020890: --------------------------------------------------------------------
    TIWLAN: 77.020974: Driver Version  : WiLink_Driver_6.1.0.1.149
    TIWLAN: 77.021036: Firmware Version: Rev 6.1.0.1.349
    TIWLAN: 77.021108: Station ID      : 08-00-28-12-34-56
    TIWLAN: 77.021166: --------------------------------------------------------------------
    TIWLAN: 77.021238: 
    TIWLAN: 77.098338: Interrogate TX/RX parameters
    TIWLAN: 107.604228: mainSecSm               , SM:MainSec SM: config, authProtocol = 3, keyExchangeProtocol=1, unicastSuite=2, broadcastSuite=2
    TIWLAN: 107.604517: mainSecSm               , SM:MAIN_SEC_SM: successful configuration SM
    TIWLAN: 107.833900: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 107.839816: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 107.845966: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 108.166376: mainSecSm               , SM:MainSec SM: config, authProtocol = 3, keyExchangeProtocol=1, unicastSuite=2, broadcastSuite=2
    TIWLAN: 108.166657: mainSecSm               , SM:MAIN_SEC_SM: successful configuration SM
    TIWLAN: 108.198638: openAuthSm              , SM:OPEN_AUTH_SM: DEBUG Authentication status is 0 
    TIWLAN: 108.204093: assocSM                 , SM:ASSOC_SM: DEBUG Success associating to AP 
    TIWLAN: 108.204666: assocSM                 , SM:ASSOC_SM: DEBUG - Association Information Get:  
    TIWLAN: 108.204855: assocSM                 , SM:ASSOC_SM: DEBUG - Association Information Get:  
    TIWLAN: 108.205254: mainSecKeysOnly         , SM:MAIN_SEC_SM: mainSecKeysOnly_StartIdle...
    TIWLAN: 139.214253: mainSecKeysOnly         , SM:MAIN_SEC_SM: mainSecKeysOnly_KeysCompleteAuthenticated...
    TIWLAN: 139.229521: connInfra               , CONSOLE:************ NEW CONNECTION ************
    TIWLAN: 139.229672: ************ NEW CONNECTION ************
    TIWLAN: 139.229754: siteMgr                 , CONSOLE:-- BSSID = 0-18-e7-e9-49-5e
    TIWLAN: 139.229859: -- SSID  = DLINK_TEST 
    TIWLAN: 139.229921: -- BSSID = 0-18-e7-e9-49-5e
    TIWLAN: 139.229978: connInfra               , CONSOLE:****************************************
    TIWLAN: 139.230288: ****************************************
    TIWLAN: 169.020575: mainSecKeysOnly         , SM:MAIN_SEC_SM: mainSecKeysOnly_StopAuthorized...
    TIWLAN: 169.120107: wlanDrvIf_Release()
    TIWLAN: 186.980345: wlanDrvIf_Open()
    TIWLAN: 187.352437: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 187.358431: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 187.364622: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 187.654683: mainSecSm               , SM:MainSec SM: config, authProtocol = 3, keyExchangeProtocol=1, unicastSuite=2, broadcastSuite=2
    TIWLAN: 187.654966: mainSecSm               , SM:MAIN_SEC_SM: successful configuration SM
    TIWLAN: 187.686687: openAuthSm              , SM:OPEN_AUTH_SM: DEBUG Authentication status is 0 
    TIWLAN: 187.695954: assocSM                 , SM:ASSOC_SM: DEBUG Success associating to AP 
    TIWLAN: 187.696516: assocSM                 , SM:ASSOC_SM: DEBUG - Association Information Get:  
    TIWLAN: 187.696707: assocSM                 , SM:ASSOC_SM: DEBUG - Association Information Get:  
    TIWLAN: 187.697090: mainSecKeysOnly         , SM:MAIN_SEC_SM: mainSecKeysOnly_StartIdle...
    TIWLAN: 207.690265: mainSecKeysOnly         , SM:MAIN_SEC_SM: mainSecKeysOnly_StopStart...
    TIWLAN: 208.003380: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 208.015512: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 209.314582: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 209.495426: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 209.504450: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 209.507267: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 212.017795: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 212.023829: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 212.029682: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 215.569196: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 215.575190: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 215.582986: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 220.151265: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 220.157120: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 220.164079: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 228.762826: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 228.768574: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 228.774791: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 245.343571: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 245.349418: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 245.355601: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 245.645955: mainSecSm               , SM:MainSec SM: config, authProtocol = 3, keyExchangeProtocol=1, unicastSuite=2, broadcastSuite=2
    TIWLAN: 245.646232: mainSecSm               , SM:MAIN_SEC_SM: successful configuration SM
    TIWLAN: 245.678074: openAuthSm              , SM:OPEN_AUTH_SM: DEBUG Authentication status is 0 
    TIWLAN: 245.684336: assocSM                 , SM:ASSOC_SM: DEBUG Success associating to AP 
    TIWLAN: 245.684901: assocSM                 , SM:ASSOC_SM: DEBUG - Association Information Get:  
    TIWLAN: 245.685094: assocSM                 , SM:ASSOC_SM: DEBUG - Association Information Get:  
    TIWLAN: 245.685486: mainSecKeysOnly         , SM:MAIN_SEC_SM: mainSecKeysOnly_StartIdle...
    TIWLAN: 285.680257: mainSecKeysOnly         , SM:MAIN_SEC_SM: mainSecKeysOnly_StopStart...
    TIWLAN: 285.895346: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 285.897001: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 286.063459: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 286.070160: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 286.075557: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 287.476403: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 287.479464: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 287.645350: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 287.653037: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 287.657206: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 290.197285: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 290.203318: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 290.209136: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 293.809274: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 293.815339: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 293.823017: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 298.272077: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 298.279035: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 298.285217: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 306.733827: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 306.739649: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 306.745725: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 323.287624: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 323.292763: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 323.296721: mlmeParser              , SM:MLME_PARSER: recieved PROBE_RESPONSE message 
    TIWLAN: 323.616813: mainSecSm               , SM:MainSec SM: config, authProtocol = 3, keyExchangeProtocol=1, unicastSuite=2, broadcastSuite=2
    TIWLAN: 323.617091: mainSecSm               , SM:MAIN_SEC_SM: successful configuration SM
    TIWLAN: 323.648708: openAuthSm              , SM:OPEN_AUTH_SM: DEBUG Authentication status is 0 
    TIWLAN: 323.654102: assocSM                 , SM:ASSOC_SM: DEBUG Success associating to AP 
    TIWLAN: 323.654678: assocSM                 , SM:ASSOC_SM: DEBUG - Association Information Get:  
    TIWLAN: 323.654865: assocSM                 , SM:ASSOC_SM: DEBUG - Association Information Get:  
    TIWLAN: 323.655261: mainSecKeysOnly         , SM:MAIN_SEC_SM: mainSecKeysOnly_StartIdle...
    TIWLAN: 354.655442: mainSecKeysOnly         , SM:MAIN_SEC_SM: mainSecKeysOnly_KeysCompleteAuthenticated...
    TIWLAN: 354.669388: connInfra               , CONSOLE:************ NEW CONNECTION ************
    TIWLAN: 354.669543: ************ NEW CONNECTION ************
    TIWLAN: 354.669625: siteMgr                 , CONSOLE:-- BSSID = 0-18-e7-e9-49-5e
    TIWLAN: 354.669731: -- SSID  = DLINK_TEST 
    TIWLAN: 354.669793: -- BSSID = 0-18-e7-e9-49-5e
    TIWLAN: 354.669849: connInfra               , CONSOLE:****************************************
    TIWLAN: 354.669943: ****************************************
    

    4477.Router_Server_Failure_then_Success.txt

    7266.Device_Router_Failure_then_Success.txt

  • Hi Siva,

    Thank you for your detailed answers.

    * You are using very old driver/FW version - The M6 driver. TI has MCP 2.5x driverset which solve a lot of issues.

    Regarding the first disconnection - packet #1486, #2066, 2068, 2229:

    The fist EAP-Request was ACKed by the FW but this is a classic race-condition between supplicant and connection state machine. When the driver completed the negotiation, the data path dropped the packet. Usually (and by spec if i'm not mistaken), APs retransmit the first EAPOL every seconds to over-come this issue.

    Eventually Cisco retransmit this EAP at packet 2066, after 30 seconds (!), the supplicant send identity EAPOL back and the AP don't answer.

    Please check whether there is a FW update for your Cisco1252. seems like AP FW issue

    The second connection looks good.

    - Elad.

  • Hi Elad

    Thank you. 

    We will look into availability of any new firmware for the router. 

    I searched the TI connectivity wiki for MCP2.5x driverset and I could not find it. Is this a Proprietary driverset by TI or is it released as Opensource driver. 

    Interestingly, we made one observation today.. 

    When we invoke the WPA_Supplicant with debug option, we do not see this connection issue. That is, when we invoke the WPA supplicant as below

    wpa_supplicant -Dwext -itiwlan0 -c supplicant_conf_file  -d

    Do you think that this has some effect on the timing and hence avoiding the race-condition.

     

    Regards

    Siva

  • Hi Siva,

    I'm not sure who you need to approach to get MCP driver. I got it from TI directly.

    I don't think there is any connection between wpa-supplicant running in debug mode, except maybe slow down the driver a little bit. I do believe that the race-condition exists and will always be there. It's something in the protocol that not well defined. 

    - Elad