Networking/Computing Tips/Tricks

Great question, and one I get all the time.

As most of you know, the manufacturer of a networking device that uses MAC addressing can be identified by the OUI - Organizationally Unique Identifier.  OUI's are obtained from the IEEE.  You can find a complete list here.  The OUI is essentially the first 24 bits of the MAC address field (it is actually 22 bits - detail details).

The problem with the question is that Apple for example may have dozens or hundreds of OUI's.  

Luckily, Wireshark can perform number name resolution for MAC addresses.  We see this in the packet dissection:

Screen Shot 2017 06 21 at 12.42.15 PM

If we right click on the source MAC address field and select Apply as a filter, we get the following syntax:

Screen Shot 2017 06 21 at 12.45.03 PM

So the first 3 bytes (3c:07:54) must be an Apple OUI.  

If we modify the filter to this, trying to get all systems that have the OUI:

Screen Shot 2017 06 21 at 12.47.00 PM

We have several problems.  First, any Ethernet MAC above this range will be included, but more importantly we have not considered all the other Apple OUI's.

Another coice would be to use "Apple":

Screen Shot 2017 06 21 at 12.49.50 PM

But we can see that Wireshark's display filter mechanism does not accept that syntax.

The solution is to use a "hidden" protocol field that the Wireshark Expert actually has for MAC addresses.   It is called the 'eth.addr_resolved' field.  Further, instead of using the '>=' operator we need to use the 'contains' operator, thus if the MAC address of any packet is resolved from the large number of OUI's to be 'Apple' we have found all the Apple based traffic.  Here it is:

Screen Shot 2017 06 21 at 12.54.20 PM

There is your answer.  Hope that helps.

If you are interested in exploring other Wireshark Expert hidden fields, on a MAC click Wireshark> Preferences> Protocols, and on a Windows machine click Edit> Preferences> Protocols and then select the 'Display hidden protocol items':

Screen Shot 2017 06 21 at 12.56.36 PM

This does not need to be on for the filter above to work.  But one can imagine using these hidden fields to expand contents of your Profiles and filters.

 

 

Comments powered by CComment

The nicest thing you can do is use these inks to support us!  Thank you!

Support our research!  Buy me a coffee :)

Support our research. Become a Patron!

Find by Tag

4G Networks 5G Networks 6in4 6LoWLAN 6LoWPAN 802.11 802.11ah 802.11ax 802.11ay 802.11az Addressing Analysis Ansible Architecture ARP AToM BGP Bloom's Taxonomy Broadband Cable cat CBRS CellStream Cellular Central Office Cheat Sheet Chrome Cisco Cloud Coloring Rules Computer Consulting CPI Customer Support Data Center Data Networking DHCPv6 DNS Docker Documentation Dublin-Traceroute dumpcap ECMP Ethernet Ethics Fragmentation G-MPLS Git GNS3 Google GQUIC Hands-On History Home Network ICMP ICMPv6 IEEE 802.11p IEEE 802.15.4 Interface Control Internet IoT IPsec IPv4 IPv6 IS-IS L2VPN L3VPN LDP Linux LLN LoL M-BGP MAC MAC OSx Macro Microsoft mininet Monitoring MPLS MTU Multicast My Room Name Resolution Netcat Netmiko NetMon netsh Networking Network Science nmap Npcap Online School OpenFlow OSPF OSPFv2 OSPFv3 OSX OTT Paris-Traceroute Parrot PIM pktmon PMTU Policy POTS POTS to Pipes PPP Profile Programming Project Management Protocol 41 PW3E Python QoS QUIC Remote Desktop Requirements RIP Routing RPL RSVP Rural SAS SDN Security Service Provider Small Business SONET Speed SS7 SSH SSL Subnetting SYSCTL T-Shark TCP TCP/IP Telco Telecom 101 Telecommunications Telephone termshark TLS Tools Traceroute Traffic Engineering Training Travel Tunnel Ubuntu Utility Video Virtualbox Virtualization VoIP VRF VXLAN Webex WEP Wi-Fi Wi-Fi 4 Wi-Fi 5 Wi-Fi 6 Wi-Fi 6/6E Windows Winpcap Wireless Wireless 5G Wireshark Wireshark Tip WLAN WPA2 Zenmap ZigBee Zoom

Support us by clicking:

Twitter Feed