NDIS Intermediate Driver for 802.11

"Maxim S. Shatskih" <> wrote in message news:<#>...
> 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


Thanx for the answer Mr. Andy.

I missed one line from the Registry given by you
""ProtocolsToBindTo"= multi_sz:"PPP" under passthru.

As Mr. Shatskih says "if it is encrypted, then its a problem.".

Well, I will take one STEP at time.

As far wireless I bound it as 802.3 and I read few docs. Its say the
the Driver below exposes 802.3 to the upper layers like IM, NDIS.sys
etc and they have a layer that converts to 802.11 and pass it their
MAC driver. Sounds good.

But I still get some Inavlid packet error when I pass on 802.3
packets, Which I will look into later and post question. I did
Analyse(Dump) the packet I got, and it say IPv6 and so on.

The problem seems to be, "If you plug in the Wireless Card(eg.
Linksys), it usually pops a dialog and asks for which network you want
to connect to(if nothing is configured). For some reason Linksys name
doesn't show up. It shows NetGear, Empty ones. Once I got "linksys"
and I chose it and I got 802.3 proper packets. But never could
reproduce it." I had configured a network path to connect to our work
thru 802.11 (NO VPN). If I don't have MY driver, the card picks that
easily.

Hopefully I will reach some "Useful" point to post further questions.

Thanx again.