9,293
edits
Changes
no edit summary
To begin configuration, click the button that looks like a pencil located next to the instance. Refer to the figure and table below for information on the fields located in the GRE instance configuration section.
To begin configuration, click the button that looks like a pencil located next to the instance. Refer to the figure and table below for information on the fields located in the GRE instance configuration section.
[[File:Networking_rutx_vpn_gre_gre_configuration_main_settings_v2.png|border|class=tlt-border]]
[[File:Networking_rutx_vpn_gre_gre_configuration_main_settings_v4.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<td>Tunnel source</td>
<td>Tunnel source</td>
<td>network interface; default: <b>none</b></td>
<td>network interface; default: <b>-</b></td>
<td>Network interface used to establish the GRE Tunnel.</td>
<td>Network interface used to establish the GRE Tunnel.</td>
</tr>
</tr>
<td>integer; default: <b>1476</b></td>
<td>integer; default: <b>1476</b></td>
<td>Sets the maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.</td>
<td>Sets the maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.</td>
</tr>
</tr>
<tr>
<tr>
<td>Outbound key</td>
<td>Outbound key</td>
<td>integer [0..4294967295]; default: <b>none</b></td>
<td>integer [0..4294967295]; default: <b>none</b></td>
<td>A key used to identify outgoing packets. This value should match the "Inbound key" value set on the opposite GRE instance or both key values should be omitted on both sides.</td>
<td>Key for outgoing packets. This value should match the 'Inbound key' value set on the opposite GRE instance or both key values should be omitted on both sides.</td>
</tr>
</tr>
<tr>
<tr>
<td>Inbound key</td>
<td>Inbound key</td>
<td>integer [0..4294967295]; default: <b>none</b></td>
<td>integer [0..4294967295]; default: <b>none</b></td>
<td>A key used to identify incoming packets. This value should match the "Outbound key" value set on the opposite GRE instance or both key values should be omitted on both sides.</td>
<td>Key for incoming packets. This value should match the 'Outbound key' value set on the opposite GRE instance or both key values should be omitted on both sides.</td>
</tr>
</tr>
<tr>
<tr>
<td>Path MTU Discovery</td>
<td>Path MTU Discovery</td>
<td>off {{!}} on; default: <b>on</b></td>
<td>off {{!}} on; default: <b>off</b></td>
<td>When unchecked, sets the <i>nopmtudisc</i> option for tunnel. Can not be used together with the TTL option.</td>
<td>When unchecked, sets the <i>nopmtudisc</i> option for tunnel. Can not be used together with the TTL option.</td>
</tr>
<tr>
<td>TTL</td>
<td>integer [0..255]; default: <b>255</b></td>
<td>Sets a custom TTL (Time to Live) value for encapsulated packets. TTL is a field in the IP packet header which is initially set by the sender and decreased by 1 on each hop. When it reaches 0 it is dropped and the last host to receive the packet sends an ICMP "Time Exceeded" message back to the source.</td>
</tr>
</tr>
<tr>
<tr>
<td>Keep alive</td>
<td>Keep alive</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>off {{!}} <span style="color:blue">on</span>; default: <b>off</b></td>
<td>Turns "keep alive" on or off. The "keep alive" feature sends packets to the remote instance in order to determine the health of the connection. If no response is received, the device will attempt to re-establish the tunnel.</td>
<td>The 'keep alive' feature sends packets to the remote instance in order to determine the health of the connection. If no response is received for [Keep alive retries] times, the device will mark the tunnel as DOWN.</td>
</tr>
<tr>
<td><span style="color:blue">Keep alive interval</span></td>
<td>integer [1..255]; default: <b>20</b></td>
<td>Frequency (in seconds) at which 'keep alive' packets are sent to the remote instance.</td>
</tr>
</tr>
<tr>
<tr>
<td>Keep alive interval</td>
<td><span style="color:blue">Keep alive retries</span></td>
<td>integer [0..255]; default: <b>none</b></td>
<td>integer [1..255]; default: <b>3</b></td>
<td>Frequency (in seconds) at which "keep alive" packets are sent to the remote instance.</td>
<td>Amount of keep alive packets to lose before marking tunnel as DOWN.</td>
</tr>
</tr>
<tr>
<tr>
<b>Routing settings</b> are used to configure routes to networks that are behind the device that hosts the opposite GRE instance. To add a new route, simply click the 'Add' button. For information on configuring the route refer to the figure and table below.
<b>Routing settings</b> are used to configure routes to networks that are behind the device that hosts the opposite GRE instance. To add a new route, simply click the 'Add' button. For information on configuring the route refer to the figure and table below.
[[File:Networking_rutx_vpn_gre_gre_configuration_routing_settings_v2.png|border|class=tlt-border]]
[[File:Networking_rutx_vpn_gre_gre_configuration_routing_settings_v3.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<td>netmask; default: <b>none</b></td>
<td>netmask; default: <b>none</b></td>
<td>Subnet mask of the network behind the device that hosts the remote GRE instance.</td>
<td>Subnet mask of the network behind the device that hosts the remote GRE instance.</td>
</tr>
<tr>
<td>Actions</td>
<td>-(interactive button)</td>
<td>Removes configuration.</td>
</tr>
</tr>
</table>
</table>
