


Like the MAC address, The LLC logical link control protocol is also layer 2, but is upper sublayer of Data Link Layer and won't affect the ability to capture the traffic unless you specify llc as a filter and there isn't any llc traffic, then you would get the blank screen. (I'm assuming the traffic you are looking for is traveling to a destination on another switch, outside the network, or at least to your gateway).īy specifying the MAC address filter, eth.addr eq xx:xx:xx:xx:xx:xx you are filtering for all traffic to and from that associated MAC address. If you are trying to trace MAC's on the switch you are also connected to, then you'll want to sniff from a port which is spanned/mirrored to the port which has inbound/outbound traffic of that switch, so that you will see all the traffic coming in and out of the switch. Active: in this case you can interact with the device and discover more about it. You can monitor the network using Wireshark and find information such as the MAC address, from MAC, you can know the device manufacture. For instance, tshark -i 1 -R "eth.addr eq xx:xx:xx:xx:xx:xx or eth.addr eq xx:xx:xx:xx:xx:xx" Passive: meaning that you dont want to interact with the device you want to discover. config system dhcp reserved-address edit 'ipphone' set ip 192.168.1. You can use a list for your MAC's in one display filter, but not a range, unless you switch to IP's instead of MAC's. There are a lot of MAC addresses there And there is no description of the MAC address (ie which device it belongs to) So I do not know how to assign a MAC address to an IP address. If you are using a display filter of eth.addr = xx:xx:xx:xx:xx:xx and you are not seeing any information being displayed/sniffed, then the traffic for that MAC address is not passing through the port you're sniffing on. One Answer: 1.) Yes, there is a router between the machines.
