Gratuitous ARP, commonly called GARP, is an unsolicited ARP message used by an IPv4 device to announce information about its own IPv4-to-MAC address mapping on the local network.
Unlike a normal ARP exchange, the device does not need to wait for another host to ask:
“Who has this IPv4 address?”
Instead, it proactively announces information associated with the address.
Gratuitous ARP is commonly useful when:
- A network interface becomes active
- An IPv4 address becomes active on a device
- A high-availability service moves between systems
- A virtual IPv4 address becomes active on another node
- Network devices need to relearn the location of a MAC address
- Address-conflict detection or defense is occurring
RFC 5227 formally describes an ARP Announcement as an ARP Request broadcast on the local link where both the sender and target IPv4 address fields contain the IPv4 address being announced.

How Gratuitous ARP Works
A normal ARP Request is sent because a host needs to discover the MAC address associated with another IPv4 address.
For example:
Who has 192.168.10.20?
Tell 192.168.10.10
With a gratuitous ARP announcement, the host is announcing information about its own address.
Assume:
IPv4 Address:
192.168.10.50
MAC Address:
00:1A:2B:3C:4D:5E
A standards-based ARP Announcement described by RFC 5227 uses an ARP Request with:
Sender Protocol Address:
192.168.10.50
Sender Hardware Address:
00:1A:2B:3C:4D:5E
Target Protocol Address:
192.168.10.50
Target Hardware Address:
00:00:00:00:00:00
Ethernet Destination:
FF:FF:FF:FF:FF:FF
ARP Operation:
Request
The important relationship is:
Sender IPv4:
192.168.10.50
Target IPv4:
192.168.10.50
The sender is announcing:
“This is the IPv4 address I am now using.”
RFC 5227 describes this ARP Announcement as a broadcast ARP Request in which both the sender and target protocol addresses contain the address being announced.
Why Is the Destination MAC Broadcast?
The Ethernet destination is:
FF:FF:FF:FF:FF:FF
so systems in the same Layer 2 broadcast domain can receive the announcement.
The message does not cross normal router boundaries.
Does Every Device Update Its ARP Cache?
Not necessarily.
It is safer to say that a gratuitous ARP allows receiving systems to learn or refresh information, depending on their ARP implementation and current cache state.
Do not assume every host will always overwrite its ARP cache solely because it receives a gratuitous ARP.

Gratuitous ARP Request vs Unsolicited ARP Reply
The term Gratuitous ARP is used somewhat broadly in networking products and documentation.
RFC 5227 specifically defines an:
ARP Announcement
using an ARP Request.
Some implementations and network products may also send unsolicited ARP Replies for related announcement purposes.
Therefore, do not assume one exact unsolicited ARP Reply field layout applies to every device or vendor.
ARP Probe vs ARP Announcement
ARP Probe and ARP Announcement are related but should not be confused.
ARP Probe
An ARP Probe is used before a device begins using an IPv4 address.
The device is essentially asking:
“Is anybody already using this address?”
RFC 5227 specifies:
Sender IPv4:
0.0.0.0
Target IPv4:
Candidate IPv4 Address
ARP Operation:
Request
Ethernet Destination:
Broadcast
Using:
Sender IPv4:
0.0.0.0
helps avoid announcing ownership before the device has confirmed that the candidate address is safe to use.
ARP Announcement
After the device has selected the address for use, it can announce it.
Example:
Sender IPv4:
192.168.10.50
Target IPv4:
192.168.10.50
Quick Comparison
| Feature | ARP Probe | ARP Announcement |
|---|---|---|
| Main Purpose | Check whether address is already in use | Announce address being used |
| Sender IPv4 | 0.0.0.0 | Announced IPv4 address |
| Target IPv4 | Candidate address | Same announced address |
| ARP Operation | Request | Request in RFC 5227 |
| Ethernet Destination | Broadcast | Broadcast |
RFC 5227 explicitly distinguishes ARP Probes from ARP Announcements in this way.

Gratuitous ARP and IP Address Conflicts
One useful role associated with gratuitous ARP and IPv4 Address Conflict Detection is identifying situations where more than one device appears to claim the same IPv4 address.
Consider:
Host A:
192.168.10.50
MAC 00:AA:AA:AA:AA:50
Host B:
192.168.10.50
MAC 00:BB:BB:BB:BB:50
This is a duplicate IPv4 address.
ARP traffic may reveal competing claims such as:
192.168.10.50 is at 00:AA:AA:AA:AA:50
192.168.10.50 is at 00:BB:BB:BB:BB:50
That is an important troubleshooting clue.
Does the Other Device Automatically Disable Its Interface?
No universal behavior should be assumed.
Conflict handling depends on:
- Operating system
- Network stack
- Device implementation
- HA software
- Address configuration method
RFC 5227 defines mechanisms for IPv4 Address Conflict Detection and address defense, but the resulting user-visible behavior varies between implementations.
Gratuitous ARP in High Availability
High availability is one of the most important practical uses of gratuitous ARP.
Imagine two appliances:
Node A:
Active
Node B:
Standby
Service IPv4:
192.168.10.100
Traffic currently reaches Node A.
Node A fails.
Node B becomes active.
The network must now direct Layer 2 traffic toward the new active node.
Gratuitous ARP can assist this convergence.
Failover with a MAC Change
Suppose:
Before Failover:
192.168.10.100
→ 00:AA:AA:AA:AA:01
After Failover:
192.168.10.100
→ 00:BB:BB:BB:BB:02
The new active device can announce the new mapping.
Clients can then refresh stale ARP information instead of waiting only for normal cache aging.
Switch MAC Table Learning
There is another important Layer 2 effect.
Ethernet switches learn MAC addresses from the:
Source MAC address of received Ethernet frames.
When the new active device sends gratuitous ARP, the switch can also relearn which switch port now leads to that MAC address.
This is especially important when a virtual MAC moves from one physical device or port to another.

Gratuitous ARP with HSRP and VRRP
First-hop redundancy protocols also use gratuitous ARP behavior.
HSRP
Cisco HSRP provides a virtual default gateway.
Cisco documents HSRP gratuitous ARP behavior when a group transitions to the Active state. Current command documentation states that HSRP sends gratuitous ARP packets when the group becomes active, with configurable count and interval.
A simplified environment:
Virtual Gateway IPv4:
192.168.10.1
Router A:
Active
Router B:
Standby
When Router B takes over, GARP can help the local Ethernet infrastructure converge.
VRRP
Current VRRPv3 is defined by RFC 9568.
For IPv4, when a VRRP router becomes Active, RFC 9568 requires it to broadcast gratuitous ARP messages containing the Virtual Router MAC address for the protected IPv4 addresses.
This highlights an important detail.
The IP-to-MAC Mapping May Not Always Change
Protocols such as VRRP use a:
Virtual MAC address
Therefore, during a normal failover, the host may continue using the same mapping:
Virtual IPv4:
192.168.10.1
Virtual MAC:
Same Before and After Failover
In this situation, an especially important function of gratuitous ARP is allowing the Ethernet switching infrastructure to learn that the virtual MAC is now reachable through a different physical port.
Where Gratuitous ARP Is Commonly Used
GARP is useful in many IPv4 HA and mobility scenarios.
Firewalls
Active/standby firewall pairs may announce service addresses after a failover.
Routers
First-hop redundancy systems such as HSRP or VRRP may use gratuitous ARP behavior during active-role transitions.
Load Balancers
HA load balancers may need to announce a virtual IPv4 service after failover or ownership changes.
The exact behavior depends on the product architecture.
Servers and Clusters
Clusters that move a service IPv4 address between hosts may use gratuitous ARP to accelerate network convergence.
Virtual Machines
When an IPv4 address or virtual interface moves between hypervisor locations, unsolicited ARP traffic may assist local Layer 2 convergence depending on the virtualization platform.
Security Risks
ARP itself does not provide strong authentication.
A receiving device cannot inherently prove that an unsolicited ARP claim is legitimate merely because it arrived on the LAN.
This makes malicious gratuitous ARP-like traffic useful in:
- ARP spoofing
- ARP poisoning
- Man-in-the-middle attempts
- Traffic redirection
- Denial-of-service attacks
Example Attack
The real default gateway is:
IPv4:
192.168.10.1
MAC:
00:10:20:30:40:50
An attacker sends a forged ARP announcement claiming:
192.168.10.1
is at
00:66:66:66:66:66
If endpoints accept the false information, traffic may be redirected toward the attacker’s device.
Dynamic ARP Inspection
Managed switches can provide:
Dynamic ARP Inspection — DAI
DAI can validate ARP information using trusted sources such as DHCP Snooping bindings on supported networks.
Conceptually:
DHCP Snooping
↓
Trusted Binding
IP + MAC + VLAN + Port
↓
Dynamic ARP Inspection
↓
Validate ARP Claims

Packet Analysis and Troubleshooting
Wireshark is extremely useful for analyzing Gratuitous ARP.
Wireshark Filter
Use:
arp
To investigate a specific IPv4 address, you can inspect ARP packets associated with that protocol address.
Linux tcpdump
Capture ARP:
sudo tcpdump -nn -e -i any arp
The -e option helps display Ethernet header information, which is useful when investigating MAC movement.
What to Look For
For an ARP Announcement, inspect:
- Ethernet source MAC
- Ethernet destination MAC
- ARP opcode
- Sender MAC
- Sender IPv4
- Target IPv4
- Interface where packet was observed
- Number and timing of repeated GARPs
Typical ARP Announcement
Conceptually:
Ethernet Destination:
ff:ff:ff:ff:ff:ff
ARP:
Request
Sender:
192.168.10.100
00:BB:BB:BB:BB:02
Target:
192.168.10.100
Troubleshooting HA Failover
Suppose:
Virtual IPv4:
192.168.10.100
Old Active:
Node A
New Active:
Node B
After failover, users cannot reach the service.
Check:
- Did Node B actually become active?
- Did Node B send GARP?
- Which MAC was announced?
- Did clients retain an old ARP entry?
- Did the switch relearn the MAC on the new port?
- Is ARP security blocking the announcement?
- Is the virtual IPv4 configured on the correct interface/VLAN?
- Is traffic reaching Node B?
Check Windows ARP Information
arp -a
or:
Get-NetNeighbor -AddressFamily IPv4
Linux
ip neigh
Check Switch MAC Learning
On a managed switch, inspect the forwarding-table entry for the relevant MAC.
A Cisco-style example is:
show mac address-table address
The command syntax varies between vendors.

Advantages and Limitations
Advantages
Faster HA Convergence
GARP can help the local network learn that an IPv4 service or MAC location has moved.
Address Announcement
A device can announce its IPv4-to-MAC relationship without waiting for another host to initiate ARP.
Conflict Detection Support
ARP Probe and Announcement behavior forms part of IPv4 Address Conflict Detection defined by RFC 5227.
Switch MAC Relearning
GARP frames can help a switch learn the current location of a moving MAC address.
Limitations
Local Broadcast Domain Only
Gratuitous ARP operates on the local Layer 2 segment.
Routers do not forward ARP broadcasts between normal routed subnets.
No Strong Authentication
ARP does not inherently verify that an announcement is trustworthy.
Receiving Behavior Can Vary
Not every endpoint processes unsolicited ARP information identically.
Security Features Can Block It
DAI or other ARP controls can interfere with legitimate GARP when incorrectly configured.
Excessive GARP Is Unnecessary
Repeated gratuitous ARP traffic should be controlled according to the product and HA design rather than generated continuously without reason.
Gratuitous ARP and IPv6
Gratuitous ARP applies to:
IPv4
IPv6 does not use ARP.
IPv6 uses:
Neighbor Discovery Protocol
over ICMPv6.
For comparable IPv6 address or neighbor announcements, systems can use:
Unsolicited Neighbor Advertisement
For example, the current VRRPv3 specification uses gratuitous ARP for protected IPv4 addresses and unsolicited Neighbor Advertisements for protected IPv6 addresses.
IPv4 HA Convergence
Gratuitous ARP
IPv6 HA Convergence
Unsolicited Neighbor Advertisement
Key Takeaways
- Gratuitous ARP is an unsolicited ARP message used to announce IPv4-to-MAC information on a local network.
- RFC 5227 defines an ARP Announcement as a broadcast ARP Request where the sender and target IPv4 addresses are both the announced address.
- An ARP Probe is different: its sender IPv4 address is
0.0.0.0because the device has not yet committed to using the candidate address. - Gratuitous ARP operates only within the local Layer 2 broadcast domain.
- GARP is commonly useful during:
- Device initialization
- IPv4 address activation
- HA failover
- Virtual IP movement
- Layer 2 MAC movement
- Do not assume every receiving host automatically replaces its ARP entry when it receives GARP.
- GARP can help endpoints refresh IPv4-to-MAC information.
- GARP Ethernet frames can also help switches relearn where a MAC address is physically located.
- HSRP supports gratuitous ARP when a group becomes Active.
- Current VRRPv3 requires an Active router to send gratuitous ARP for protected IPv4 addresses using the Virtual Router MAC.
- With virtual-MAC HA designs, the IP-to-MAC mapping may remain unchanged during failover; the important change may instead be the switch port through which that virtual MAC is reachable.
- Gratuitous ARP can assist IPv4 address-conflict detection and defense, but conflict-handling behavior varies by implementation.
- ARP does not provide strong authentication, so unsolicited ARP traffic can be abused for spoofing and poisoning.
- Dynamic ARP Inspection can help protect managed access networks, but it must be designed to allow legitimate HA behavior.
- IPv6 does not use Gratuitous ARP. Similar functions use ICMPv6 Neighbor Discovery and unsolicited Neighbor Advertisements.
Gratuitous ARP is most valuable in dynamic IPv4 networks where addresses or Layer 2 ownership can move.
During a failover, do not troubleshoot only the virtual IPv4 address.
Ask:
Did the new active device send a GARP?
Which MAC address did it advertise?
Did endpoint ARP information converge?
Did the switch MAC table move to the new port?
Is Dynamic ARP Inspection or another security feature blocking the announcement?
Does the HA design use the same virtual MAC or a different MAC after failover?
Answering those questions usually reveals whether a post-failover problem is caused by:
- ARP state
- MAC-table state
- HA configuration
- Security enforcement
- Or another network-path issue
Useful Links and References
SanchitGurukul Resources
Official Technical References
Your feedback matters
Was this post helpful?
Discussion
0 approved comments
No approved comments yet. You can start the discussion below.
Leave a Comment
No login is required. Name and email are used for moderation/security. Your email is never displayed publicly. All comments require administrator approval.
Discover more from SanchitGurukul
Subscribe to get the latest posts sent to your email.
