DHCP RELAY over L2TPv3

From Teltonika Networks Wiki

Introduction[edit | edit source]

A DHCP relay agent allows the DHCP clients to obtain IP addresses from a DHCP server that is not configured on the same LAN.

This article provides a configuration example with details on how to set-up a DHCP relay over a L2TPv3 VPN.

Prerequisites[edit | edit source]

You will need:

  • Two RUT or RUTX devices (one as Server and other as Client)
  • A PC acting as a Host for testing
  • Both routers must have a Public Static or Public Dynamic IP addresses

Configuration Scheme[edit | edit source]

Topology LT2Pv3.png

DHCP Server Settings[edit | edit source]

DHCP Pool[edit | edit source]

Login to the router's WebUI and navigate to Network → Interfaces → Ethernet LAN. Click the 'Edit' button on the right side of the interface to set the LAN network address.

Server new 01 fixed.png

Under DHCP SERVER set parameters for the DHCP pool.

Server new 02 1 fixed.png


Set up Mobile WAN as Main WAN[edit | edit source]

Enter to the router’s WebUI, go to Network → Interfaces press mouse click on the Mobile Wan interface, then drag it to the 1st position and then press Save & Apply. Server new 03 fix.png

Create L2TPv3 instance[edit | edit source]

Go to router’s WebUI, under Service → VPN → L2TP → L2TPv3 and create new L2TPV3 instance.

LOCAL SETTING

Local address: 84.15.XXX.XXX

Tunnel ID: 100

Session ID: 100

Cookie: 12ABCDEF

PEER SETTING

Peer address: 84.15.XXX.XXX

Peer Tunnel ID: 10

Peer Session ID: 10

Peer Cookie: 12ABCDEF

INSTANCE SETTING

Bridge to: LAN

MTU: 1500

Encapsulation: IP

Layer 2 specific header type: Linux Default

Server new 04 01 fix.png

Server new 04 02.png

Note: Specify on "Local address" your mobile WAN public IP. Local value for Tunnel ID, session ID and Cookie must match with the peer values being used at the other end.

DHCP Client Settings (Relay)[edit | edit source]

DHCP Relay[edit | edit source]

Enter the router's WebUI, go to Network → Interface → LAN → DHCP Server and change the "Enable DHCP" field value from Enable to Relay and type in the DHCP Server the IP address of the server. Click Save & Apply.

Client 01 fix.png

Note: The IPv4 address of the LAN interface is different from the server's LAN interface address, this is necessary to avoid conflicts.

Set up Mobile WAN as Main WAN[edit | edit source]

Enter to the router’s WebUI, go to Network → Interfaces press mouse click on the Mobile Wan interface, then drag it to the 1st position and then press Save & Apply.

Client 02 fix.png

Modify Enable-DHCP-renew firewall rule[edit | edit source]

Enter in the router’s WebUI, go to Network → Firewall → Traffic rules to additionally allow destination port 67.

Client 03.png

Create L2TPv3 instance[edit | edit source]

Go to router’s WebUI, under Service → VPN → L2TP → L2TPv3 and create new L2TPV3 instance.

LOCAL SETTING

Local address: 84.15.XXX.XXX

Tunnel ID: 10

Session ID: 10

Cookie: 12ABCDEF

PEER SETTING

Peer address: 84.15.XXX.XXX

Peer Tunnel ID: 100

Peer Session ID: 100

Peer Cookie: 12ABCDEF

INSTANCE SETTING

Bridge to: LAN

MTU: 1500

Encapsulation: IP

Layer 2 specific header type: Linux Default

Client 04 fix.png

Server new 04 02.png

Note: Specify on "Local address" your mobile WAN public IP. Local value for Tunnel ID, session ID and Cookie must match with the peer values being used at the other end.


Testing DHCP over L2TPv3[edit | edit source]

To test the realy settings go to DHCP server to check that devices are able to recieve IP addresses in the range 192.168.10.150 - 192.168.10.170 either via LAN port or Wi-Fi. Access the CLI and run cat /tmp/dhcp.leases to list all DHCP clients.

Test 01 fix.png

Asking for the Address Resolution Protocol (ARP) table is also an other method to find hosts on the LAN network.

Test 02 fix.png