M2M Cellular Gateway
Gateway
Netmask
Encryption Cipher
Hash Algorithm
Scenario Operation Procedure
In above diagram, Network‐A is in the headquarters, and the subnet of its Intranet is
10.0.76.0/24. The security gateway for Network‐A has the IP address of 10.0.76.2 for
LAN interface and 203.95.80.22 for WAN interface. It serves as an OpenVPN server.
Network‐B is in the mobile office and the subnet of its Intranet is 10.0.75.0/24. The
security gateway for Network‐B has the IP address of 192.168.1.253 for LAN interface
and 118.18.81.33 for WAN interface. It serves as an OpenVPN client.
Establish an OpenVPN VPN tunnel by starting from the OpenVPN client site. So hosts in
Network‐B can access hosts or servers in Network‐A. But can't access from Network‐A
to Network‐B.
To communicate each other securely between Intranets of 10.0.75.0/24 and
192.168.1.0/24, please add route policy according to the environment by checking the
"Enable" box of Advanced Configuration.
OpenVPN VPN Client Scenario
When you want the security gateway to play an OpenVPN client role, check the "Enable" box and
choose "Client" option in the "OpenVPN Configuration" window. And make its related configuration in
following sections.
OpenVPN Client Configuration
"OpenVPN Client Configuration" window can let you enable the OpenVPN client function by
checking the "Enable" box.
OpenVPN Client List
"OpenVPN Client List" window shows your defined OpenVPN clients and their tunnel status. Only
some important information for all tunnels are shown in the list in following diagram.
Index skipping is used to reserve slots for new function insertion, when required.
10.0.76.253
255.255.255.0/24
Blowfish
SHA‐1
240