Gratuitous ARP (GARP) & Duplicate IP Detection
Watch PC-A check whether an IPv4 address is already in use, see an ARP broadcast flood through the switch, and compare a conflict-free startup with a duplicate-IP response. Inspect the exact Ethernet and ARP fields along the way.
Original GARP animation
Your GIF · loops automaticallyOriginal animation supplied for this lesson. The diagram uses a GARP packet to discuss duplicate-address detection; the interactive lab below separates ARP Probe (check before use) from ARP Announcement / GARP (announce an address in use).
0.0.0.0 and target IP 10.1.1.1. Also, ARP is not guaranteed to receive a reply when a gratuitous announcement is sent. Both are Ethernet broadcasts on the local VLAN; routers don't normally forward that broadcast into another subnet.Interactive packet-level lab
Choose a scenario and step through each event
Follow the packet
PrepareWhat changed at this stage?
Packet fields, switch MAC learning, and example host ARP state update alongside the selected stage.
Packet inspector
Live fields change with the selected stage and scenario.
Switch MAC table
| VLAN | Source MAC | Port |
|---|
Learning the source MAC is different from learning an IP→MAC mapping.
Receiver's ARP cache (example)
| IPv4 | MAC | Observation |
|---|
Host ARP cache behavior varies by operating system and policy; an unsolicited announcement may refresh an existing entry but need not create a new one.
Probe vs GARP: the exact field differences
| Field | ARP Probe (pre-use check) | ARP Announcement / GARP |
|---|---|---|
| Ethernet destination | ff:ff:ff:ff:ff:ff | ff:ff:ff:ff:ff:ff |
| EtherType | 0x0806 (ARP) | 0x0806 (ARP) |
| Operation | Request (1) | Request (1) in RFC 5227 announcement |
| Sender MAC (SHA) | PC-A's MAC | PC-A's MAC |
| Sender IPv4 (SPA) | 0.0.0.0 | 10.1.1.1 |
| Target MAC (THA) | 00:00:00:00:00:00 | 00:00:00:00:00:00 |
| Target IPv4 (TPA) | 10.1.1.1 | 10.1.1.1 |
| Main purpose | Check whether address is in use | Announce use / refresh neighbors' mappings |
Note: Gratuitous ARP may also be implemented as an unsolicited ARP Reply. The interactive example uses an RFC 5227 ARP Announcement (Request) and a Probe (Request).
Understand the behavior
Why does the switch flood it?
ARP requests use Ethernet destination ff:ff:ff:ff:ff:ff. The switch learns the incoming source MAC on port 1 and floods the broadcast out other forwarding ports in VLAN 10. It does not determine who owns 10.1.1.1.
What proves an address is occupied?
During probing, a valid ARP message from a different MAC asserting the proposed IPv4 address signals a conflict. An owner may respond, and the new host must not proceed to claim that address in the RFC 5227 flow.
Why announce afterward?
After successful probing, the new owner broadcasts an ARP Announcement to tell neighbors which MAC owns the IP. It's not a request to resolve a remote host. An unsolicited reply is not guaranteed or required.
Check your understanding
8 questions with explanations