// JP opened flex table

Click to See Complete Forum and Search --> : NDIS Intermediate Driver for 802.11


gxn
October 1st, 2004, 04:08 PM
Hello

Thanx 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.

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

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

Though I am developing this driver in Pocket PC,

ANY HELP is WELCOME and really appreciated.

Thank you
Ganesan

IvanBohannon
October 5th, 2004, 01:45 PM
It depends on the media type that the underlying Linksys driver is returning -- and it looks like its returning 802.3 as the media type, which is fine.

use 802.3 as the media type.

The 802.11 media type came with NDIS 5.1, and your linksys driver for pocket pc is probably Ndis 5.0 i.e. was developed for Win2k.

Any other questions let me know.

gxn
October 6th, 2004, 06:30 PM
Thanx for the reply Mr. IvanBohannon. I appreciate.

I am creating Imtermediate Driver in Windows CE, but Windows 2000 has similar Architeture.

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

The 4 Items I am working on.

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

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

For these 2 items, I AM ABLE TO analyse the packets.


3) WAN - Accroding to docs and DDK diagrams in MSDN (CE 3.0 and 4.2)

Windows CE supports(has) NDISWAN that sits under PPP(TCP/IP over
PPP) and over AsyncMac.
(OR)
Windosoc--> TCP/IP --> PPP --> NDISWAN ---> AsyncMAC --> Serial(or
TAPI and Modem)--->Hardware.


a) Bind with Ndis_WAN_medium and alter some send and receives. I
have writen the code (simple changes to passthru example).
b) I created registry under AsyncMac(\\comm\\AsyncMac1
\\Parms\\MyDriver)

But the driver(ProtocolBind function) is called for all (like
PPP, PPTP, L2TP, AsynMac etc.) and thus HALTS.

QUESTIONS on this item.

aa) Where DOES the IM Driver sit in the above Diagram(flow)??
bb) What regitry entires to create, and where? AND what packets
will I get?


4. Wireless LAN (802_11).

a) Bind with Ndis_802_11_medium. But it gets bound to 802_3(its
OK, doesn't halt).
b) Created registry under \\comm\\802_11_Device1\\Parms\\MyDriver
c) Binds but SendPackets fails (invalid packets).

You mentioned binding to 802_3 is ok.

So, Questions on this item

aa) What packets Am I getting (note, it got bound to 802_3
instead of 802_11) and How do I forward it?
bb) Do I construct 802_11 packets from 802_3 or something like
that?


I AM LOOKING FOR HELP for ITEMS 3 and 4. Any help is welcome.


Thanx much for the patience.
Ganesan

saurabh_8380
March 16th, 2005, 06:33 AM
Hi Ganeshan,
Can you please tell me how your driver got hooked to the 802.3. Can you tell me any way that I am able to trace the packets passed when I try to access any Site through my pocket explorer and the device is connected to desktop via Active Sync.
Also, can you please tell me the packet structure of the IrDA Packet. I am unable to find that.


Thanks,
Saurabh

//JP added flex table