31,703
edits
Changes
GRE Tunnel configuration examples (view source)
Revision as of 16:29, 15 June 2018
, 16:29, 15 June 2018no edit summary
** '''Enable''' - enables the GRE Tunnel instance
** '''Enable''' - enables the GRE Tunnel instance
** '''Remote endpoint IP address''' - the Public IP address of the opposite router
** '''Remote endpoint IP address''' - the Public IP address of the opposite router
** '''Remote network''' - LAN IP address of the opposite router
** '''Remote network''' - LAN IP address of the opposite router. This and Remote network netmask are used for '''remote LAN access'''
** '''Remote network netmask''' - subnet mask of the opposite router's LAN
** '''Remote network netmask''' - subnet mask of the opposite router's LAN
** '''Local tunnel IP''' - virtual IP address the GRE Tunnel instance
** '''Local tunnel IP''' - virtual IP address the GRE Tunnel instance
*** '''Keep alive interval''' - the period (in seconds) at which Keep alive packets will be sent to the specified host
*** '''Keep alive interval''' - the period (in seconds) at which Keep alive packets will be sent to the specified host
'''NOTE''': remember to replace certain parameter values (like IP addresses) with your own relevant data.
'''NOTE''': remember to replace certain parameter values (like IP addresses) with your own relevant data.
==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. In order to test a GRE Tunnel connection, login to one of the routers' WebUIs and go to '''Services → CLI'''. Login with user name: '''root''' and the router's admin password. From there you should then be able to '''ping''' the opposite instance's virtual IP address. To use a ping command, type '''ping <ip_address>''' and press the "Enter" key on your keyboard:
[[File:Configuration example ipsec testing.png]]
You can also test if LAN access is working the same way. Instead of pinging the opposite instance's LAN IP address, ping one of the end device's IPs. One common issue that can be encountered here is that the end devices '''might need their DHCP leases renewed'''. There are many methods of accomplishing this, but the easiest and most accessible way is to simply disconnect and reconnect the LAN cable to device or the router that it's connected to.
If the ping requests are successful, congratulations, your setup works! If not, we suggest that you review all steps once more.
==See also==
==See also==
