31,703
edits
Changes
no edit summary
* '''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==
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 set up in order to make sure that it works properly. We already tested the IPsec connection login to one of the routers' WebUI 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:Configuration example l2tp pptp testing.png]]
If the ping requests are successful, congratulations, your set up works! If not, we suggest that you review all steps once more.
If you're using the server as a web proxy, end devices connected to the L2TP client router should have the Public IP address of the L2TP server. You can visit this website to check the Public IP address: http://www.whatsmyip.org/
==See also==
==See also==
