Testing OIDs of NDIS driver

NTDEV
1

Hi,

I want to unit test the OIDs of my NDIS driver. I can easily test the Send,
Receive and ISR routines using some packet generator/analyzer. However I
don’t have direct control over Query and SetInformation’s OIDs.

As we test the IOCTL rotines of a NT driver by a test application, is there
any way to (unit)test the Query and SetInformation functions of a NDIS
driver ?

The NdisTester does offer some help in this area, but I guess we can’t
control what OID to test neither we can pass any parameters.
Please give your comments.

Thanks and Regards,
Abhijit Mirajkar

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

Hello,

What kind is your driver of? If it is miniport one and it is NDIS5.X compatible, you may use WMI features to send set or query OIDs to your driver. All of standard OIDs are registered with WMI. As for example, you can obtain all OID_GEN_VENDOR_DESCRIPTION of installed adapters dumping the WMI instances of MSNdis_VendorDescription class in root\WMI namespace.
If you want to obtain your own defined OIDs, you should provide WMI support to your driver.

Thanks,
Leonid.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of
xxxxx@controlnet.co.in
Sent: Tuesday, December 18, 2001 5:56 AM
To: NT Developers Interest List
Subject: [ntdev] Testing OIDs of NDIS driver

Hi,

I want to unit test the OIDs of my NDIS driver. I can easily test
the Send,
Receive and ISR routines using some packet generator/analyzer. However I
don’t have direct control over Query and SetInformation’s OIDs.

As we test the IOCTL rotines of a NT driver by a test
application, is there
any way to (unit)test the Query and SetInformation functions of a NDIS
driver ?

The NdisTester does offer some help in this area, but I guess we can’t
control what OID to test neither we can pass any parameters.
Please give your comments.

Thanks and Regards,
Abhijit Mirajkar

You are currently subscribed to ntdev as: xxxxx@online.sinor.ru
To unsubscribe send a blank email to xxxxx@lists.osr.comb???.???????&?v?'?ׯj?.n?Qyȩf??]?:.?˛???m??֛???zf???%y?ޞ?^?˛??^r*Lzfެ?…???l??ܢ

3

I believe, if you define custom OIDs, NDIS will register them with WM=
I, so
you don’t need to add WMI support to your miniport, it will be handle=
d
automatically.

Marc Reinig
System Solutions

-----Original Message-----
=46rom: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Leonid Slobodchi=
kov
Sent: Tuesday, December 18, 2001 4:59 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Testing OIDs of NDIS driver

What kind is your driver of? If it is miniport one and it is NDIS5.=
X
compatible,
you may use WMI features to send set or query OIDs to your driver. =
All of
standard OIDs are registered with WMI. As for example, you can obta=
in all
OID_GEN_VENDOR_DESCRIPTION of installed adapters dumping the
WMI instances of MSNdis_VendorDescription class in root\WMI namespa=
ce.
If you want to obtain your own defined OIDs, you should provide WMI
support
to your driver.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of
xxxxx@controlnet.co.in
Sent: Tuesday, December 18, 2001 5:56 AM
To: NT Developers Interest List
Subject: [ntdev] Testing OIDs of NDIS driver

Hi,

I want to unit test the OIDs of my NDIS driver. I can easily test
the Send,
Receive and ISR routines using some packet generator/analyzer. Howe=
ver I
don’t have direct control over Query and SetInformation’s OIDs.

As we test the IOCTL rotines of a NT driver by a test
application, is there
any way to (unit)test the Query and SetInformation functions of a N=
DIS
driver ?

The NdisTester does offer some help in this area, but I guess we ca=
n’t
control what OID to test neither we can pass any parameters.
Please give your comments.

Thanks and Regards,
Abhijit Mirajkar

You are currently subscribed to ntdev as: xxxxx@online.sinor.ru
To unsubscribe send a blank email to
leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.comb- -=E7.-T=83T-=81=81=1C-&=DEv=DA’=
=81=D7=81j=C9Lz)=E2-v=9Cm=E9e?=EBS-=E9=EC=81=81=1C
-&=DE=81=E9=DDi=81Z=9EG=83j)m-W +=E9=EDu=EB=F8=DF^Mv±=81-+

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

4

Hello,

Certainly, you are rigth. Saying about WMI support I mean defining custom OIDs, mapping they to GUIDs by writting a MOF file and filling in an NDIS_GUID structure.

Thanks,
Leonid.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Marc Reinig
Sent: Tuesday, December 18, 2001 10:58 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Testing OIDs of NDIS driver

I believe, if you define custom OIDs, NDIS will register them with WMI, so
you don’t need to add WMI support to your miniport, it will be handled
automatically.

Marc Reinig
System Solutions

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Leonid Slobodchikov
Sent: Tuesday, December 18, 2001 4:59 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Testing OIDs of NDIS driver

> What kind is your driver of? If it is miniport one and it is NDIS5.X
compatible,
> you may use WMI features to send set or query OIDs to your
driver. All of
> standard OIDs are registered with WMI. As for example, you can
obtain all
> OID_GEN_VENDOR_DESCRIPTION of installed adapters dumping the
> WMI instances of MSNdis_VendorDescription class in root\WMI namespace.
> If you want to obtain your own defined OIDs, you should provide WMI
support
> to your driver.

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of
> xxxxx@controlnet.co.in
> Sent: Tuesday, December 18, 2001 5:56 AM
> To: NT Developers Interest List
> Subject: [ntdev] Testing OIDs of NDIS driver
>
>
> Hi,
>
> I want to unit test the OIDs of my NDIS driver. I can easily test
> the Send,
> Receive and ISR routines using some packet generator/analyzer. However I
> don’t have direct control over Query and SetInformation’s OIDs.
>
> As we test the IOCTL rotines of a NT driver by a test
> application, is there
> any way to (unit)test the Query and SetInformation functions of a NDIS
> driver ?
>
> The NdisTester does offer some help in this area, but I guess we can’t
> control what OID to test neither we can pass any parameters.
> Please give your comments.
>
> Thanks and Regards,
> Abhijit Mirajkar
>
> —
> You are currently subscribed to ntdev as: xxxxx@online.sinor.ru
> To unsubscribe send a blank email to
xxxxx@lists.osr.comb- -?.-T?T-??-&?v?'?ׁj?Lz)?-v?m?
e??S-?쁁
-&ށ??i?Z?G?j)m-W +??u???^Mv±?-+

You are currently subscribed to ntdev as: xxxxx@online.sinor.ru
To unsubscribe send a blank email to xxxxx@lists.osr.com???y˫???+.n?+???u?ڲ˛??^r*D???kN???r??zǧu??jy???^j???ׯ??? 0?j?b??(??(