Add serial WAN links: a V.35 medium, a clock, and a router that has the ports #1483
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!1483
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/serial-links"
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?
Add serial WAN links: a V.35 medium, a clock, and a router that has the ports
The engine had 64 media — copper, fibre at nine rates, PON, DAC, DOCSIS, MoCA, DSL, powerline, Wi-Fi, cellular — and no concept of a synchronous serial cable. No device in the catalogue had a serial port either. So the first WAN lab anyone builds in Packet Tracer (two routers back to back, one DCE,
clock rate, an IP each, a ping) was impossible rather than merely unmodelled.The medium.
serial-v35and aserialcage: one cable, no choice of optic, mated only to itself, refused against RJ45 as a connector mismatch. Its rate is clocked, not negotiated, so the speed ladder is the setclock ratecan dial (64k–8M), filtered by the port's own maximum like every other cage.The clock. A serial link has exactly one DCE. Neither end clocked is
E_SERIAL_NO_CLOCK; both ends clocked isE_SERIAL_TWO_CLOCKS. Both refuse at cabling time and both name the fix. The link's rate is the clock, not the port's ceiling — a 64 kbps line is 64 kbps.clock rate <bps>is refused on a non-serial port, and refuses a rate the port cannot clock by listing the ones it can.The hardware.
cisco/2811: two onboard 10/100 FastEthernet (not gigabit — the 2811 predates onboard GigabitEthernet, and a lab expecting 1G is describing a 2911) plus a WIC-2T in the first HWIC slot givingSe0/0/0andSe0/0/1.Three existing invariants caught this and were right to, which is the part worth reporting:
hardware-invariantsslowIsCorrectbeside DSL and PON, because a T1 is honestly 1.544 Mbps and flagging it would push a contributor to inflate the one number the spec exists to statecable-matrixbidi-media84 suites, 4212 assertions, 40 new in
test/serial-links.test.js(medium, mating, the 2811's ports, both clock refusals, the CLI's own refusals, and a ping crossing a clocked link).docs/PHYSICAL_LAYER.mdgains §2.1;CONNECTORS.mdthe cage row;CLI.mdthe command.1dcc1157c14f0d2e70624f0d2e7062dc6f47f926Rebased onto
mainand landed (ff5c18f1), both commits. Conflicts were all adjacent-insertion, not behavioural: the VRRP ownership block inengine/device.js, theip address dhcprow indocs/CLI.md, and the media table inengine/media.jswheremainhad grown per-baud console variants while the branch addedserial-v35. Resolutions kept both sides and were checked by the branch's own suite:engine/device.js— keptmain's VRRP block and the branch'sholdsIp()commentary aboveholdsIp();engine/media.js— keptmain's five console-baud media, added onlyserial-v35(the branch's older singleconsole-rs232entry would have collided with the key);docs/CLI.md— keptmain's corrected DHCP-client row, added the twoclock raterows;test/hardware-invariants.test.js— union of the slow-is-correct set, both rationales kept in the comment.The same fossil CodeQL failure as #1484 was present (this branch's base predates
dd8b024a, which dropped the GitHub-legacy workflows); the rebase removed it.Rebasing also put the new 2811 in front of
test/doc-catalog-counts.test.js, which requires every count indocs/DEVICE_REGISTRY.mdto match the catalogue: 2,038 → 2,039 models, 368 → 369 routers, 48 → 49 Cisco devices. Regenerated withscripts/regen-registry-doc.jsrather than hand-edited.Verified before pushing: full suite 240 suites / 8,944 assertions, 4 failures all from the document counts, fixed;
serial-links40/40,cable-matrix406,hardware-invariants26,bidi-media73,address-ownership24,doc-catalog-counts24, syntax 309 files. Post-merge onmain: catalogue 2,039 with the 2811 present,serial-links40/40.helplisted neither of the two features landed yesterday, nor the DHCP pool sub-mode #1491