Ipv4 Dhcp Relay - D-Link NetDefendOS User Manual

5.4. IPv4 DHCP Relay

The DHCP Problem
With DHCP, clients send requests to locate the DHCP server(s) using broadcast messages.
However, broadcasts are normally only propagated across the local network. This means that the
DHCP server and client always need to be on the same physical network. In a large Internet-like
network topology, this means there would have to be a different DHCP server on every network.
This problem is solved by the use of a DHCP relayer.
The DHCP Relayer Solution
A DHCP relayer takes the place of the DHCP server in the local network and acts as the link
between the client and a remote DHCP server. It intercepts requests coming from clients and
relays them to the DHCP server. The DHCP server then responds to the relayer, which forwards
the response back to the client. DHCP relayers use the TCP/IP Bootstrap Protocol (BOOTP) to
implement this relay functionality. For this reason DHCP relayers are sometimes referred to as
BOOTP relay agents.
The Source IP of Relayed DHCP Traffic
For relayed DHCP traffic, the option exists in NetDefendOS to use the interface on which it listens
as the source interface for forwarded traffic or alternatively the interface on which it sends out
the forwarded request.
Although all NetDefendOS interfaces are core routed (that is to say, a route exists by default that
routes interface IP addresses to Core), for relayed DHCP requests this core routing does not apply.
Instead, the interface is the source interface and not core.
Adding Dynamic Routes for Relayed DHCP Leases
This DHCP Relay object property should be enabled to add a route automatically for each DHCP
lease that is handed out to a client via the DHCP relay. This property is enabled in the example
described at the end of this section.
This option can add large numbers of routes to the routing table and a better solution is to set up
a single static route in advance which routes the IP range that could be handed out on the
correct interface.
Enabling Proxy ARP
In some scenarios, it is necessary to add a route for each DHCP lease using the property
described above. Consider the layout shown below, where a single DHCP server is handing out
IPs in the same network range via relay by NetDefendOS to two clients on the separate interfaces
If1 and If2.
Note
DHCP relay is a feature which is currently only available with IPv4 DHCP.
404
Chapter 5: DHCP Services