DHCP Relay configuration example: Difference between revisions

Latest revision as of 13:44, 5 August 2024

Main Page > General Information > Configuration Examples > Router control and monitoring > 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.

@@ Line 1: / Line 1: @@
-==Introduction==
+<p style="color:red">The information on this page is updated in accordance with the [https://wiki.teltonika-networks.com/view/FW_%26_SDK_Downloads'''00.07.08'''] firmware version .</p>
-'''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.
+===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.
-==Configuration overview and prerequisites==
+====Topology====
+----
+DHCP server network settings:
+ LAN IP/subnet: 192.168.4.1/24
+DHCP Relay network settings:
-For this configuration you will need 2 routers. One as a DHCP Server and the other as a DHCP Relay.
+ LAN IP/subnet: 192.168.2.1/24
+ WAN IP: 192.168.4.194
-'''Prerequisites:'''
+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.
-DHCP Relay device WAN port needs to be connected to DHCP server LAN port.
+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.
-DHCP Relay network settings:
+[[File:708576_Topo.png|border|class=tlt-border| center|1000px]]
+===Configuration===
+----
+{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
+| series = RUTX
+}}
+====DHCP Server Configuration====
+----
+=====LAN Configuration=====
+Open router’s '''WebUI → Network → LAN''' click [[File:Pencil2.png]]on current available LAN interface configuration:
+======General Settings======
+----
+Make the following changes:
+# Enter IPv4 address: '''192.168.4.1'''
+[[File:DHCP_RELAY_1_1.png|border|class=tlt-border|center]]
+=====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
+[[File:DHCP_RELAY_2.png|border|class=tlt-border|center|1100px]]
+=====Static Route Configuration=====
+----
+Open '''WebUI → Network → Routing → Static routes'''
+======Static IPv4 Routes======
+----
+click [[File:Add Button.png|40x70px]] 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'''
- LAN IP/subnet: 192.168.2.1/24
+[[File:DHCP_RELAY_3.png|border|class=tlt-border|center|1100px]]
- WAN IP: 192.168.4.194
-DHCP server network settings:
+====DHCP Relay Configuration====
+----
+=====Relay WAN Confiuration=====
+----
+Open router’s '''WebUI → Network → WAN → WAN interfaces''' click [[File:Pencil2.png]]current available WAN interface configuration:
+======General Settings======
+----
+Make the following changes:
- LAN IP/subnet: 192.168.4.1/24
+# Select Protocol: '''Static'''
+# Enter IPv4 address: '''192.168.4.194'''
-'''Configuration scheme:'''
+[[File:DHCP_RELAY_7.png|border|class=tlt-border|center|1000px]]
-[[File:Networking_rutx_manual_lan_static_dhcp_server_relay_scheme_v2.png|border|class=tlt-border]]
+=====Relay LAN Confiuration=====
+Open router’s '''WebUI → Network → LAN''' click [[File:Pencil2.png]]current available LAN interface configuration:
+======General Settings======
+----
+Make the following changes:
+# Enter IPv4 address: '''192.168.2.1'''
-==Configuration Steps==
+[[File:DHCP_RELAY_4.png|border|class=tlt-border|center]]
-. Enable DHCP Relay feature on device which will relay DHCP requests. In WebUI navigate to '''Network -> Interface -> LAN -> DHCP Server''' and change '''Enable DHCP''' field value from Enable to Relay and then type in the DHCP Server IP address and click on Save & Apply.
+=====Firewall Rule Configuration=====
+Open router’s '''WebUI → Network → Firewall → Traffic Rules''' click [[File:Pencil2.png]] on Allow-DHCP-Renew rule:
+======Firewall - Traffic Rules - Allow-DHCP-Renew======
+----
+# Enter Destination Port: '''67'''
-[[File:Networking_rutx_manual_lan_static_dhcp_server_dhcp_relay_configuration_v1.png|border|class=tlt-border]]
+[[File:DHCP_RELAY_8.png|border|class=tlt-border|center]]
-. Modify Enable-DHCP-renew firewall rule in '''Network -> Firewall -> Traffic rules''' to additionally allow destination port 67.
-[[File:Networking_rutx_manual_firewall_trafic_rules_configuration_for_dhcp_relay_v1.png|border|class=tlt-border]]
-. DHCP Server must be able to assign addresses from 192.168.2.0/24 IP address pool. If DHCP Server is a Teltonika device running RUTOS then you can add this address pool via router's CLI by running command:
+=====DHCP Replay Configuration=====
+----
+Open router’s '''WebUI → Network → DHCP → Server Settings → IPv4 → DHCPv4 servers''' click [[File:Pencil2.png]]current available server interface configuration:
+======DHCPv4: lan======
+----
+Make the following changes:
- echo "dhcp-range=192.168.2.100,192.168.2.200,12h" >> /etc/dnsmasq.conf
+# Enable: '''on'''
+# Select DHCPv4 mode: '''Relay'''
+# Enter DHCP server address: '''192.168.4.1'''
-* 192.168.2.100 - specifies start of DHCP address pool range
+[[File:DHCP_RELAY_5.png|border|class=tlt-border|center|1000px]]
-* 192.168.2.200 - specifies end of DHCP address pool range
-* 12h - specifies DHCP lease time
-. In this topology DHCP Server has no route to DHCP Relay's network so it must be added manually. Static route can be added via '''Network -> Routing -> Static IPv4 routes'''.
+===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.
-[[File:Networking_rutx_manual_routing_ip4_static_routes_configuration_v1.png|border|class=tlt-border]]
+[[File:DHCP_RELAY_11.png|border|class=tlt-border|center|1000px]]
-* Interface: Network interface where DHCP Relay resides
-* Target: Network of DHCP Relay
-* IPv4 netmask: Subnet of DHCP Relay network
-* IPv4 Gateway: IP address of DHCP relay interface which is connected to DHCP Server
-==Additional notes==
+===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.
 [[Category:Router control and monitoring]]