A failed ping can report the wrong reason: "no ARP reply" when the port was actually shut #1431

Closed
opened 2026-11-11 17:41:17 +00:00 by jaylouisw · 0 comments
Owner

ping reports why nothing came back by reading the run's discard events from the end backwards, so the reason it prints is the last discard — and the last one is usually the least true.

Measured on a -- sw -- r1, uplink shut on r1:

known target  (10.91.0.1):   reason: "peer port shut (r1 Gi0/0/0)"     <- correct: the wire is shut
unknown target (10.91.0.99): reason: "no ARP reply from 10.91.0.99"    <- the wire was shut, not silent

The end-of-run sweep that reports unanswered ARPs always lands last in the event log, so it always won — blaming silence for a frame that never left. The reply also only searched events after the ping started, so a shut port noticed earlier in the run was invisible to it.

What should be true

  1. the reason is the earliest/true cause, ranked: port or wire that cannot carry the frame first, silence next, policy (ACL/VLAN/NAT) last;
  2. an ACL denial still outranks "no reply";
  3. no shutdown makes the same ping answer again, with no stale state.
`ping` reports why nothing came back by reading the run's discard events **from the end backwards**, so the reason it prints is the *last* discard — and the last one is usually the least true. Measured on `a -- sw -- r1`, uplink shut on `r1`: ``` known target (10.91.0.1): reason: "peer port shut (r1 Gi0/0/0)" <- correct: the wire is shut unknown target (10.91.0.99): reason: "no ARP reply from 10.91.0.99" <- the wire was shut, not silent ``` The end-of-run sweep that reports unanswered ARPs always lands **last** in the event log, so it always won — blaming silence for a frame that never left. The reply also only searched events *after* the ping started, so a shut port noticed earlier in the run was invisible to it. ### What should be true 1. the reason is the **earliest/true cause**, ranked: port or wire that cannot carry the frame first, silence next, policy (ACL/VLAN/NAT) last; 2. an ACL denial still outranks "no reply"; 3. `no shutdown` makes the same ping answer again, with no stale state.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge#1431
No description provided.