plans: a DHCP DISCOVER does not cross a router, and nothing picks the pool a relayed client needs #2040

Merged
jaylouisw merged 1 commit from plan/1118-2137 into main 2026-11-18 22:52:33 +00:00
Owner

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 on a603c7f7 with a two-router lab (PC on R1 10.20.0.0/24, the only pool on R2): the run records no-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 answers no-pool with its own interface address. ip helper-address answers % Unrecognized interface command, engine/segment.js:19-20 and docs/SIMULATION.md:314 state the absence as deliberate, and normalizePool() 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.

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 on `a603c7f7` with a two-router lab (PC on R1 `10.20.0.0/24`, the only pool on R2): the run records `no-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 answers `no-pool` with its own interface address. `ip helper-address` answers `% Unrecognized interface command`, `engine/segment.js:19-20` and `docs/SIMULATION.md:314` state the absence as deliberate, and `normalizePool()` 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.
plans: a DHCP DISCOVER does not cross a router, and nothing picks the pool a relayed client needs
All checks were successful
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 10s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Arm auto-merge (pull_request) Successful in 3s
4a21c5084f
forgejo-actions force-pushed plan/1118-2137 from 4a21c5084f
All checks were successful
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 10s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Arm auto-merge (pull_request) Successful in 3s
to 5531621121 2026-11-18 21:41:45 +00:00
Compare
jaylouisw force-pushed plan/1118-2137 from 0c5de53620 to d8c31b1d49
All checks were successful
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 5s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Successful in 55s
CI / Test (Node 22) (pull_request) Successful in 1m2s
CI / Test (Node 18) (pull_request) Successful in 1m5s
CI / Arm auto-merge (pull_request) Successful in 4s
2026-11-18 22:47:06 +00:00
Compare
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-18 22:52:09 +00:00
jaylouisw deleted branch plan/1118-2137 2026-11-18 22:52:35 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!2040
No description provided.