0
edits
Changes
GRE Tunnel configuration examples (view source)
Revision as of 07:46, 15 July 2019
, 07:46, 15 July 2019Just a misspelling ...
[[File:How to add new gre tunnel instance v2.png]]
[[File:How to add new gre tunnel instance v2.png]]
----
----
* Click the "Edit" button located to the right of the newly created GRE Tunnel instance to enter the settings window. Bellow is capture of configurations for both GRE Tunnel instances:
* Click the "Edit" button located to the right of the newly created GRE Tunnel instance:
[[File:Gre tunnel configuration example.png]]
[[File:How to edit gre tunnel.png]]
----
* You will be redirected to the settings window where you can start configuring the GRE Tunnel instance. Bellow is capture of configurations for both GRE Tunnel instances:
[[File:Gre tunnel configuration example v2.png|1150px]]
* Below are explanations of the parameters highlighted in the figure above. Other parameters (not highlighted) are defaults. You can find descriptions for these parameters in the '''[[VPN#GRE Tunnel|VPN manual page, GRE Tunnel section]]'''
** '''Enable''' - enables the GRE Tunnel instance
** '''Remote endpoint IP address''' - the Public 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
** '''Local tunnel IP''' - virtual IP address the GRE Tunnel instance (make sure it is '''unique''' for each instance)
** '''Local tunnel netmask''' - subnet mask of the local GRE Tunnel
** '''Enable Keep alive''' - enables the tunnel's keep alive function. When enabled, the instance sends ICMP packets to the specified host at the specified frequency. If no response is received, the instance attempts to restart the connection
*** '''Keep alive Host''' - hostname or IP address to which Keep alive packets will be sent to. Best to use a hostname/IP address belonging to the opposite instance's LAN. For this example we just use the other router's LAN IP address
*** '''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.
==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 devices' 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==