Re: DOT11_OPERATION_MODE_NETWORK_MONITOR in NDIS 6.0 on Vista

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



You should be able to use the "PCAGizmo" tool to examine OIDs above and below the Microsoft Native Wi-Fi driver. See the URL:

http://pcausa.com/Utilities/PCAGizmo/PCAGizmo.htm

Thomas F. Divine

<toddlange1@xxxxxxxxx> wrote in message news:1184852791.087527.213940@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jul 18, 3:14 pm, "Gianluca Varenni"
<gianluca.vare...@xxxxxxxxxxxxxxxx> wrote:
Are you sure the calls actually get forwarded all the way down to the
atheros driver? I know at least some of the Atheros NDIS6.0 drivers do not
actually deliver the "uncooked" 802.11 frames.

Have a nice day
GV

--
Gianluca Varenni, Windows DDK MVP

CACE Technologieshttp://www.cacetech.com

<toddlan...@xxxxxxxxx> wrote in message

news:1184785230.672299.286600@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

> Hello Smart People,

> In NDIS 6.0, Microsoft added an operational mode called
> DOT11_OPERATION_MODE_NETWORK_MONITOR. It is designed to turn a 802.11
> wireless adapter into a promiscuous capture card. In this mode you
> can set filters to see all raw data and management packets, set
> channel, set frequency, gather statistics, etc.

> I interested in using these new features for the purpose of packet
> analysis in a protocol analyzer. Can these new features be used on
> Vista from within an NDIS protocol driver? It appears they may be
> blocked by Windows when I have tried to set them from within a
> protocol driver. I'm using a current Atheros NDIS 6.0 driver on Vista
> and the calls never make it down to the miniport driver.

> Is this by design to prevent 3rd party application developers from
> using these new features, or I'm I missing something?

> Thanks,

> Todd Lange

The call to set the operational mode NEVER makes it to the Atheros
driver. The call to read the mode does work and will return the
operational mode. Is Windows blocking the call down to the driver?
The Atheros driver has code to process the OID, but it never sees
it.

-Todd


.



Relevant Pages

  • Re: DOT11_OPERATION_MODE_NETWORK_MONITOR in NDIS 6.0 on Vista
    ... Which specific Atheros driver ... Vista from within an NDIS protocol driver? ... The call to set the operational mode NEVER makes it to the Atheros ...
    (microsoft.public.development.device.drivers)
  • Re: DOT11_OPERATION_MODE_NETWORK_MONITOR in NDIS 6.0 on Vista
    ... I know at least some of the Atheros NDIS6.0 drivers do not ... Gianluca Varenni, Windows DDK MVP ... Vista from within an NDIS protocol driver? ... The call to set the operational mode NEVER makes it to the Atheros ...
    (microsoft.public.development.device.drivers)
  • Re: atheros chips dangerous?
    ... Wesley Morgan wrote: ... the Atheros driver is fantastic. ... The driver may be "binary" in some ways, but I think we got the best of both worlds. ... "FOSS" that it gets more peer review need only to look at some of the oldest open source projects around, such as sendmail or XFree/Xorg, to realize that security problems can persist for years without being discovered. ...
    (FreeBSD-Security)
  • DriverEntry not being called
    ... I am working on a SDIO wirless card driver and am attempting to use ... the Atheros driver as as example. ... spawn a secondary thread to do the NdisRegisterAdapter() call (again, ... 0xc0000004 indicating an exception. ...
    (microsoft.public.windowsce.embedded)
  • Re: Network card - sis190 driver and YAST2
    ... and everthing is fine except for the network. ... with an active sis190 driver and also an Atheros 802.11 b/g wireless PCI ... the Atheros driver should be. ...
    (alt.os.linux.suse)