

The switches clone a copy of all the traffic on that port en send it to the port to which your PC is connected. Note: The following screenshots were taken using an old (pre v2.0) version of Wireshark. Once a wireless card is in monitor/promiscuous mode, the data can be viewed live using Wireshark in Monitor Mode.


Other possibility (but this requires managed switches with this ability and access to them) is to setup the port on either A or B as a so-called span-port or mirror-port (depends on vendor how it is called). This capture can be viewed live from Wireshark running in Monitor Mode. The easiest way to properly listen in to the conversation between A and B is to put a simple hub (which transmits ALL traffic to all its ports) between either A or B and the LAN and have the monitoring PC listen in on that same hub. As your own NIC isn't part of the conversation between the other 2 computers it will generally NOT receive that traffic. Most switches these days are smart and will only send traffic to where it is needed. IP-subnets (Layer 3) have nothing to do with it.Īnd anything in the same (v)lan as your own NIC can be seen, unless your switches keep it away from your NIC. Please note that I say (v)lan, because this is a Layer 2 thing. Which means anything happening outside your own (v)lan is invisible anyway.
