Question about porting NDIS 4.0 IPSEC Driver to windows 2000

NTDEV
1

Dear All,
Now I am busy to porting a NT 4.0 NDIS IPSEC Driver
(implemented as a IM
Driver)
to Windows 2000 platform.I have already read the XP
DDK’s passthru sample.
And I know that the inf file for NT 4.0 NDIS driver
must be modified
heavily, but
I don’t know whether the source code also need be
modified and if so how I
can modify it. Thanks.

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

There are several issues that are significantly different:

1.) PnP - These features need to be supported in W2K/WXP>
2.) DeviceIoControl API. If you have such an API on WNT, then it must be
modified to use NdisMRegisterDevice instead you your current method.
3.) It is likely that your BindAdapterHandler will require modification to
use the “UpperBindings” string fetched using NdisReadConfiguration.
4.) There are a myriad of NDIS 5.0 features that must also be considered.

Best bet is to start from the XP DDK sample.

Some potentially useful information may be at
http://www.rawether.net/ndisim - including the release notes.

Good luck,

Thomas F. Divine

----- Original Message -----
From: “darth vader”
To: “NT Developers Interest List”
Sent: Monday, November 05, 2001 10:28 AM
Subject: [ntdev] Question about porting NDIS 4.0 IPSEC Driver to windows
2000

> Dear All,
> Now I am busy to porting a NT 4.0 NDIS IPSEC Driver
> (implemented as a IM
> Driver)
> to Windows 2000 platform.I have already read the XP
> DDK’s passthru sample.
> And I know that the inf file for NT 4.0 NDIS driver
> must be modified
> heavily, but
> I don’t know whether the source code also need be
> modified and if so how I
> can modify it. Thanks.
>

—
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