Share via

NDISTest 6.5 - WlanNetmonMode

  • Article

This automated test suite verifies the device can be put into netmon mode.

Test details

Associated requirements

Device.Network.WLAN.Base.MeetScanAndConnReq Device.Network.WLAN.Base.SupportPromiscuousAndMulticastPacketFiltering Device.Network.WLAN.CSBBase.MeetScanAndConnReq Device.Network.WLAN.CSBBase.SupportPromiscuousAndMulticastPacketFiltering Device.Network.WLAN.CSBSoftAP.SupportSoftAP Device.Network.WLAN.SoftAP.SupportSoftAP

See the device hardware requirements.

Platforms

Windows 7 (x64) Windows 7 (x86) Windows RT (ARM-based) Windows 8 (x64) Windows 8 (x86) Windows RT 8.1 Windows 8.1 x64 Windows 8.1 x86

Expected run time

~5 minutes

Categories

Certification Reliability

Type

Automated

 

Running the test

Before you run the test, complete the test setup as described in the test requirements: Wireless LAN (802.11) Testing Prerequisites.

The following suites are available:

  • SendRecv_ext

The SendRecv_ext suite consists of the following:

Name Description

MgmtPacketsIndicated

Verify that the device under test (DUT) reports all management packets that were sent by the access point to the operating system.

SetDUTNetmonModeAndPhy

  • Configure the DUT to run in network monitor mode and verify that all supported OIDs can be called.

  • Query supported PHYs on the DUT, system under test (SUT), and the access point.

  • Configure the DUT to use DOT11_OPERATION_MODE_NETWORK_MONITOR.

  • Query desired PHY list to see if the DUT still supports that OID.

  • Set PHY on all devices to the same PHY.

NetmonMode

Verify that the DUT reports all packets transmitted between the SUT and the access point to the operating system while in DOT11_OPERATION_MODE_NETWORK_MONITOR mode.

SetDUTNetmonModeAndPhy

  • Configure the DUT to run in network monitor mode and verify all supported OIDs can be called.

  • Query supported PHYs on the DUT, SUT, and the access point.

  • Configure the DUT to use DOT11_OPERATION_MODE_NETWORK_MONITOR.

  • Query desired PHY list to see if the DUT still supports that OID.

  • Set PHY on all devices to the same PHY.

NetmonMode

Verify that the DUT reports all packets transmitted between the SUT and the access point to the operating system while in DOT11_OPERATION_MODE_NETWORK_MONITOR mode.

SetDUTNetmonModeAndPhy

  • Configure the DUT to run in network monitor mode and verify all supported OIDs can be called.

  • Query supported PHYs on the DUT, SUT, and the access point.

  • Configure the DUT to use DOT11_OPERATION_MODE_NETWORK_MONITOR.

  • Query desired PHY list to see if the DUT still supports that OID.

  • Set PHY on all devices to the same PHY.

NetmonMode

Verify that the DUT reports all packets transmitted between the SUT and the access point to the operating system while in DOT11_OPERATION_MODE_NETWORK_MONITOR mode.

SetDUTNetmonModeAndPhy

  • Configure the DUT to run in network monitor mode and verify all supported OIDs can be called.

  • Query supported PHYs on the DUT, SUT, and the access point.

  • Configure the DUT to use DOT11_OPERATION_MODE_NETWORK_MONITOR.

  • Query desired PHY list to see if the DUT still supports that OID.

  • Set PHY on all devices to the same PHY.

NetmonMode

Verify that the DUT reports all packets transmitted between the SUT and the access point to the operating system while in DOT11_OPERATION_MODE_NETWORK_MONITOR mode.

SetDUTNetmonModeAndPhy

  • Configure the DUT to run in network monitor mode and verify all supported OIDs can be called.

  • Query supported PHYs on the DUT, SUT, and the access point.

  • Configure the DUT to use DOT11_OPERATION_MODE_NETWORK_MONITOR.

  • Query desired PHY list to see if the DUT still supports that OID.

  • Set PHY on all devices to the same PHY.

NetmonMode

Verify that the DUT reports all packets transmitted between the SUT and the access point to the operating system while in DOT11_OPERATION_MODE_NETWORK_MONITOR mode.

 

Troubleshooting

For troubleshooting information, see Troubleshooting Wireless LAN (802.11) Tests.

 

 

Send comments about this topic to Microsoft