NDIS Intermediate Driver for 802.11

Hello

Thank you for reading this message.

I am developing an Intermediate Driver for 802.11.
I have problem Binding to the Underlying Miniport.

The NdisOpenAdapter() funtion takes in a Array of supported mediums. I
have given the following mediums array to this function.

1. NdisMedium802_3
2. NdisMedium802_5
3. NdisMedium802_11

I have a 802.11 card inserted (Linksys card), but the NdisOpenAdapter
is binding to NdisMedium802_3 medium. It doesn't recognize
NdisMedium802_11. When I tried to Forward NDIS packets from the upper
layer i get Inavlid packet error.

In otherwords, HOW DO WE BIND TO 802_11 miniport drivers as an
Intermediate driver?

The NdisOpenAdapter document doesn't specify 802_11 support, BUT
NDIS.H does have this medium supported.

I am developing this IM driver in Pocket PC. I did look at the
PASSTHRU sample.

ANY HELP is WELCOME and really appreciated.

Thank you
Ganesan

All 802.11 miniports in Windows XP emulate 802.3. So, you will only see
802.3 headers and only 802.3 miniports. All 802.11 miniports report
NdisMedium802_3 to OID_GEN_MEDIA_SUPPORTED and OID_GEN_MEDIA_IN_USE and
then NdisPhysicalMediumWirelessLan to OID_GEN_PHYSICAL_MEDIUM.

In Longhorn, this is likely to change.

Bryan S. Burgin


This posting is provided "AS IS" with no warranties, and confers no rights.

> In otherwords, HOW DO WE BIND TO 802_11 miniport drivers as an
> Intermediate driver?

Same way as to Ethernet. Just ignore that they are wireless.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation

http://www.storagecraft.com

Hello Ganisan,

I note that neither of the respondees took into account
that you are developing on PocketPC.

I hope you don't consider this Spam, but we provide a
toolkit that lets you have IM functionality without
developing an IM.

Our DNE product is a transparent NDIS framework with a
consistent API for plugins that you develop. It
facilitates capture, modification, insertion, deletion,
and redirection of packets across all NDIS-supported LAN
and WAN devices. On PocketPC, it does make WAN
interfaces, bluetooth, and even the cradle transparent to
the plugin.

If you use DNE, you are protected from OS changes,
service packs, new device drivers and NDIS devices,
compatibility with other software products and IMs, and
new versions of Windows/PocketPC/CE (and Solaris, Linux,
etc).

With literally millions of copies installed, DNE is the
most widely used NDIS 'shim.' Even Microsoft and Cisco
have licensed it from us for use in their networking
products. Aside from providing a great base to develop
sophisticated networking products (our customers have
developed routers, switches, bridges, QoS schedulers,
high speed packet captures, multicast, IPSEC, TCP
spoofing, PPPoE, L2TP and much more), it is extremely
fast, supports all adapter types (WAN and LAN, WLAN, USB,
etc), and enables you to write one piece of code that
will run on all supported Operating Systems (Win95, 98,
ME, NT, 2K, XP, 2003, Linux, Solaris, WindowsCE/PocketPC,
etc). It even provides a consistent cross-platform
interface to user space and the registry.

In the WinCE/PocketPC environment, it lets you develop
and debug on Windows, then just recompile to execute and
work on WinCE/PocketPC. This is a huge advantage over
trying to debug solely on the PocketPC.

Also, if you've ever tried to get through the WHQL
process with an intermediate driver, you know that it is
a long and costly process. Since DNE is already signed
by Microsoft, all plugins run under DNE's signature.
Thus, you can save thousands of dollars on driver signing
alone.

We also have a wide variety of plugins already available
which can be provided as a base for any products you're
thinking of, and if necessary, we can develop or port
your drivers for you. We also supply WAN and LAN virtual
adapters (DCHP spoofing on the LAN VA) with DNE.

Let me know if you have any interest. The product is
more fully described at
www.deterministicnetworks.com/Products/dne.asp.


Steve


>-----Original Message-----
>Hello
>
>Thank you for reading this message.
>
>I am developing an Intermediate Driver for 802.11.
>I have problem Binding to the Underlying Miniport.
>
>The NdisOpenAdapter() funtion takes in a Array of
supported mediums. I
>have given the following mediums array to this function.
>
>1. NdisMedium802_3
>2. NdisMedium802_5
>3. NdisMedium802_11
>
>I have a 802.11 card inserted (Linksys card), but the
NdisOpenAdapter
>is binding to NdisMedium802_3 medium. It doesn't
recognize
>NdisMedium802_11. When I tried to Forward NDIS packets
from the upper
>layer i get Inavlid packet error.
>
>In otherwords, HOW DO WE BIND TO 802_11 miniport drivers
as an
>Intermediate driver?
>
>The NdisOpenAdapter document doesn't specify 802_11
support, BUT
>NDIS.H does have this medium supported.
>
>I am developing this IM driver in Pocket PC. I did look
at the
>PASSTHRU sample.
>
>ANY HELP is WELCOME and really appreciated.
>
>Thank you
>Ganesan
>.
>

> I note that neither of the respondees took into account
> that you are developing on PocketPC.

This is just not a Pocket PC/Windows CE forum.
microsoft.public.windowsce.platbuilder is more suitable.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation

http://www.storagecraft.com

"Maxim S. Shatskih" <> wrote in message news:<>...
> > I note that neither of the respondees took into account
> > that you are developing on PocketPC.
>
> This is just not a Pocket PC/Windows CE forum.
> microsoft.public.windowsce.platbuilder is more suitable.


Well

Thanx A LOT again.

All or Most my problems are with the registry creation and where the
driver should be positioned? and what packets am I getting?

Nothing complex about these(since its an IM), but very vague hierarchy
of whos who?. ** I agree with Mr. Shatskih. he is right **

The four I am working on.

1. 802_3 - simple - Bind with 803_medium, create a registry under
\\comm\\802_3_Device1\\Parms\\MyDriver. I get 802_3 pakets.

2. Irda - simple too. Bind with Irda_medium, Create a registry under
\\comm\\IrSir1\\Parms\\MyDriver. I get IrLap pakets.

For these 2 I can analyse what I want.


3. WAN - Windows CE 3.0 supports(has) NDISWAN that sits under
PPP(TCP/IP over PPP) and over AsyncMac.
a. Bind with WAN_medium and Alter some send and receives. I have
writen the code (simple changes to passthru).
b. But What regitry entires to create, and where? AND what packets
will I get? (Should be PPP!!!)
(I created registry under AsyncMac, but the driver(ProtocolBind)
is called for all (like PPP, PPTP, L2TP, AsynMac etc.) and thus HALTS.

Just the question of Who is doing what? Well I don't know right
now.

4. Wireless LAN (802_11).
a. Bind with 802_11_medium. But gets bound to 802_3(its OK, doesn't
halt).
b. Created registry under \\comm\\802_11_Device1\\Parms\\MyDrive
c. Binds but Send fails. Do I construct 802_11 packets from 802_3
and send it below? (Of course first I will query to make sure the
medium I get from below is 802_11). OR its the otherway around (802_11
to 802_3).

Anyway, sorry to post these questions here since this is first time
ever I am posting questions in WEB. Usually combinations and docs were
enough.
I will TRY to POST it in Win CE(PPC) forum BUT HELP is very less over
there.

Thanx
Ganesan

> 3. WAN - Windows CE 3.0 supports(has) NDISWAN that sits under
> PPP(TCP/IP over PPP) and over AsyncMac.

No.

WinCE 3.0 and 4.2 (WM 2002 and 2003) does not support IM filtering of PPP.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation

http://www.storagecraft.com

Guys,

Sorry to be salesy on this, but that's what DNE does. We
do support IM (actually our plugin) filtering of PPP on
all devices and all Windows OSs including CE and PocketPC.


Steve
>-----Original Message-----
>> 3. WAN - Windows CE 3.0 supports(has) NDISWAN that
sits under
>> PPP(TCP/IP over PPP) and over AsyncMac.
>
>No.
>
>WinCE 3.0 and 4.2 (WM 2002 and 2003) does not support IM
filtering of PPP.
>
>--
>Maxim Shatskih, Windows DDK MVP
>StorageCraft Corporation
>
>http://www.storagecraft.com
>
>
>.
>

For filtering WAN packets under PPC2002 the following registry
settings work for me. I see PPP packets ...

[HKEY_LOCAL_MACHINE\Comm\passthru]
"DisplayName"="passthru client"
"Group"="NDIS"
"ImagePath"="passthru.dll"

[HKEY_LOCAL_MACHINE\Comm\passthru\Linkage]
"Route"=multi_sz:"passthru1"

[HKEY_LOCAL_MACHINE\Comm\passthru1]
"DisplayName"="passthru client"
"Group"="NDIS"
"ImagePath"="passthru.dll"

[HKEY_LOCAL_MACHINE\Comm\passhtru1\Parms]
"BusNumber"=dword:0
"BusType"=dword:0
"HomeAdapter"=dword:1
"ProtocolsToBindTo"= multi_sz:"PPP"


[HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms]
"ProtocolsToBindTo"= multi_sz:"passthru"

[HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms\passthru]
"UpperBindings"=multi_sz:"passthru1"


Wireless LAN is the same as basic 802_3 stuff. Same client, same
registry settings (but on different adapter obviously)

Andy


> Well
>
> Thanx A LOT again.
>
> All or Most my problems are with the registry creation and where the
> driver should be positioned? and what packets am I getting?
>
> Nothing complex about these(since its an IM), but very vague hierarchy
> of whos who?. ** I agree with Mr. Shatskih. he is right **
>
> The four I am working on.
>
> 1. 802_3 - simple - Bind with 803_medium, create a registry under
> \\comm\\802_3_Device1\\Parms\\MyDriver. I get 802_3 pakets.
>
> 2. Irda - simple too. Bind with Irda_medium, Create a registry under
> \\comm\\IrSir1\\Parms\\MyDriver. I get IrLap pakets.
>
> For these 2 I can analyse what I want.
>
>
> 3. WAN - Windows CE 3.0 supports(has) NDISWAN that sits under
> PPP(TCP/IP over PPP) and over AsyncMac.
> a. Bind with WAN_medium and Alter some send and receives. I have
> writen the code (simple changes to passthru).
> b. But What regitry entires to create, and where? AND what packets
> will I get? (Should be PPP!!!)
> (I created registry under AsyncMac, but the driver(ProtocolBind)
> is called for all (like PPP, PPTP, L2TP, AsynMac etc.) and thus HALTS.
>
> Just the question of Who is doing what? Well I don't know right
> now.
>
> 4. Wireless LAN (802_11).
> a. Bind with 802_11_medium. But gets bound to 802_3(its OK, doesn't
> halt).
> b. Created registry under \\comm\\802_11_Device1\\Parms\\MyDrive
> c. Binds but Send fails. Do I construct 802_11 packets from 802_3
> and send it below? (Of course first I will query to make sure the
> medium I get from below is 802_11). OR its the otherway around (802_11
> to 802_3).
>
> Anyway, sorry to post these questions here since this is first time
> ever I am posting questions in WEB. Usually combinations and docs were
> enough.
> I will TRY to POST it in Win CE(PPC) forum BUT HELP is very less over
> there.
>
> Thanx
> Ganesan

Use VPN's encryption - and you will see the encrypted packets. Useless for
a firewall.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation

http://www.storagecraft.com

"Andy" <> wrote in message
news: m...
> For filtering WAN packets under PPC2002 the following registry
> settings work for me. I see PPP packets ...
>
> [HKEY_LOCAL_MACHINE\Comm\passthru]
> "DisplayName"="passthru client"
> "Group"="NDIS"
> "ImagePath"="passthru.dll"
>
> [HKEY_LOCAL_MACHINE\Comm\passthru\Linkage]
> "Route"=multi_sz:"passthru1"
>
> [HKEY_LOCAL_MACHINE\Comm\passthru1]
> "DisplayName"="passthru client"
> "Group"="NDIS"
> "ImagePath"="passthru.dll"
>
> [HKEY_LOCAL_MACHINE\Comm\passhtru1\Parms]
> "BusNumber"=dword:0
> "BusType"=dword:0
> "HomeAdapter"=dword:1
> "ProtocolsToBindTo"= multi_sz:"PPP"
>
>
> [HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms]
> "ProtocolsToBindTo"= multi_sz:"passthru"
>
> [HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms\passthru]
> "UpperBindings"=multi_sz:"passthru1"
>
>
> Wireless LAN is the same as basic 802_3 stuff. Same client, same
> registry settings (but on different adapter obviously)
>
> Andy
>
>
> > Well
> >
> > Thanx A LOT again.
> >
> > All or Most my problems are with the registry creation and where the
> > driver should be positioned? and what packets am I getting?
> >
> > Nothing complex about these(since its an IM), but very vague hierarchy
> > of whos who?. ** I agree with Mr. Shatskih. he is right **
> >
> > The four I am working on.
> >
> > 1. 802_3 - simple - Bind with 803_medium, create a registry under
> > \\comm\\802_3_Device1\\Parms\\MyDriver. I get 802_3 pakets.
> >
> > 2. Irda - simple too. Bind with Irda_medium, Create a registry under
> > \\comm\\IrSir1\\Parms\\MyDriver. I get IrLap pakets.
> >
> > For these 2 I can analyse what I want.
> >
> >
> > 3. WAN - Windows CE 3.0 supports(has) NDISWAN that sits under
> > PPP(TCP/IP over PPP) and over AsyncMac.
> > a. Bind with WAN_medium and Alter some send and receives. I have
> > writen the code (simple changes to passthru).
> > b. But What regitry entires to create, and where? AND what packets
> > will I get? (Should be PPP!!!)
> > (I created registry under AsyncMac, but the driver(ProtocolBind)
> > is called for all (like PPP, PPTP, L2TP, AsynMac etc.) and thus HALTS.
> >
> > Just the question of Who is doing what? Well I don't know right
> > now.
> >
> > 4. Wireless LAN (802_11).
> > a. Bind with 802_11_medium. But gets bound to 802_3(its OK, doesn't
> > halt).
> > b. Created registry under \\comm\\802_11_Device1\\Parms\\MyDrive
> > c. Binds but Send fails. Do I construct 802_11 packets from 802_3
> > and send it below? (Of course first I will query to make sure the
> > medium I get from below is 802_11). OR its the otherway around (802_11
> > to 802_3).
> >
> > Anyway, sorry to post these questions here since this is first time
> > ever I am posting questions in WEB. Usually combinations and docs were
> > enough.
> > I will TRY to POST it in Win CE(PPC) forum BUT HELP is very less over
> > there.
> >
> > Thanx
> > Ganesan