ARP

What this topic solves

IPv4-to-MAC resolution, ARP cache, gratuitous ARP, proxy ARP, duplicate addressing and troubleshooting.

Follow state and packet path

Validate prefix, scope, gateway, neighbor resolution, MTU and longest-prefix match. Correct addressing without a return path is still a failure.

Input → classification/state → decision → table → next-hop/output → counters

Design before configuration

• Define the failure domain and expected convergence behavior.
• Document addressing, identifiers, timers, MTU and policy boundaries.
• Prefer explicit, observable state over assumptions.
• Plan rollback and out-of-band access before risky changes.

Commands and verification

Command syntax varies by platform and software release. The examples below come from the existing portal content and must be validated against the target platform documentation before production use.

Host A: 192.0.2.10/24
Host B: 192.0.2.20/24

A determina que B é on-link
A → broadcast: "Quem tem 192.0.2.20?"
B → reply: "192.0.2.20 está em 00:bb:..."
A → frame unicast para MAC de B

A: 192.0.2.10/24
GW: 192.0.2.1
Servidor: 198.51.100.50

IP destino no pacote: 198.51.100.50
MAC destino no primeiro frame: MAC de 192.0.2.1

Evidence-driven workflow

1. Define source, destination, time window and exact symptom.
2. Establish the expected healthy state and compare it with the observed state.
3. Inspect counters, tables, logs and packet captures before resets.
4. Test one hypothesis at a time and prefer reversible changes.
5. Repeat the original test after correction and check side effects.

RFC 826

Use the current standard/RFC and the documentation for the exact software release being operated. Vendor syntax is an implementation detail; protocol behavior should be understood independently.

Prove the behavior in a controlled topology

Build the smallest topology that reproduces the mechanism, capture control and data traffic, introduce one deliberate failure and diagnose it before applying the fix.

Related network topics