docs: traceroute names the hop that stopped it, and ends the walk there (#1516) #1626
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1626
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/1116-0715"
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?
f5d06378(#1610) taught traceroute to stop at a probe that was stopped by a down cable, a shut port, a denying ACL or a forbidden VLAN, and to print the recorded reason in brackets (2 * no reply (link down)). Neither doc said so:docs/SIMULATION.md3.3 ICMProw claimed "a silent hop prints*" and said nothing about the walk ending at a structural drop, so a pulled cable read as thirty identical stars.docs/CLI.md's command table described only time-exceeded and echo-reply, and the page had no place that explained the bracketed clause.Both corrected. The transcript added to
docs/CLI.md(#A trace that stops where the cable did) was reproduced from the engine: PC1 to a server two routed hops away, PC1's own cable pulled viasetLinkState,1 * no reply (link down), walk stops after one hop. The deliberate non-final case is stated too — ano ARP reply from <ip>hop prints its reason and the walk continues, perFINAL_DROPinengine/simulator.js, verified with a next hop nobody owns (30 hops, each carrying the reason).Docs only — no engine, test or script changes.
Guards: syntax-check 342 files OK; no control bytes; doc citations 350, 0 new suspects; docs-show-commands 7 passed / 0 failed (47 forms); help-completeness 8 passed / 0 failed.