Talk:Dynamic Host Configuration Protocol

DHCPACK destination address

The example DHCPACK message lists 192.168.1.100 as its destination address in the IP section which contradicts teaching literature (Kurose & Ross: Computer Networking: A Top-Down Approach, where DHCP ACK is still being broadcasted) and seems to be at odds with RFC2131, Section 3.2.3. The example might still be correct, but if so an explanation why the offered IP address may already be used would be helpful.

Paul4096 (talk) 10:21, 14 October 2018 (UTC)

RFC2131, Section 4.1 supports the example DHCPOFFER and DHCPACK message as correct:

Normally, DHCP servers and BOOTP relay agents attempt to deliver DHCPOFFER, DHCPACK and DHCPNAK messages directly to the client using unicast delivery. The IP destination address (in the IP header) is set to the DHCP 'yiaddr' address (i.e not 255.255.255.255) and the link-layer destination address is set to the DHCP 'chaddr' address.

Techie3 (talk) 05:56, 9 October 2021 (UTC)

IPv4 addresses used

The address used in article are in 192.168.1.0/24.

Should the addresses comply RFC 5737 - IPv4 Address Blocks Reserved for Documentation? It reserves blocks 192.0.2.0/24 (TEST-NET-1), 198.51.100.0/24 (TEST-NET-2) and 203.0.113.0/24 (TEST-NET-3) for documentation purposes. — Preceding unsigned comment added by Cfturkja (talk • contribs) 12:04, 20 November 2021 (UTC)

DHCP OP codes / message types

Should the OP byte in the listed DHCP packet examples only be one of the two defined types in RFC2131: BOOTREQUEST (0x01) or BOOTREPLY (0x02)? 96.38.135.89 (talk) 01:13, 26 June 2024 (UTC)

DHCP Header: Options Offset

Is the Offset of the options field in the examples correct? I assume that should be right after the "magic coockie" and therefore at offset 268 instead of 292, right? Winejoe (talk) 10:32, 2 December 2024 (UTC)