DHCP Relay configuration example
The information on this page is updated in accordance with the 00.07.08 firmware version .
Introduction
DHCP Relay is a router that forwards IP addresses from the DHCP Server to the user devices, even if the server is on a different network. The main benefit of this approach is that a single DHCP Server can distribute IP addresses to multiple networks. Bellow you will find an example of how to configure a basic DHCP Relay configuration.
Prerequisites & Topology
Prerequisites
- For this configuration you will need 2 routers. One as a DHCP Server and the other as a DHCP Relay.
- DHCP Relay device WAN port needs to be connected to DHCP server LAN port.
Topology
DHCP server network settings:
LAN IP/subnet: 192.168.4.1/24
DHCP Relay network settings:
LAN IP/subnet: 192.168.2.1/24 WAN IP: 192.168.4.194
The DHCP relay service enables the forwarding of DHCP broadcast messages to network segments that a client computer is not directly connected to. It allows a single DHCP server to be shared across different logical network segments separated by a firewall. Unlike handling IP addresses, the DHCP relay service sends unicast messages rather than broadcast messages.
When a client needs a DHCP-assigned IP address, it broadcasts a request to the network attached to its interface. The DHCP relay service on the firewall intercepts this request on an interface connected to the same network, such as LAN 192.168.2.0/24. The relay service then unicasts the request to all configured DHCP servers in the LAN and receives an IP address offer from a DHCP server (e.g., 192.168.4.1) that has a range of addresses configured for the client's network segment (e.g., 192.168.2.0/24). This offer is forwarded to the client. If the client accepts the offer, it acknowledges the DHCP address and assigns it to its interface immediately.
Configuration
If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Advanced" button, located at the top of the WebUI.
DHCP Server Configuration
LAN Configuration
Open router’s WebUI → Network → LAN click 
on current available LAN interface configuration:
General Settings
Make the following changes:
- Enter IPv4 address: 192.168.4.1
Lease Configuration
Open router’s WebUI → System → Mantenance → CLI
Enter this command to CLI:
echo "dhcp-range=192.168.2.100,192.168.2.200,12h" >> /etc/dnsmasq.conf
Static Route Configuration
Open WebUI → Network → Routing → Static routes
Static IPv4 Routes
click 
and apply this to the route:
- Select Interface: lan | Enter Target: 192.168.2.0 | Enter IPv4-Netmask: 255.255.255.0 | Enter IPv4-Gateway: 192.168.4.194
DHCP Relay Configuration
Relay WAN Confiuration
Open router’s WebUI → Network → WAN → WAN interfaces click current available WAN interface configuration:
General Settings
Make the following changes:
- Select Protocol: Static
- Enter IPv4 address: 192.168.4.194
Relay LAN Confiuration
Open router’s WebUI → Network → LAN click current available LAN interface configuration:
General Settings
Make the following changes:
- Enter IPv4 address: 192.168.2.1
Firewall Rule Configuration
Open router’s WebUI → Network → Firewall → Traffic Rules click on Allow-DHCP-Renew rule:
Firewall - Traffic Rules - Allow-DHCP-Renew
- Enter Destination Port: 67
DHCP Replay Configuration
Open router’s WebUI → Network → DHCP → Server Settings → IPv4 → DHCPv4 servers click current available server interface configuration:
DHCPv4: lan
Make the following changes:
- Enable: on
- Select DHCPv4 mode: Relay
- Enter DHCP server address: 192.168.4.1
Testing the configuration
Navigate to the Open DHCP server's WebUI -> Status -> Network -> LAN. If the configuration is successful, the lease for the 192.168.2.0/24 network should be displayed in the WebUI DHCP lease list.
Additional notes
Note: It's strongly recommended to use static IP configuration for DHCP Relay WAN interface otherwise there might be cases when WAN interface will receive new IP address which will cause static route to stop working.