L2TP over IPsec: Difference between revisions
No edit summary |
No edit summary |
||
| Line 83: | Line 83: | ||
==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 set up in order to make sure that it works properly. We already tested the IPsec connection login to one of the routers' | 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 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:Configuration example l2tp pptp testing.png]] | [[File:Configuration example l2tp pptp testing.png]] | ||
If the ping requests are successful, congratulations, your | If the ping requests are successful, congratulations, your setup works! If not, we suggest that you review all steps once more. | ||
While you're connected to the Command Line Interface, you can also check the IPsec connection status again just to be safe. If you don't remember how to do that, refer to the '''[[L2TP_over_IPsec#Testing_the_connection|3.1.3]]''' section of this article. | |||
==See also== | ==See also== | ||