Prev: WDF - how to share interrupt between two driver those are in the same stack?
Next: Avstream Architecture Question
From: Zhou on 20 Feb 2008 09:44
Dear all,

We have completed a Native 802.11 wireless lan miniport driver, which
passed NDISTest6.5 and worked very well.

We plan to implement a proprietary security type, named WAPI. As the
WDK document says, we developed a Native 802.11 IHV extensions DLL to
implement the WAPI security. It works well, but only on BSS networks.

IHV extensions can't support IBSS networks on Vista as the WDK
document says. Unfortunately the WAPI security on IBSS networks is a
very important feature for our products. We MUST implement it on IBSS
networks.

Our objective is to request OIDs and send/receive specified data
frames on IBSS networks.

We have ever developed a protocol driver, just like Winpcap. The
protocol driver is based on the sample ndisprot in WDK. However it
failed to request the OIDs of OID_DOT11_xxx. Other OIDs, such as
OID_802_3_CURRENT_ADDRESS, succeeded, but the corresponding OIDs
handle in the miniport driver hasn't been called.

We consider that the Native 802.11 Intermediate (IM) Driver intercepts
the OIDs. As WDK document says, the IM driver "Exposes its upper
miniport edge as a legacy 802.3 device". Does it mean the IM driver is
supposed to reject the 802.11 OIDs, such as OID_DOT11_xxx?

How should we do? Any advice is welcome.
From: Pavel A. on 21 Feb 2008 13:14
Have you tried "vendor specific" OIDs? (high byte = 0xFF)

--PA

"Zhou" <czzhou(a)gmail.com> wrote in message news:65d0dfcc-4bf0-4ec7-8427-a44b3c4380f5(a)d4g2000prg.googlegroups.com...
> Dear all,
>
> We have completed a Native 802.11 wireless lan miniport driver, which
> passed NDISTest6.5 and worked very well.
>
> We plan to implement a proprietary security type, named WAPI. As the
> WDK document says, we developed a Native 802.11 IHV extensions DLL to
> implement the WAPI security. It works well, but only on BSS networks.
>
> IHV extensions can't support IBSS networks on Vista as the WDK
> document says. Unfortunately the WAPI security on IBSS networks is a
> very important feature for our products. We MUST implement it on IBSS
> networks.
>
> Our objective is to request OIDs and send/receive specified data
> frames on IBSS networks.
>
> We have ever developed a protocol driver, just like Winpcap. The
> protocol driver is based on the sample ndisprot in WDK. However it
> failed to request the OIDs of OID_DOT11_xxx. Other OIDs, such as
> OID_802_3_CURRENT_ADDRESS, succeeded, but the corresponding OIDs
> handle in the miniport driver hasn't been called.
>
> We consider that the Native 802.11 Intermediate (IM) Driver intercepts
> the OIDs. As WDK document says, the IM driver "Exposes its upper
> miniport edge as a legacy 802.3 device". Does it mean the IM driver is
> supposed to reject the 802.11 OIDs, such as OID_DOT11_xxx?
>
> How should we do? Any advice is welcome.


 | 
Pages: 1
Prev: WDF - how to share interrupt between two driver those are in the same stack?
Next: Avstream Architecture Question