DHCP RELAY over L2TPv3: Difference between revisions

From Teltonika Networks Wiki
VisualWikitext
mNo edit summary
No edit summary
Line 22: Line 22:


Under '''DHCP SERVER''' set parameters for the DHCP pool.
Under '''DHCP SERVER''' set parameters for the DHCP pool.
[[File:Server new 02 1 fixed.png|none|thumb]]
[[File:Server new 02 1 fixed.png|border|class=tlt-border|750x750px]]




===Set up Mobile WAN as Main WAN===
===Set up Mobile WAN as Main WAN===
Enter to the router’s WebUI, go to '''Network → Interfaces''' press mouse click on the Mobile Wan interface, then drag it to the 1<sup>st</sup> position and then press '''Save & Apply'''.
Enter to the router’s WebUI, go to '''Network → Interfaces''' press mouse click on the Mobile Wan interface, then drag it to the 1<sup>st</sup> position and then press '''Save & Apply'''.
[[File:Server new 03 fix.png|none|thumb]]
[[File:Server new 03 fix.png|border|class=tlt-border|750x750px]]
===Create L2TPv3 instance===
===Create L2TPv3 instance===
Go to router’s WebUI, under '''Service → VPN → L2TP → L2TPv3''' and create new '''L2TPV3''' instance.
Go to router’s WebUI, under '''Service → VPN → L2TP → L2TPv3''' and create new '''L2TPV3''' instance.
Line 33: Line 33:
'''LOCAL SETTING'''
'''LOCAL SETTING'''


Local address: 84.15.155.201
Local address: 84.15.XXX.XXX


Tunnel ID: 100
Tunnel ID: 100
Line 43: Line 43:
'''PEER SETTING'''
'''PEER SETTING'''


Peer address: 84.15.249.182
Peer address: 84.15.XXX.XXX


Peer Tunnel ID: 10
Peer Tunnel ID: 10
Line 60: Line 60:


Layer 2 specific header type: Linux Default
Layer 2 specific header type: Linux Default
[[File:Server new 04 01 fix.png|none|thumb]]
 
[[File:Server new 04 02.png|alt=L2TPv3 Server Settings|center|thumb|480x480px|L2TPv3 Server Settings]]Specify the Local address of your mobile WAN. Local value for Tunnel ID, session ID and Cookie must match with the peer values being used at the other end.
[[File:Server new 04 01 fix.png|border|class=tlt-border|750x750px]]
 
[[File:Server new 04 02.png|border|class=tlt-border|750x750px]]
 
'''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) ==
==DHCP Client Settings (Relay) ==
Line 67: Line 71:
===DHCP Relay===
===DHCP Relay===
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.
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.
[[File:Client 01 fix.png|none|thumb]]
 
[[File:Client 01 fix.png|border|class=tlt-border|750x750px]]
 
'''Note:''' The IPv4 address of the LAN interface is different from the server's LAN interface address, this is necessary to avoid conflicts.
'''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===
===Set up Mobile WAN as Main WAN===
Enter to the router’s WebUI, go to '''Network → Interfaces''' press mouse click on the Mobile Wan interface, then drag it to the 1<sup>st</sup> position and then press '''Save & Apply'''.
Enter to the router’s WebUI, go to '''Network → Interfaces''' press mouse click on the Mobile Wan interface, then drag it to the 1<sup>st</sup> position and then press '''Save & Apply'''.
[[File:Client 02 fix.png|none|thumb]]
 
[[File:Client 02 fix.png|border|class=tlt-border|750x750px]]
 
===Modify Enable-DHCP-renew firewall rule===
===Modify Enable-DHCP-renew firewall rule===
Enter in the router’s WebUI, go to '''Network → Firewall → Traffic rules''' to additionally allow destination port 67.
Enter in the router’s WebUI, go to '''Network → Firewall → Traffic rules''' to additionally allow destination port 67.
[[File:Client 03.png|alt=DHCP renew firewall rule|center|thumb|555x555px|DHCP renew firewall rule]]
 
[[File:Client 03.png|border|class=tlt-border|750x750px]]


===Create L2TPv3 instance===
===Create L2TPv3 instance===
Line 82: Line 91:
'''LOCAL SETTING'''
'''LOCAL SETTING'''


Local address: 84.15.249.182
Local address: 84.15.XXX.XXX


Tunnel ID: 10
Tunnel ID: 10
Line 92: Line 101:
'''PEER SETTING'''
'''PEER SETTING'''


Peer address: 84.15.155.201
Peer address: 84.15.XXX.XXX


Peer Tunnel ID: 100
Peer Tunnel ID: 100
Line 109: Line 118:


Layer 2 specific header type: Linux Default
Layer 2 specific header type: Linux Default
[[File:Client 04 fix.png|none|thumb|747x747px]]
 
[[File:Server new 04 02.png|alt=L2TPv3 Client Settings|center|thumb|523x523px|L2TPv3 Client Settings]]
[[File:Client 04 fix.png|border|class=tlt-border|750x750px]]
 
[[File:Server new 04 02.png|border|class=tlt-border|750x750px]]
 
'''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==
==Testing DHCP over L2TPv3==
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.
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.
[[File:Test 01 fix.png|none|thumb]]
 
[[File:Test 01 fix.png|border|class=tlt-border|750x750px]]
 
Asking for the Address Resolution Protocol (ARP) table is also an other method to find hosts on the LAN network.
Asking for the Address Resolution Protocol (ARP) table is also an other method to find hosts on the LAN network.
[[File:Test 02 fix.png|none|thumb]]
 
[[File:Test 02 fix.png|border|class=tlt-border|750x750px]]

Revision as of 22:43, 25 March 2022

Main Page > General Information > Configuration Examples > Use cases > DHCP RELAY over L2TPv3

Introduction

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

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

I will paste a Topology Image here

DHCP Server Settings

DHCP Pool

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.

Under DHCP SERVER set parameters for the DHCP pool.


Set up Mobile WAN as Main WAN

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.

Create L2TPv3 instance

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

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)

DHCP Relay

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.

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

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.

Modify Enable-DHCP-renew firewall rule

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

Create L2TPv3 instance

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

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

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.

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

Retrieved from "https://wiki.teltonika-networks.com/index.php?title=DHCP_RELAY_over_L2TPv3&oldid=89969"