Link state is decoration: a cable marked down still carries traffic #1057
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1057
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?
Linkhas carriedstate: 'up' | 'down' | 'blocked'since the physical layer was built, andnothing in the engine ever reads it:
Link.isUp()exists, is exported, is serialised, and has no caller. So a cable markeddown:The field is decoration. The failure it hides is total: a lab can show a cut link passing
traffic, which is the one thing a network simulator must never do.
What a lab needs
Pulling a cable is the single most common thing a technician does in Packet Tracer, and this project
has no word for it.
topo.disconnect()deletes the link, which is a different operation: the portsunpatch, the hardware changes, and the cable never comes back. What is missing is:
are not unicast into the port that used to lead somewhere.
can show the window in which nothing works — and the answer at any instant inside it says
convergingrather than "host unreachable", which is a different and wrong diagnosis.instant, and still report the correct convergence window.
link down <id> at <ms>.Acceptance
reason: 'link down'and the link id.reason: 'converging'; at 41 s itsucceeds, and
getConvergence().convergedAtMsis 40 000.link state/stateSinceMs/lastChangeAtMsround-trip through save/load; links that never changedcarry no new field, so regenerated examples stay byte-identical.
link up|down|stateandlinksin the CLI with the usages above;POST /api/topologies/:id/links/:linkId/state; a down cable drawn dashed and red.Not in scope
Degraded links (no CRC errors, no flapping), autonegotiation on recovery, interface self-test
failures, and RSTP fast convergence — the timer model is 802.1D, so re-convergence costs the same
30 s as a boot. These are documented in
docs/LINK-STATE.mdrather than half-implemented.