none
Wi-Fi Issue RRS feed

  • Question

  • Hi,

    We are seeing a different behavior with respect to Wi-Fi while resuming.

    What are the actual steps or OID's that need to be called when a device comes out of suspend?

    In one scenario the OID's that are called is as given below.

    • OID_802_11_INFRASTRUCTURE_MODE Get BSSType
    • OID_802_11_ENCRYPTION_STATUS
    • OID_802_11_SSID (Previous preferred AP SSID is returned correctly)
    • OID_802_11_BSSID_LIST
    • OID_802_11_BSSID_LIST
    • OID_802_11_BSSID_LIST
    • OID_802_11_BSSID_LIST
    • OID_802_11_INFRASTRUCTURE_MODE Set BSSType:1
    • OID_802_11_SSID
    • TIWLAN: 0.124042: set OID_802_11_SSID |JUNK| SSID Len:32

    In second scenratio the OID's that are called as given below.

    • OID_802_11_BSSID_LIST_SCAN
    • OID_802_11_RSSI
    • OID_802_11_RSSI
    • OID_GEN_MEDIA_CONNECT_STATUS
    • OID_GEN_PHYSICAL_MEDIUM
    • OID_GEN_XMIT_OK
    • OID_GEN_RCV_OK
    • OID_GEN_INIT_TIME_MS
    • OID_GEN_DIRECTED_BYTES_XMIT
    • OID_GEN_DIRECTED_BYTES_RCV
    • OID_GEN_MULTICAST_BYTES_XMIT
    • OID_GEN_MULTICAST_BYTES_RCV
    • OID_GEN_BROADCAST_BYTES_XMIT
    • OID_GEN_BROADCAST_BYTES_RCV
    • OID_GEN_DIRECTED_FRAMES_RCV
    • OID_GEN_RCV_ERROR
    • OID_GEN_XMIT_ERROR
    • OID_GEN_MEDIA_SENSE_COUNTS
    • OID_802_11_AUTHENTICATION_MODE
    • OID_802_11_INFRASTRUCTURE_MODE Get BSSType
    • OID_802_11_ENCRYPTION_STATUS
    • OID_802_11_SSID (Returns SSID Name correctly)
    • OID_802_11_BSSID_LIST
    • No Sites were found
    • OID_802_11_INFRASTRUCTURE_MODE Set BSSType:1
    • OID_802_11_AUTHENTICATION_MODE
    • OID_802_11_ENCRYPTION_STATUS
    • OID_802_11_SSID (Sets with the valid SSID name)
    • OID_802_11_BSSID_LIST
    • OID_802_11_BSSID_LIST
    • OID_802_11_RSSI
    • OID_802_11_BSSID_LIST
    • OID_802_11_BSSID_LIST
    • OID_802_3_CURRENT_ADDRESS
    • OID_802_11_ASSOCIATION_INFORMATION
    • OID_802_3_CURRENT_ADDRESS
    • OID_802_11_ASSOCIATION_INFORMATION
    • OID_802_3_CURRENT_ADDRESS
    • OID_802_11_ADD_KEY
    • OID_802_11_ADD_KEY

    TIWLAN: 0.908922: ************ NEW CONNECTION ************

    TIWLAN: 0.908938: ****************************************

    The issue is in first scenario reconnecting to Wi-FI AP after suspend and resume fails where as in second scenario reconnecting to Wi-Fi AP is success.

    Please do let me know if you have any suggestion to debug this.

    Regards,

    GSR

    Wednesday, October 9, 2013 6:24 AM

All replies

  • Hi,

    Any suggestions. I have cloned NDIS UIO DLL and NET UI. 

    Are there any other components can we clone and see on what basis OID_802_11_SSID is called with JUNK SSID by upper layers?

    Regards,

    GSR

    Friday, October 11, 2013 10:38 AM
  • Hi,

    This seems/is a miniport driver.  OID_802_11_SSID is called based on what you select from NetUI or in case of reassociation/reboot the profile gets stored and selection of SSID is initiated by NDIS.

    You might be required to check what happens when this OID comes in wherein it seems to throw some error message regarding junk SSID. This could also be an attempt to turn on the wifi radio in which case NDIS selects a junk (most likely since it says 32 as size). Once this portion is debugged , the other OIDs will automatically be pushed in and would most likely result in a successful connection.

    You may also post any other logs if possible.

    Regards,

    Balaji.


    • Edited by balajitrv1 Monday, October 14, 2013 5:25 AM
    Monday, October 14, 2013 5:20 AM
  • Hello Balaji,

    Thank You for your time and reply.

    In one of the CE Networking blogs I read that JUNK SSID is sent when it wants to disassociate. I am not aware that to turn Wi-Fi radio on JUNK SSID is sent.

    Also I don't understand in first scenario, the OID starts with OID_802_11_INFRASTRUCTURE_MODE where as in second scenario it starts with more OIDs and the Infrastructure mode OID starts some where in between.

    In scenario 1 the upper layer asks for SSID and it returns the SSID name correctly which is connected to previously. But after few more other OID's it sets SSID with JUNK value.

    Regards,

    GSR

    Tuesday, October 15, 2013 11:56 AM
  • Hi,

    Is the first scenario obtained on a reboot , whereas the second scenario is an initial connection to an AP. 

    Anyways , can you check if any OID is returning failure in the driver.

    After the print of junk , is the driver / NDIS not doing / trying anything?. Typically it should do several connection attempts.

    Regards,

    Balaji.

    Tuesday, October 15, 2013 3:51 PM
  • Hello Balaji,

    Thank You for the reply.

    Both the scenarios are from different  suspend and resume test.

    The NDIS is not trying to connect once it sets with a JUNK SSID.

    We have a third party network connection manager application. So is it possible to remove N/W and dial up connection UI for Wi-Fi?

    When suspend and resume occurs automatic connection to preferred network connection is it performed by WZCSVC?

    Regards,

    GSR


    • Edited by GSRid Wednesday, October 16, 2013 12:33 PM
    Wednesday, October 16, 2013 9:30 AM
  • Hi,

    Are you trying the suspend and resume tests from CTK/CETK. 

    Yes , you can  remove NetUI and related tools. Remove SYSGEN_CONNMC, SYSGEN_CONNMGR2(WEC7) from the build.

    In case of wince 6.0 it is WZCSVC that has the control , whereas in WEC7 it is native wifi architecture and not WZCSVC that manages the wireless adapters and pushes OIDs inside.

    Regards,

    Balaji.

    Thursday, October 17, 2013 7:32 AM
  • Hi Balaji,

    In WinCE 6.0 we are trying to remove the SYSGEN_CONNMC. But as we are using Active Sync over USB N/W UI catalog item is added as dependency. 

    For out test we need to include SYSGEN_AS_BASE and SYSGEN_AS_FILE but wanted to remove SYSGEN_CONNMC in the final image as of now I am trying this but didn't find a way to do that.

    Regards,

    GSR

    Monday, October 21, 2013 9:35 AM