

Packets sent on multiple streams if your monitoring wireless interface has lower number of radioĮx: A 802.11n data packet sent on 3 streams at 450Mb/s won’t be seen if your 802.11n monitoring interface has only 2 Rx radios (very common with Windows machine or Airpcap dongles.Packets sent on multiple streams but one or more streams can’t be decoded.Malformed packets at the 802.11 preamble level (due to interference, low signal or bad antenna position).Packets of an adjacent channel can be heard.Įx: a packet sent on channel 10 can be captured by monitor mode in channel 11.All bad FCS 802.11 packets are seen, as long as the 802.11 preamble is valid.All valid 802.11 packets heard by the radio on the frequency, encrypted or not.OSI model level: Physical (PHY) Layer + Data Link Layer (Mac).Connection state: Must be disassociated of any network, but configured with a specific channel & channel width (20 – 160MHz).Monitor mode is enabled, link-layer header is now 802.11 & a pseudo radiotap header added by WiresharkĮncrypted 802.11n data packet captured in monitoring mode on Channel 116. Monitoring mode works specifically for Wi-Fi, allowing to capture packets at the 802.11 radio level, not at the Ethernet level anymore.

Packets not seen: Bad FCS packets: dropped by the network interface before the capture library can be aware of them.Packets seen: depends off the promiscuous mode.Lowest protocol seen: Ethernet (IEEE 802.3).Connection state: Wire: cable plugged (!) / Wireless: associated to an Access Point or ad-hoc network.With or without promiscuous mode, Ethernet packet capture works with:
#HOW TO USE PROMISCUOUS MODE WIRESHARK MAC#
Typically, Debookee NA module must put the interface in promiscuous mode to see intercepted packets from other devices like an iPhone because the destination MAC address is the iPhone’s one, not our own MAC address.
