Tunnel Routing – Setting
There are two major steps to set up Tunnel Routing, define the association of tunnels (see the tables: Basic Setting and Tunnel Group) and set up the routing rules (see the tables: Default Rules, Routing Rules and Persistent Rules). Tunnel Routing works in symmetric FortiWAN sites, when the unit we are talking about or configuring to is called local host (or local site), the opposite unit is then called remote host (or remote site).
Basic Setting
The basic settings are located here: enabling or disabling Tunnel Route logging, define names and entering tunnel routing activation key (if the encryption function is enabled for a tunnel group).
| Tunnel Route Log | Enable or disable logging. FortiWAN provides mechanisms to record, notify and analysis on events refer to the Tunnel Routing service, see “Log”, “Statistics: Tunnel Status”, “Statistics:
Tunnel Traffic”, “Report: TR Status” and “Report: TR Reliability”. |
| Local Host ID | Assign a unique host name for this unit. Tunnels are established between two FortiWAN units. Host ID is used for Tunnel Routing to recognize the units running TR transmission.
Symmetrically, this field is required to the opposite unit. |
| Key | Decide a secret key for tunnel encryption and enter it here, if the encryption function is enabled for a tunnel group. Tunnel Routing encryption employs only one secret key for all tunnel transmissions, therefore, please set the decided key to all the tunnel routing hosts.
This key is used for the data encryption built in Tunnel Routing, not for encryption of IPSec. For an IPSec protection on Tunnel Routing, please refer to “IPSec”. |
| Confirm | Confirm the key above. |