Visual RFC.
ALL RFCs / RFC 2131
Read the RFC ↗
RFC 2131 / MECHANISMS

Reach a server through a relay

02

A relay carries DHCP between a client’s local network and a server elsewhere. Its giaddr field supplies relay context.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 4.1 ↗
RFC 2131 · § 4.1EXAMPLE
3 / 3
Reach a server through a relayLocal broadcast becomes a relayed request with giaddr and returns via the relay.RELAY ACROSS THE BROADCAST BOUNDARYclientrelayserverclient linkbroadcastforwardgiaddr = relay IPserver → relaydeliver locallyUDP server port 67 · client port 68
03
Return to the correct client link.

The server responds to the relay, which delivers the response locally.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Broadcast scope need not limit server placement.

  • DHCP uses UDP server port 67 and client port 68.
  • A relay populates giaddr when forwarding a client request.
  • With nonzero giaddr, the server sends return messages to the relay’s DHCP server port; the relay forwards to the client.
DETAILS

Relay and server policy determine address selection. This example does not imply that relays authenticate every client or that any relay-supplied field can be trusted without deployment controls.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Discover and select an address
  2. Reach a server through a relay
  3. Renew before the lease expires
  4. Validate a remembered address
  5. Check conflicts and release addresses
  6. Request settings without a lease
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗