plans: the MTU is 1500 everywhere, and no packet in the lab can be too big #2080
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!2080
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "plan/1119-0337"
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?
Forward plan, docs only:
docs/plans/mtu-and-fragmentation.md.Measured on
be18b65d. The model holds an MTU (engine/device.js:90), one code path reads it(
Simulator.pathMtu()engine/simulator.js:3963-3983) and turns it into an MSS (engine/flow.js:111-118),and no operator can move it:
ip mtu 9000is% Unrecognized interface command,show interfacesprints noMTU line, the port block of
serialize()does not write the field (a probe confirms a reload returns 1500),and
pingcannot send a packet larger than its hard-coded 100 bytes, so nothing in a lab can ever be too bigfor a link.
Six ranked steps, each one PR: (1)
ip mtu <68-9000>+ save/print (S); (2)ping … size(S); (3) enforce theegress MTU — fragments when DF is clear, ICMP type 3 code 4 when it is set (needs Jay's approval, M);
(4) the PMTUD black hole as a lab (needs Jay's approval, M); (5) ICMPv6 Packet Too Big and the 1280 floor
(S); (6) the docs, including the two stale clauses already in
docs/SIMULATION.md:216.Closes no open issue: the queue holds one device request (#130), and no open PR touches an MTU. Continues
docs/plans/counter-reset.md, which names this gap as out of scope.3fe1c43ab47cf43f72027cf43f7202to72bb5a8014