NDIS5 to 6 porting Vista - OID_DOT11 are not working Please help

NTDEV
1

Hi,

I am porting protocol driver to NDIS5 to NDIS6 for Vista.

In Vista OID_802_11 OIDs are phased out and new OIDs are introduced are OID_DOT11.

My problem is Some of the OID_DOT11s are not working, whenever i query it returns with error code “31 - A device attached to the system is not functioning.”

I added OID_DOT11 oids in protocol driver Valid OID list, still problem exists.

Some of the OIDs are working for Ex:

OID_DOT11_MAC_ADDRESS

OID_DOT11_ENUM_ASSOCIATION_INFO

OID_DOT11_DESIRED_SSID_LIST

but the main OIDs Which i need are not working which are as follows

OID_DOT11_RESET_REQUEST

OID_DOT11_SCAN_REQUEST

OID_DOT11_ENUM_BSS_LIST

and i am unable to find alternative OIDs for the following OIDs forOID_802_11

OID_802_11_ADD_WEP - Set

OID_802_11_ADD_KEY - Set

OID_802_11_REMOVE_KEY - Set

OID_802_11_ENCRYPTION_STATUS - Set

OID_802_11_PRIVACY_FILTER - Set

OID_802_11_RSSI - Query

OID_802_11_BSSID_LIST - Query

OID_802_11_INFRASTRUCTURE_MODE - Set

Please let me know whether support of these OIDs are Vendor dependent.

I used PCAUSA Ndisscope application to test the OIDS, which shows all the OID_DOT11 are supported when i actually use them it returns with error code 31.

Please help me whether any alternative is there for the above OIDs or the vendor has to provide the support for the OIDs.

Thanks in advance

Regards,

Rathan Raj

2

The alternative is to use the documented *USERMODE* extensions to the WLAN
client. You can even use a subset of that API on XP SP3.

Why do you think you need to issue 802.11 related OIDs to an adapter on NT6?

Good Luck,
Dave Cattley
Consulting Engineer
Systems Software Development

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@hotmail.com
Sent: Wednesday, December 17, 2008 10:58 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] NDIS5 to 6 porting Vista - OID_DOT11 are not working Please
help

Hi,

I am porting protocol driver to NDIS5 to NDIS6 for Vista.

In Vista OID_802_11 OIDs are phased out and new OIDs are introduced are
OID_DOT11.

My problem is Some of the OID_DOT11s are not working, whenever i query it
returns with error code “31 - A device attached to the system is not
functioning.”

I added OID_DOT11 oids in protocol driver Valid OID list, still problem
exists.

Some of the OIDs are working for Ex:

OID_DOT11_MAC_ADDRESS

OID_DOT11_ENUM_ASSOCIATION_INFO

OID_DOT11_DESIRED_SSID_LIST

but the main OIDs Which i need are not working which are as follows

OID_DOT11_RESET_REQUEST

OID_DOT11_SCAN_REQUEST

OID_DOT11_ENUM_BSS_LIST

and i am unable to find alternative OIDs for the following OIDs
forOID_802_11

OID_802_11_ADD_WEP - Set

OID_802_11_ADD_KEY - Set

OID_802_11_REMOVE_KEY - Set

OID_802_11_ENCRYPTION_STATUS - Set

OID_802_11_PRIVACY_FILTER - Set

OID_802_11_RSSI - Query

OID_802_11_BSSID_LIST - Query

OID_802_11_INFRASTRUCTURE_MODE - Set

Please let me know whether support of these OIDs are Vendor dependent.

I used PCAUSA Ndisscope application to test the OIDS, which shows all the
OID_DOT11 are supported when i actually use them it returns with error code
31.

Please help me whether any alternative is there for the above OIDs or the
vendor has to provide the support for the OIDs.

Thanks in advance

Regards,

Rathan Raj

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

3

Hi David,

I am porting existing supplicant to Vista. currently in XP code it issues OID_802_11 Oids.
In Vista OID_802_11 are not supported. So i have to issue OID_DOT11 OIDS through my NDIS protocol driver. Problem is I am using D-Link AirPlus G DWL- G630 wireless card which does not support all the OIDs i need to query or set.
So is there any solution for this, or is this the problem of miniport driver. Currently i am trying Wlanapi but wlanapi also does not solve all my needs.

4

Supplicants on Vista are very different story…
The documentation unfortunately isn’t complete,
part of it maybe still is under NDA.

Good luck.
–PA

xxxxx@hotmail.com wrote:

Hi David,

I am porting existing supplicant to Vista. currently in XP code it issues OID_802_11 Oids.
In Vista OID_802_11 are not supported. So i have to issue OID_DOT11 OIDS through my NDIS protocol driver. Problem is I am using D-Link AirPlus G DWL- G630 wireless card which does not support all the OIDs i need to query or set.
So is there any solution for this, or is this the problem of miniport driver. Currently i am trying Wlanapi but wlanapi also does not solve all my needs.

5

> I am porting existing supplicant to Vista.

Yes, I understand *what* you are doing. I want to get you to ask yourself
the question “should you be doing this?”

Vista provides a rich set of mechanisms to extend the WLAN client (from
usermode) which render the creation of third-party ‘supplicants’ (wireless
configuration utilities is what I think you mean here) somewhat moot (and
more precisely, very difficult). What is it about *your* ‘supplicant’ that
you cannot accomplish by simply helping the Vista WLAN client do by calling
its APIs?

Almost everything you can reasonably expect to be able to do using the ‘raw’
OIDs can be controlled from the usermode APIs in a way that does not screw
up everyone else’s experience with using the WiFi connectivity - thus the
creation of the WLAN client and extensibility APIs.

And if you really are building ‘supplicant’ behavior (aka, 802.1x EAPOL
authentication behavior) you should look at the companion extensibility
technology in Vista called EAPHOST.

And after all that, you are truly convinced that you must directly take
control of the WiFi card from Vista, good luck. You are in for a very
challenging activity involving way more than a simple protocol driver bound
to the adapter and nice little usermode service or application talking to
the protocol driver. NT6 is not NT5 where WiFi was an afterthought bolted
on in an expedient way that was easily pushed ‘out of the way’. In NT6,
WiFi is tightly architected into how the network infrastructure operates.
As such, it is a lot more difficult to get Windows to ‘let go’ of a WiFi
adapter. The good news is that for the most part, no ISV should need to do
much more than can be accomplished with the WLAN Client API.

If you are an IHV with your own card, the WLAN IHV Extension API is how you
‘expose’ unique card specific functionality. Since your e-mail address does
not indicate you work for D-LINK (or the chipset vendor that actually
provides the driver for that D-LINK card) nor one of the very few places
where the driver development occurs for these devices, I am guessing you are
trying to support an ISV ‘wifi configuration utility’.

So, time to push back on whomever told you to just port it to Vista. It is
very likely you have a produce management challenge and not a engineering
challenge.

Good Luck,
-Dave

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@hotmail.com
Sent: Wednesday, December 17, 2008 12:06 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] NDIS5 to 6 porting Vista - OID_DOT11 are not working
Please help

Hi David,

I am porting existing supplicant to Vista. currently in XP code it issues
OID_802_11 Oids.
In Vista OID_802_11 are not supported. So i have to issue OID_DOT11 OIDS
through my NDIS protocol driver. Problem is I am using D-Link AirPlus G DWL-
G630 wireless card which does not support all the OIDs i need to query or
set.
So is there any solution for this, or is this the problem of miniport
driver. Currently i am trying Wlanapi but wlanapi also does not solve all my
needs.

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

6

Hi david,
to put it simply i am porting a application in which i require to query / set OIDs to get the information from the driver via ndis6 protocol driver.
this is because i have to say driver scan and get the access point list so that i can associate and authenticate using radius server.

Problem still is the same in Vista new OIDs introduced called OID_DOT11. but the wireless card does not support all the DOT11 oids and OID_802_11 is ruled out because they are deprecated in vista.
I am new to protocol driver development. I ported NDIS5 driver to 6 successfully. It works for wired connection. For wireless It requires that i needs to query/ set using OID_DOT11 OIDs. in which some of the OIDs OID_DOT11_SCAN_REQUEST is not working and returns errror 32 “A device attached to the system is not functioning.” SO i am having question whether miniport support is needed or not. I am not deveoping miniport driver. If any alternatives are there in Vista please can you provide me the links to refer and what technologies are there to proceed further. I found WMI ican be used for query but using wmi we cannot set OIDs. Currently i am following wlanapi. which is also not sufficient to provide the complete feature as provided in OID_802_11. Basically i need to provide alternative api or OIDs for OID_802_11 so that my application works under vista

Thanks

7

Exactly what ‘features’ do you need. You mention only a single OID below
(ODI_DOT11_SCAN_REQUEST) and yet the WLAN Client APIs provide a rich set of
capability to determine the set of SSIDs and BSSIDs within range of the
radio as well as to trigger active scanning.

So again, what is it you think you need? You do not need the ‘complete
feature set of OID_802_11’ you need some higher level description of the
functionality controlled by your application. That is my entire point. You
have to rethink how your applications requirements can be met ‘at a high
level’ by the WLAN API.

Throw out the idea that you have of simply porting a protocol driver and
existing control application which talks legacy OID_802_11 or even thinks it
is going to talk OID_DOT11. Neither of those control surfaces are exposed
outside of the native WiFi infrastructure and most definitely *not* to NDIS
Protocols. Yes, some subset of queries was translated to just make some
WiFi aware network components interoperable but no effective ‘control’ (just
status) is available.

Good Luck,
-Dave

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@hotmail.com
Sent: Wednesday, December 17, 2008 2:12 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] NDIS5 to 6 porting Vista - OID_DOT11 are not working
Please help

Hi david,
to put it simply i am porting a application in which i require to query /
set OIDs to get the information from the driver via ndis6 protocol driver.
this is because i have to say driver scan and get the access point list so
that i can associate and authenticate using radius server.

Problem still is the same in Vista new OIDs introduced called OID_DOT11.
but the wireless card does not support all the DOT11 oids and OID_802_11 is
ruled out because they are deprecated in vista.
I am new to protocol driver development. I ported NDIS5 driver to 6
successfully. It works for wired connection. For wireless It requires that i
needs to query/ set using OID_DOT11 OIDs. in which some of the OIDs
OID_DOT11_SCAN_REQUEST is not working and returns errror 32 “A device
attached to the system is not functioning.” SO i am having question whether
miniport support is needed or not. I am not deveoping miniport driver. If
any alternatives are there in Vista please can you provide me the links to
refer and what technologies are there to proceed further. I found WMI ican
be used for query but using wmi we cannot set OIDs. Currently i am following
wlanapi. which is also not sufficient to provide the complete feature as
provided in OID_802_11. Basically i need to provide alternative api or OIDs
for OID_802_11 so that my application works under vista

Thanks

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

8

Hi David,

In my application currently uses following OIDs in XP i need to provide support for these OIDs in Vista.
We already implemented protocol driver using NDIS wrapper found in DDK folder ndisprot.
These OIDs are used status indication and to set some property to miniport.
We are implementing 802.1x authentication porting from XP to Vista.
In XP These are OIDs are supported -
Note: Q - Query ; S - Set
OID_802_11_BSSID_LIST (Q)
OID_802_11_ASSOCIATION_INFORMATION (Q)
OID_802_11_INFRASTRUCTURE_MODE (S)
OID_802_11_BSSID (S/Q)
OID_802_11_SSID (S/Q)
OID_802_11_ADD_WEP (S)
OID_802_11_ADD_KEY (S)
OID_802_11_REMOVE_KEY (S)
OID_802_11_ENCRYPTION_STATUS (S)
OID_802_11_PRIVACY_FILTER (S)
OID_802_11_RSSI (Q)
OID_DOT11_EXTSTA_CAPABILITY (S/Q) — Working
OID_DOT11_ENABLED_AUTHENTICATION_ALGORITHM (S) — Working
OID_DOT11_SUPPORTED_UNICAST_ALGORITHM_PAIR (Q) — Working

OID_DOT11_RESET_REQUEST (S)
OID_DOT11_SCAN_REQUEST (S)

Power management
OID_DOT11_NIC_POWER_STATE (Q)
OID_DOT11_POWER_MGMT_REQUEST (S)
Total 18 OID needs to be supported

I found some of the alternative OIDs for the above in OID_DOT11
I am not able to find one to one mapping for the following OIDs because eventhough they are supported they are not functioning.
OID_802_11_ADD_WEP (S)
OID_802_11_ADD_KEY (S)
OID_802_11_REMOVE_KEY (S)
OID_802_11_ENCRYPTION_STATUS (S)

for Ex: OID_802_11_BSSID_LIST i have alternative for this is WlanGetNetworkBssList in wlanapi but when queried OID_802_11_BSSID_LIST we get PNDIS_802_11_BSSID_LIST_EX structure data when we extract (PNDIS_WLAN_BSSID_EX)&pBssidList->Bssid[0] we have in PNDIS_WLAN_BSSID_EX a field called Privacy which needs to get information about WEP encryption requirement, i am not able to get that information in wlan api.
I am not able to map OID_802_11_ADD_WEP,OID_802_11_ADD_KEY ,OID_802_11_REMOVE_KEY ,OID_802_11_ENCRYPTION_STATUS
The DOT11 oids not functioning are
OID_DOT11_RESET_REQUEST (S)
OID_DOT11_SCAN_REQUEST (S)
OID_DOT11_POWER_MGMT_REQUEST

Please provide me help in what exactly i need to look into. Whether i completely forget about OIDs, if that is the case then if i use wlanapi then protocol driver we implemented is of no use. we need to change minimal so i am concentrating on OID_DOT11 which are introduced in Vista. I want to know whether vendors provide support for the DOT11 OIDs.
Thanks

9

Try WlanGetAvailableNetworkList(). This is what I mean by ‘think high
level’.

I have. You are apparently not willing to accept that answer yet.

Yeah, we all want ‘minimal change’. Too bad. We don’t all get what we
want. In this case, MSFT made a major change to how WLAN works in Windows
and in general, it was a very good move from the perspective of clamping
down on a fractured ecosystem of incompatible and inconsistent WLAN
experience from multiple vendors that served to confuse the end-user
experience greatly. Now there is truly interoperable and extensible
*infrastructure* in the WLAN world. Get used to it and figure out how to
leverage it because it is here to stay, as best I can tell.

Of course they do. The vendors you speak of, however, are NIC vendors whom
have provided WLAN ExtSta compatible drivers for NDIS6. If they did not
provide such drivers, there NICs would be treated as ‘legacy’ by Vista and
the fallback OID_802_11_xxx behavior would be used. But darn near every
significant WLAN NIC chipset vendor (what, all three of them?) has provided
such drivers for both directly attached and USB attached *current* chipsets
so the point I rather moot.

What you fail to understand (fundamentally) about the architecture in this
case is that those OIDs specify an interface between the *platform*
(NDIS6/WLAN) and the NIC Miniport (IHV provided) and not an interface
exposed to ISVs for their particular use. The WLAN infrastructure is not
a ISV replaceable unit just like NDIS and NDISWAN, and NDISTAPI, and the
myriad other *infrastructure* components that ship with the OS are not ISV
replaceable. OIDs are defined for the private communication between
NDISTAPI and NDIS 4.0 style WAN Miniports too. Yet, they are definitely
*not* intended to be exposed to random protocols bound to WAN Miniports.
Well, just like NDISWAN, WLAN is now core infrastructure with IHV interfaces
and ISV interfaces. The ISV interfaces happen to be in usermode (just like
the RAS APIs).

No matter how much you ask the same question, I can only give the one
answer. Displacing the WLAN infrastructure is not an option to be
considered seriously. Extending it, however, is possible at various IHV and
ISV accessible API surfaces. I stand by my assessment that based on what
you have said you want to do, the WLAN API will meet your *high level* goals
(but not necessarily leverage your legacy code base).

Good Luck,
Dave Cattley
Consulting Engineer
Systems Software Development

10

Hi David,
Thanks for the brief mail.
Currently i am completely proceeding towards Wlan Api. i am trying to query PMKids and for the following OIDs
OID_802_11_ADD_WEP (S) OID_802_11_ADD_KEY (S) OID_802_11_REMOVE_KEY (S) OID_802_11_ENCRYPTION_STATUS (S) i am finding alternative api in Wlanapi.
If you know any info on this can you please share .

Thanks

11

David R. Cattley wrote:

… The WLAN infrastructure is not
a ISV replaceable unit just like NDIS and NDISWAN, and NDISTAPI, and the
myriad other *infrastructure* components that ship with the OS are not ISV
replaceable. OIDs are defined for the private communication between
NDISTAPI and NDIS 4.0 style WAN Miniports too. Yet, they are definitely
*not* intended to be exposed to random protocols bound to WAN Miniports.
Well, just like NDISWAN, WLAN is now core infrastructure with IHV interfaces
and ISV interfaces. The ISV interfaces happen to be in usermode (just like
the RAS APIs).

I haven’t been in this topic for a while, but IIRC,
a “design hole” occured there again.
MS exposed custom EAP add-ins only to IHVs, and left out
providers of hardware-independent solutions.
The ISVs have to lobby each hardware vendor to integrate
their stuff into device driver packages… quite a mess.
Hope to be wrong and hear that this has been solved long ago.

–PA

12

Pavel,

Indeed, there are some holes and I for one lobbied hard to find ways to get
ISV access to some additional aspects of the association and key exchange
processes (alas, rather unsuccessfully).

Indeed only IHVs have good access to the facilities to take over the
association/authentication process through the IHV extension mechanism and
because that is tied to the PnP Device ID it is challenge to get ISV
‘functionality’ tied in at that location. Partnership is the most obvious
way but probably the hardest unless you are a pretty big partner. It is
true that an ‘ISV’ extension would have been a nice feature. Maybe we can
have one in Windows 8.

However, extending EAP is quite straight forward with EAPHOST (it was not
all that onerous with RASEAP but EAPHOST is *much* better). Taking over
the entire EAPOL dialog (as you point out) is presently only something that
is made available to IHV extensions or resorting to serious skullduggery.

There are always things that cannot be done or are hard to get done. If it
were all easy, then, I and many others on this list would be out looking for
alternative livelihoods :slight_smile:

Cheers,
-dave

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Pavel A.
Sent: Thursday, December 18, 2008 2:25 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] NDIS5 to 6 porting Vista - OID_DOT11 are not working
Please help

David R. Cattley wrote:

… The WLAN infrastructure is not
a ISV replaceable unit just like NDIS and NDISWAN, and NDISTAPI, and the
myriad other *infrastructure* components that ship with the OS are not ISV
replaceable. OIDs are defined for the private communication between
NDISTAPI and NDIS 4.0 style WAN Miniports too. Yet, they are definitely
*not* intended to be exposed to random protocols bound to WAN Miniports.
Well, just like NDISWAN, WLAN is now core infrastructure with IHV
interfaces
and ISV interfaces. The ISV interfaces happen to be in usermode (just
like
the RAS APIs).

I haven’t been in this topic for a while, but IIRC,
a “design hole” occured there again.
MS exposed custom EAP add-ins only to IHVs, and left out
providers of hardware-independent solutions.
The ISVs have to lobby each hardware vendor to integrate
their stuff into device driver packages… quite a mess.
Hope to be wrong and hear that this has been solved long ago.

–PA

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

13

Hi David,

Can you please help me, how to set filter that only allows for EAPoL frames using wlan api.
OID_802_11_PRIVACY_FILTER when set with Ndis802_11PrivFilter8021xWEP will set the filter that only allows EAPoL frames in XP, In vista using wlanapi how to set this?

Best Regards,
Rathan Raj

14

Hi David,

I got the answer, It can be set when we do WlanConnect(). There is a field called dwFlags.

I have one more question how we can get the PMKIDS using Wlanapi.
Currently OID_DOT11_PMKID_LIST, using this OID gives me No of PMKIDs but i want to use wlanapi to get the info. Is there any way it can be done using wlanapi.

Best Regards,
Rathan Raj

15

I do not think it is possible to access the PMKIDs from the WLAN API. That
would present a bit of a security risk, would it not? What do you need
access to the PMKIDS for? AFAIK the typical exchange is that the WLAN
Client or IHV Extension determine the PMKIDS through the appropriate
negotiations and the set them into the NICs table. Are you trying to add
some way of negotiating PMKIDS that is not supported by the current WLAN
client? If so, I think that puts you into the area of “ISV” trying to add
and “IHV” extension (alas, the rather gaping hole in the WLAN Client).

You might try taking these questions to the MSDN forums as well. The
‘driver’ content of your solution is probably trending towards zero at this
point and you are likely to find additional expertise on leveraging the WLAN
Api in some of the MSFT public forums.

Good Luck,
Dave Cattley
Consulting Engineer
Systems Software Development

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@hotmail.com
Sent: Monday, December 22, 2008 8:07 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] NDIS5 to 6 porting Vista - OID_DOT11 are not working
Please help

Hi David,

I got the answer, It can be set when we do WlanConnect(). There is a field
called dwFlags.

I have one more question how we can get the PMKIDS using Wlanapi.
Currently OID_DOT11_PMKID_LIST, using this OID gives me No of PMKIDs but i
want to use wlanapi to get the info. Is there any way it can be done using
wlanapi.

Best Regards,
Rathan Raj

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

16

Hi,

I need to query how many PMKIDS are supported for a particular interface.
Using OID_DOT11_PMKID_LIST i am able to query. i want to confirm whether it is possible to get using wlanapi. If not i will stick to OID_DOT11_PMKID_LIST.

Thanks for the help.

Best Regards,
Rathan Raj

17

To know ‘how many are supported’ I would have expected you to use
OID_DOT11_EXTSTA_CAPABILITY and look at the uPMKIDCacheSize field of the
returned DOT11_EXTSTA_CAPABILITY structure. Unfortunately (and again, I
have no idea why you need to know how large the PMKID cache is), that
operational parameter is not available via WlanQueryInterface() nor
WlanGetInterfaceCapability(). Have you tried via WMI?

But really, why do you care how many entries can be placed into the cache?

Cheers,
-dave

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@hotmail.com
Sent: Monday, December 22, 2008 10:08 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] NDIS5 to 6 porting Vista - OID_DOT11 are not working
Please help

Hi,

I need to query how many PMKIDS are supported for a particular interface.
Using OID_DOT11_PMKID_LIST i am able to query. i want to confirm whether it
is possible to get using wlanapi. If not i will stick to
OID_DOT11_PMKID_LIST.

Thanks for the help.

Best Regards,
Rathan Raj

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

18

Hi David,

I need PMKID because application needs it.
I am new to WMI, i will sure try to see how to get information using wmi.
Thanks for the help.

Best Regards,
Rathan Raj

19

To be precise, I don’t expect you to get the PMKIDs from WMI. You said you
needed the cache size. Now you say the application needs the PMKID
mappings. Which is it? And if your application actually wants the keys,
why?

-dave

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@hotmail.com
Sent: Monday, December 22, 2008 11:37 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] NDIS5 to 6 porting Vista - OID_DOT11 are not working
Please help

Hi David,

I need PMKID because application needs it.
I am new to WMI, i will sure try to see how to get information using wmi.
Thanks for the help.

Best Regards,
Rathan Raj

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

20

Hi david,

Even i am confused by your comment.
You said you can use wmi. now you are saying it is not possible.
I need number of PMKIDs to initialize the cache, i never said PMKID mappings.
I need how to get equivalent function in wlanapi for one of the OIDs which is named as OID_DOT11_PMKID_LIST.

anyway i will try to figure it out my self…

If anybody has any info regarding getting No of PMKID please share your experience.

Best Regards,
Rathan Raj