Summary of the Network
| Headquarters | Branch | |
| WAN1 | 211.21.33.186 | Dynamic IP |
| WAN2 | Dynamic IP | Dynamic IP |
| LAN | 192.168.1.0/24 | 192.168.2.0/24 |
The settings for the headquarters:
Set the field Local Host ID as “HQ”.
Local Host ID: HQ
| Group Name | Remote Host
ID |
Algorithm | Tunnels
Local IP |
Remote IP | Weight |
| HQ-Branch | Branch | Round-Robin | 211.21.33.186 | Dynamic IP at
WAN1 |
1 |
| Dynamic IP at
WAN2 |
Dynamic IP at
WAN2 |
1 |
Routing Rules
| Source | Destination | Service | Group | Fail-Over |
| 192.168.1.0/255.255.255.0 | 192.168.2.0/255.255.255.0 | Any | HQ-Branch | No-Action |
The settings for the branch1
Set the field Local Host ID as Branch
Local Host ID: Branch
Tunnel Group
| Group Name | Remote Host
ID |
Algorithm | Tunnels
Local IP |
Remote IP | Weight |
| Branch-HQ | HQ | Round-Robin | Dynamic IP at
WAN1 |
211.21.33.186 | 1 |
| Dynamic IP at
WAN2 |
Dynamic IP at
WAN2 |
1 |
Routing Rules
| Source | Destination | Service | Group | Fail-Over | |
| 192.168.2.0/255.255.255.0 | 192.168.1.0/255.255.255.0 | Any | Branch-HQ | No-Action |
Example 3 Forwarding of Tunnel Routing
A company operates two branch offices oversea. Each office deploys a public line to access Internet. Each branch office sets up an individual tunnel with the headquarters to access the corporate Intranet.
Requirements
The LAN links in branch 1 and branch 2 can communicate with each other via the tunnel established with the headquarter.
Summary of the Network
| Headquarters | Branch 1 | Branch 2 | |
| WAN 1 | No | 1.1.1.1 | No |
| WAN 2 | No | No | 2.2.2.2 |
| WAN 3 | 3.3.3.3 | No | No |
| LAN | 192.168.3.0/24 | 192.168.1.0/24 | 192.168.2.0/24 |