plans: a DHCP DISCOVER does not cross a router, and nothing picks the pool a relayed client needs #2040
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!2040
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "plan/1118-2137"
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 only - no engine, test or workflow edits.
docs/plans/dhcp-relay.md: DHCP is modelled end to end inside one broadcast domain, and stops dead at the router in front of it. Measured ona603c7f7with a two-router lab (PC on R110.20.0.0/24, the only pool on R2): the run recordsno-server/ "no DHCP server in this broadcast domain" and the port stays unaddressed; a server in the same segment with a pool for another subnet answersno-poolwith its own interface address.ip helper-addressanswers% Unrecognized interface command,engine/segment.js:19-20anddocs/SIMULATION.md:314state the absence as deliberate, andnormalizePool()derives option 54 from the pool gateway (dhcp.js:207-213), which a relay would make the router.Six steps, each one PR: the setting (store/print/persist, S, no behaviour change) -> the crossing and giaddr-based pool choice (M, needs Jay's approval) -> option 54 names the server (S) -> the two new failure sentences (S) -> docs, help and the help-completeness list (S) -> running-config paste-back fixture (S). Closes no open issue: the queue is #130 and #803, both device requests.
4a21c5084f55316211215531621121to816c1f3898816c1f3898tocaf8691f68caf8691f68to0c5de536200c5de53620tod8c31b1d49