DHCP is a complete library with no caller: ip address dhcp never gets a lease #1051

Closed
opened 2026-11-08 08:22:03 +00:00 by jaylouisw · 0 comments
Owner

engine/dhcp.js models DHCPv4 properly - pool normalisation, validation, DISCOVER/OFFER,
REQUEST/ACK-NAK, renewals, reservations, exclusions, lease expiry - and has its own passing suite.

engine/simulator.js never requires it:

$ grep -c "dhcp" engine/simulator.js
0

So a host configured with ip address dhcp sets iface.dhcp = true, prints a confirmation, and
stays unaddressed forever:

PC-d2#show ip interface brief
Interface              IP-Address      OK? Method Status                Protocol
eth0                  unassigned      YES  DHCP    up                    up

Every ping it sends then fails silently, and the lab reads as a broken configuration rather than a
missing feature. SIMULATION.md §5.1 documents this honestly; the README
previously listed "DHCP client + server" as implemented.

What is needed

  • The exchange in the data path: DISCOVER, OFFER, REQUEST, ACK as real frames, so the timeline shows
    them and a lab can debug a wrong pool the way it would on real gear.
  • A server that never allocates its own address, an exhausted pool that says so, and a segment with
    no server that fails with a reason instead of silence.
  • DHCP relay, Option 82 and snooping stay out of scope until the base case works.
`engine/dhcp.js` models DHCPv4 properly - pool normalisation, validation, DISCOVER/OFFER, REQUEST/ACK-NAK, renewals, reservations, exclusions, lease expiry - and has its own passing suite. `engine/simulator.js` never requires it: ``` $ grep -c "dhcp" engine/simulator.js 0 ``` So a host configured with `ip address dhcp` sets `iface.dhcp = true`, prints a confirmation, and stays unaddressed forever: ``` PC-d2#show ip interface brief Interface IP-Address OK? Method Status Protocol eth0 unassigned YES DHCP up up ``` Every ping it sends then fails silently, and the lab reads as a broken configuration rather than a missing feature. [SIMULATION.md §5.1](docs/SIMULATION.md) documents this honestly; the README previously listed "DHCP client + server" as implemented. ## What is needed - The exchange in the data path: DISCOVER, OFFER, REQUEST, ACK as real frames, so the timeline shows them and a lab can debug a wrong pool the way it would on real gear. - A server that never allocates its own address, an exhausted pool that says so, and a segment with no server that fails with a reason instead of silence. - DHCP relay, Option 82 and snooping stay out of scope until the base case works.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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#1051
No description provided.