ARP Cache Inspection
What you'll learn: How to examine ARP tables to detect duplicate MAC addresses and inconsistencies that reveal ARP poisoning attacks.
Why Inspect the ARP Cache?
Your computer maintains an ARP cache—a small table mapping IP addresses to MAC (hardware) addresses. Think of it like a phone book: "Who has IP 192.168.1.1? Oh, that's MAC address AA:BB:CC:DD:EE:FF." This cache speeds up network communication, but attackers can poison it with false entries to intercept traffic.
By inspecting your ARP cache regularly, you can spot telltale signs of ARP poisoning attacks before they compromise your data.
What to Look For
1. Duplicate MAC Addresses
If multiple IP addresses map to the same MAC address (especially the attacker's), someone may be impersonating legitimate devices. For example:
192.168.1.1→AA:BB:CC:11:22:33(legitimate gateway)192.168.1.50→AA:BB:CC:11:22:33(suspicious!)
2. Rapid Cache Changes
ARP entries shouldn't change frequently. If a gateway's MAC address keeps flipping between values, an attacker might be actively poisoning the cache.
3. Unexpected MAC Vendors
MAC addresses contain vendor identifiers. If your router suddenly shows a MAC from a laptop manufacturer, that's a red flag.
How to Inspect
On most systems, view your ARP cache with simple commands:
- Windows:
arp -a - Linux/Mac:
arp -norip neighbor show
Compare entries against known-good records (your router's actual MAC, for instance). Document baseline values when your network is clean, then regularly check for deviations.
Key Takeaway: ARP cache inspection reveals duplicate MACs and suspicious changes that indicate active poisoning attacks—your first line of defense in detecting man-in-the-middle attempts on your local network.