tracePath answers arrived over a cable that is down #1516

Closed
opened 2026-11-15 18:01:04 +00:00 by jaylouisw · 0 comments
Owner

tracePath does not consult link state. After linkDown on a WAN uplink, ping to the internet correctly fails while tracePath to the same destination still returns ok: true, arrived: true.

Why it matters: any check or UI panel built on "did the trace arrive" passes over a pulled cable. A trace is the evidence an operator pastes into a ticket, so it must not be more optimistic than the data plane.

Where: engine/simulator.js tracePath (~:3950) - the hop walk needs the same per-link verdict _deliver uses.

Suggested fix: run each hop through the existing Topology.linkState() verdict and stop the walk at the first down link, reporting the link and the reason rather than skipping it.

`tracePath` does not consult link state. After `linkDown` on a WAN uplink, `ping` to the internet correctly fails while `tracePath` to the same destination still returns `ok: true, arrived: true`. **Why it matters:** any check or UI panel built on "did the trace arrive" passes over a pulled cable. A trace is the evidence an operator pastes into a ticket, so it must not be more optimistic than the data plane. **Where:** `engine/simulator.js` `tracePath` (~:3950) - the hop walk needs the same per-link verdict `_deliver` uses. **Suggested fix:** run each hop through the existing `Topology.linkState()` verdict and stop the walk at the first down link, reporting the link and the reason rather than skipping it.
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#1516
No description provided.