

My lab consists of a wireless access point (AP), a wireless client that is used to connect to the AP, and a third wireless-capable device listening in promiscuous mode – this third device is using Wireshark.

This post is based on a testing environment where I own all involved devices. Otherwise, other modes generally only allow your machine to interpret traffic destined for it. Promiscuous mode allows a capable wireless network interface card (WNIC) to listen to all wireless traffic, regardless if the traffic is destined for your client machine or not. I know I am! This should go without saying, be responsible in what you do. If you’ve never used Wireshark with promiscuous mode enabled, I highly recommend it – if you’re into geeky things that is.
