![]() ![]() 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. From: bugzilla-daemon Prev by Date: Wireshark-bugs Bug 9569 Disable TPNCP (proprietary Audiocodes) dissector - rename tpncp. 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" References: Wireshark-bugs Bug 9582 New: wireshark always crashes on my Mac OS X Mavericks. Or you could use the keystroke Control+E. ![]() You can select the menu item Capture -> Start. Click the first button on the toolbar, titled Start capturing packets. 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. Once select the network interface, you can start the capture, and there are several ways to do that. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |