Changes

----

----

* '''Server configuration''':

* '''Server configuration''':

# '''Enable''' - when checked, enables the instance

 

# '''Local IP''' - the server's virtual IP address

* '''Enable''' - when checked, enables the instance

# '''Remote IP range''' parameters - the range of virtual IP addresses that will be assigned to connecting clients

* '''Local IP''' - the server's virtual IP address

# '''User name''' and '''Password''' - authentication information used to authenticate connecting clients

* '''Remote IP range''' parameters - the range of virtual IP addresses that will be assigned to connecting clients

* '''User name''' and '''Password''' - authentication information used to authenticate connecting clients

----

----

* '''Client configuration''':

* '''Client configuration''':

[[File:Networking rutxxx configuration l2tp client configuration v1.jpg|border|class=tlt-border|1100px]]

[[File:Networking rutxxx configuration l2tp client configuration v2.png|border|class=tlt-border|1100px]]

* '''Enable''' - when checked, enables the instance

# '''Enable''' - when checked, enables the instance

* '''Server''' - L2TP server's Public IP address

# '''Server''' - L2TP server's Public IP address

* '''User name''' and '''Password''' - authentication information. Used the values specified in the Server's configuration  

# '''User name''' and '''Password''' - authentication information. Used the values specified in the Server's configuration

==Testing the setup==

==Testing the setup==

If you've followed all the steps presented above, your configuration should be finished. But as with any other configuration, it is always wise to test the setup in order to make sure that it works properly. We already tested the IPsec connection in the '''[[L2TP_over_IPsec#Testing_the_connection|3.1.3]]''' section of this article. To test an L2TP connection, login to one of the routers' WebUIs and go to '''Services → CLI'''. Login with user name: '''root''' and the router's admin password. You should then be able to '''ping''' the opposite instance, i.e., if you logged in to the server's CLI, you should be able to ping the client's virtual IP address, and vice versa. To use a ping command, type '''ping <ip_address>''' and press the "Enter" key on your keyboard:

If you've followed all the steps presented above, your configuration should be finished. But as with any other configuration, it is always wise to test the setup in order to make sure that it works properly. We already tested the IPsec connection in the '''[[L2TP_over_IPsec#Testing_the_connection|3.1.3]]''' section of this article. To test an L2TP connection, login to one of the routers' WebUIs and go to '''Services → CLI'''. Login with user name: '''root''' and the router's admin password. You should then be able to '''ping''' the opposite instance, i.e., if you logged in to the server's CLI, you should be able to ping the client's virtual IP address, and vice versa. To use a ping command, type '''ping <ip_address>''' and press the "Enter" key on your keyboard:

[[File:Networking rutxxx configuration examples l2tp over ipsec ping v1.jpg|border|class=tlt-border]]

[[File:Networking rutxxx configuration examples l2tp over ipsec ping v2.png|border|class=tlt-border|600px]]

If the ping requests are successful, congratulations, your setup works! If not, we suggest that you review all steps once more.

If the ping requests are successful, congratulations, your setup works! If not, we suggest that you review all steps once more.