Hi all,
Is it possible to trap some perticular NDIS OID requests at miniport driver level and overide the existing functionality with own custom functionality for the perticular OID and retain all other functionality of the original miniport driver ?
So in perticular that extened functionality will lie at same level as that of existing miniport driver and since the source code of the existing driver is not available the newly implemented functionality will exist as a seperate entity/module.
Are there any APIs avaiable to intercommunicate between the two - the existing miniport driver and the extended functionality ?
Please suggest if any way exits…or will have to write a complete miniport driver for a small functionality change…!!
Regards,
Suraj
Jiyo cricket on Yahoo! India cricket
Yahoo! Messenger Mobile Stay in touch with your buddies all the time.
“Suraj Pavaskar” wrote in message news:xxxxx@ntdev…
Hi all,
Is it possible to trap some perticular NDIS OID requests at miniport driver level and overide the existing functionality with own custom functionality for the perticular OID and retain all other functionality of the original miniport driver ?
So in perticular that extened functionality will lie at same level as that of existing miniport driver and since the source code of the existing driver is not available the newly implemented functionality will exist as a seperate entity/module.
Are there any APIs avaiable to intercommunicate between the two - the existing miniport driver and the extended functionality ?
Please suggest if any way exits…or will have to write a complete miniport driver for a small functionality change…!!
Regards,
Suraj
You can certainly write a NDIS Intermediate filter driver that can filter any NDIS request to query or set information or to send or receive packets.
In particular, you can filter the OID_802_11 faimly of requests and do whatever you want with them. You can, for example, return a completely fake BSSID list of your own invention in response to the OID_802_11_BSSID_LIST query.
However, this does not help at all with the problem you have been asking about for a long time.
You still do not have any way to access the proprietary inner workings of the adapter’s miniport driver or the adapter hardware itself. You must get this essential information from the adapter vendor.
You still cannot modify (speed up) the scan time - because you don’t have any way to fetch it from the real adapter’s miniport.
You still cannot modify fetch native wi-fi packets - because you don’t have any way to fetch them from the real adapter’s miniport.
Sorry.
Thomas F. Divine, Windows DDK MVP
Firstly thank you very much for your kind reply…
Still I’ve sometings playing on my mind…
Sir, if in case I can get the internal details of the adapter hardware, is it possible to implement only the required functionality i.e. a faster scanning functionality in my new miniport driver and use this cutomized miniport driver along with the existing miniport driver ?
So effectively two miniport drivers will exist simultanously and may be my customized driver will be used only for scanning by some perticular application and rest of the time the original driver will be functional.
I have really no idea if this is possible…
Please suggest on this…
Thanks & Regards,
Suraj
“Thomas F. Divine” wrote:
“Suraj Pavaskar” wrote in message news:xxxxx@ntdev…
Hi all,
Is it possible to trap some perticular NDIS OID requests at miniport driver level and overide the existing functionality with own custom functionality for the perticular OID and retain all other functionality of the original miniport driver ?
So in perticular that extened functionality will lie at same level as that of existing miniport driver and since the source code of the existing driver is not available the newly implemented functionality will exist as a seperate entity/module.
Are there any APIs avaiable to intercommunicate between the two - the existing miniport driver and the extended functionality ?
Please suggest if any way exits…or will have to write a complete miniport driver for a small functionality change…!!
Regards,
Suraj
You can certainly write a NDIS Intermediate filter driver that can filter any NDIS request to query or set information or to send or receive packets. In particular, you can filter the OID_802_11 faimly of requests and do whatever you want with them. You can, for example, return a completely fake BSSID list of your own invention in response to the OID_802_11_BSSID_LIST query. However, this does not help at all with the problem you have been asking about for a long time. You still do not have any way to access the proprietary inner workings of the adapter’s miniport driver or the adapter hardware itself. You must get this essential information from the adapter vendor. You still cannot modify (speed up) the scan time - because you don’t have any way to fetch it from the real adapter’s miniport. You still cannot modify fetch native wi-fi packets - because you don’t have any way to fetch them from the real adapter’s miniport. Sorry. Thomas F. Divine, Windows DDK MVP
—
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
---------------------------------
Jiyo cricket on Yahoo! India cricket
Yahoo! Messenger Mobile Stay in touch with your buddies all the time.