none
The WPS IE OUI/OUI type 00-50-F2-04 it is automatically changed to 01-00-01-00 on Win10 OS. RRS feed

  • Question

  • We want to add WPS IE content in Probe Request/ Associate Request packet when doing WPS in Win10.

     

    We set WPS IE to Probe Request/ Associate Request packet method:

    WPS Application set WPS IE àLightweight Filter driver àWDI for Win10 àNdis driver (set WPSIE to Probe Request/ Associate Request packet)

    We trace to NdisFOidRequest function in the last step of NDIS LWF driver , the setting buffer is correct .

    But the driver receive the incorrect the WPS IE OUI & OUI type content 01-00-01-00, all buffer content is only changed 4 bytes in the middle, it is the special WPS IE OUI & OUI type on Win10.

     

    Example the setting buffer:

    { 0x1a, 0x00, //IE length (2byte)

    0xdd,              //Element ID

    0x18,              //Length

      0x00, 0x50, 0xF2, 0x04, //OUI

      0x10, 0x4a, 0x00, 0x01, 0x10, //Version

      0x10, 0x3a, 0x00, 0x01, 0x01, //Request type = Enrollee , open 802.1x

      0x10, 0x49, 0x00, 0x06, 0x00, 0x37, 0x2A, 0x00, 0x01, 0x20 //Vendor Extension , WPS2.0

     };

     

    According to the content in Win7/Win8.1 OS is correct, discussing with chip vendor, we guess that the OUI & OUI type is changed maybe from Win10WDI.

    Would you please help to see why WPS IE OUI & OUI type 00-50-F2-04 is changed to 01-00-01-00 on Win10, thanks a lot.


    • Edited by Joanne-Lee Tuesday, June 28, 2016 8:39 AM
    Tuesday, June 28, 2016 8:34 AM

All replies

  • Are you writing your own LWF driver? Which OID does your LWF send?  LWFs are not allowed to issue their own OID_DOT11_SCAN_REQUEST commands. All state-changing OIDs must originate with the NWIFI filter, so that the state doesn't get out of sync.
    Wednesday, June 29, 2016 6:20 PM