Specifications

37 / 80
o Tunnel the following network
If there are TCP/IP connected devices in Arctic’s LAN (on contrary to the setup,
where there are only serial connected devices in Arctic side), the Arctic’s LAN
needs to be tunneled over the VPN in order to provide the end-to-end connectivity
with M2M GW LAN and Arctic LAN.
In this example, there is an Ethernet-connected device, let’s say a computer (with
IP address 10.10.10.2), in Arctic’s LAN, which must have a route to M2M GW’s
LAN.
• Remote network IP
The LAN on the opposite
side of the VPN tunnel, i.e. the Arctic’s LAN network address.
Needs to be configured if the “Tunnel the following network” routing mode is chosen. In
this example fill with value 10.10.10.0.
• Remote network mask
The netmask of the Arctic’s LAN network address.
In this example 255.255.255.0.
• Username
The username of the L2TP peer, this must match the Arctic’s username in Arctic’s L2TP-
VPN settings. The parameter must also match the hostname of the Arctic.
In this example, fill with value arctic1.
• Password
The password of L2TP peer. Must match the password in Arctic’s L2TP-VPN settings
.
In this example, fill with value password.
4. Click “Confirm” button to apply the changes.
13.7.3. SSH-VPN configuration
The configuration for SSH-VPN is done in similar way than the L2TP-VPN apart from the difference
of SSH public keys that has to be exchanged between the M2M GW and Arctic. Without proper
SSH public keys in place, the SSH-VPN is not able to work.
See the M2M GW’s user’s manual, Chapter 6: SSH-VPN Configuration for details of configuring the
SSH-VPN.
1. Click the SSH-VPN icon in M2M GW’s main screen.
• Figure 44: SSH-VPN icon
2. The screen in Figure 45: M2M GW's SSH-VPN configuration will open; note that
there is already a configured Arctic with the example configuration settings in the
figure in this document.