docs(simulation): no spanning-tree exists - the doc said it did not #2061
No reviewers
Labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!2061
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/1119-0047"
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?
docs/SIMULATION.md§2.4 (spanning tree) said STP cannot be disabled bracketed by a false fact: "show spanning-treeexists,no spanning-treedoes not".The console accepts
no spanning-tree: it is declared inengine/cli.js:697({ modes: ["config"], match: ["spanning-tree"], syntax: "no spanning-tree", effect: "clears the bridge priority" }) and answered by the shared spanning-tree handler. On a switch it printsNo bridge priority set: the device is using the default 32768, and afterspanning-tree priority 4096it printsBridge priority cleared (was 4096), back to the default 32768.docs/CLI.mddocuments the same line (#1502, "no spanning-tree… touch the priority").The conclusion the row was making - STP runs on every
l2-forwardbox and nothing turns it off - is still true; only the supporting claim was wrong. The row now says what the command does and cites where it is defined.Guards unchanged: syntax-check 430 files OK; docs-cli-transcript 4, docs-show-commands 7 (59 forms / 118 commands), help-completeness 8 (102 rows), no-form-help-key 81 - all pass before and after.
no spanning-treedoes exist - it clears the priority2d0dc86383527e010a05527e010a05to4fd196abe6