Despite this, I will still mask involved MAC addresses from included images. 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. From everything I read online this is not suppose to be the case which is very confusing.If you’ve never used Wireshark with promiscuous mode enabled, I highly recommend it – if you’re into geeky things that is. VMC task manager is showing 10 Mbits incoming, I see the multicast traffic destined for VMAįrom these results I gather that the Network Adapter is in promiscuous. Now, loaded Wireshark again in Promiscuous mode VMC task manager is NOT showing the additional bandwidth, Wireshark is NOT showing the multicast traffic VMB task manager is showing 10 Mbits incoming, I see the multicast traffic destined for VMA Now, to verify the traffic I loaded Wireshark in NON-promiscuous mode VMC is NOT subscribed . Task manager is NOT showing any additional bandwidth Task manager is showing 10 Mbits incoming

VMA is subscribed to a multicast group and is receiving 10 Mbits Multicast thread), and have discovered a behavioral difference between the Network Adapter and Legacy Network Adapter.įrom my testing it seems the Network Adapter is using promiscuous mode and the Legacy is not (or the legacy is able to manage multicast (igmp) packets a lot better).ģ VMs running on a single host (teamed nics) I've been investigating an issue with Multicast spamming (see m y

Promiscuous mode wireshark what is it