speed 100 is lost on save: the forced line rate is not in the port document, and the round-trip test could not see it #1405
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1405
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?
Found by asking the save question from the other end: not "does the document reload as itself" but "set one thing,
save, reload, and diff the port object field by field".
Save, then reload: the port is back at its hardware rate, and
speed 100has gone fromshow running-configaswell — which is what makes it permanent, because nothing is left to put it back.
duplex, one line above it in boththe writer and the reader, was saved all along.
Why the existing guarantee missed it
test/port-roundtrip.test.jsround-tripped a lab straight out of the catalogue, so every field sat at its defaultand the comparison was default-in, default-out. A setting that is only non-default after a command is invisible to
a sweep over virgin labs. The section's claim — "every field of every port survives the round trip, for every model
in the catalogue" — was tested against a file that carried nothing.
What must be true instead
own rate must not grow a
speedMbps: nullline);show interfacessays(forced), running-config still printsspeed <mbps>, and the cable runsat that rate — the value the engine uses, not merely a field;
spanning-tree portfast,vlan 20 name labanddo show vlaneach answered a different question #1493