docs(CLI): the running-config table lists NAT, the bridge priority and clock rate #2042
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!2042
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/1118-2147"
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?
What was untrue
docs/CLI.md-> What the config contains opens with "the output is also complete: every object the CLI can configure appears in it" and then enumerates the printed sections in a table. Three things the printer writes had no row:ip nat pool <name> <start> <end> netmask <mask>and oneip nat inside source ...line per rule, plus per-interfaceip nat inside/ip nat outside;spanning-tree priority <n>;clock rate <bps>inside a serial interface block.Evidence from the code
engine/cli.js(running-config printer) pushesip nat pool ...and each rule vianat.formatRuleLine(), thenspanning-tree priority, both before thefor (const i of dev.interfaces.values())walk;clock rateis pushed inside that walk;ip nat inside|outsidecomes fromi.natRole.test/config-completeness.test.jsalready declares both keys (stpPriority,nat) as things the printer must cover, so the table was behind its own guard.Verified by typing it back:
ip nat pool WAN 203.0.113.1 203.0.113.6 netmask 255.255.255.0,ip nat inside source list 192.168.10.0/24 interface Gi0/1 overload,ip nat inside source static 192.168.10.60 203.0.113.1 tcp 443andspanning-tree priority 4096all print in exactly that form and replay.Second, smaller correction in the same sentence
The paragraph after the table said a value equal to the assumed default "is printed only when it differs, which is the same rule the rest of the config follows". A typed
spanning-tree priority 32768is printed (the printer testsstpPriority !== null, not the value), so the page now states that exception instead of contradicting the console.Guards (before -> after)
node scripts/syntax-check.js— 425 files, all OK (unchanged)Docs-only: no engine change.