DHCP Relay

Cross-Subnet DHCP · Option 82 · Multi-Server · Lease Renewal · DECLINE & NAK · RFC 3046

A free protocol simulators tool from NetOcta that runs entirely in your browser — no sign-up or install.

About this tool

A DHCP broadcast cannot simply cross a router to reach a remote server. A relay acts as the messenger between the client's subnet and that server. This simulator shows cross-subnet allocation alongside Option 82, multiple-server and renewal scenarios. Beginners can follow the messages first, then inspect the fields that help the server choose the correct address pool.

How it works

  1. Choose a relay scenario and locate client, relay and server.
  2. Play the client's request toward the relay.
  3. Inspect the forwarded message and server response.
  4. Follow the reply back to the client and check the lease.

Worked example

A client sits in 10.1.1.0/24 with relay interface 10.1.1.1. The relay forwards its request to a server on another subnet and supplies giaddr 10.1.1.1. The server uses that subnet context to offer 10.1.1.100 rather than an address from the server's own LAN.

Common mistakes

Do not assume ordinary routers forward DHCP broadcasts automatically. A reachable server also needs a matching scope and a return path. Option 82 provides relay information; it is not the client's requested IP address.

FAQ

Is the relay the DHCP server?

Not necessarily. The relay forwards messages; the server selects addresses and manages leases. One device may support both roles, but they remain distinct functions.