A failed ping can report the wrong reason: "no ARP reply" when the port was actually shut #1431
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1431
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
pingreports 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 onr1: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
no shutdownmakes the same ping answer again, with no stale state.