- GateManager Own - Datalogging Scenarios
- LogTunnel Scenarios
- SiteManager Embedded Scenarios
- SiteManger Scenarios
SiteManager GUI - Status & Tunnels
Each status line describes one tunnel instance. The exact information provided depends on the configuration and kind of tunnel, but will consist of any of the following:
When clicking this icon, the view is zoomed in to display status of tunnels to this specific peer only.
This field (which spans all tunnels to a given peer) shows the name and public IP address of the peer.
Shows which interface is used by the tunnel. In case VPN Load Balancing is in effect locally (i.e. between the local UPLINK interfaces), this indicates the "master" interface.
This tunnel is currently not started.
The tunnel is being started. The stage of the tunnel negotiation is displayed in square brackets:
- [MAIN_I1] - [MAIN_I4]: Our end is initiating phase 1 (ISAKMP).
- [MAIN_R1] - [MAIN_R3]: Our end is responding to phase 1.
- [QUICK_I1] - [QUICK_I2]: Our end is initiating phase 2 (IPSEC).
- [QUICK_R1] - [QUICK_R2]: Our end is responding to phase 2.
The tunnel is up and running.
For IPsec tunnels, this field shows the IP address and subnet mask of the local network.
For EasyTunnel Service Tunnels, the text "EasyTunnel Service" is displayed.
For IPsec tunnels, this field shows the IP address and subnet mask of the remote network.
For EasyTunnel Service Tunnels, this field will be blank on the EasyTunnel Client. On the EasyTunnel Server is a link labelled "Remote Management", which allows you to attach to the LAN or DEV1 interface of the EasyTunnel Client.
The encryption algorithm used by the tunnel.
The time elapsed since the tunnel was established.
Note: The default lifetime of a tunnel is approximately 480 minutes (8 hours), after which a new instance will be negotiated.
The time elapsed since traffic was last seen on the tunnel in each direction.
The VPN Load Balancing ratio between the local UPLINK interfaces (in "master":"slave" order, not necessarily UPLINK:UPLINK2), shown for each direction.
The VPN Load Balancing ratio between the two addresses of the peer (in "master":"slave" order, not necessarily "primary":"backup"), shown for each direction.
The compression ratio in each direction, or 'off' if compression is not enabled.
The number of bytes that have travelled through the tunnel in each direction.
Note 1: The numbers are approximations; they can vary a few bytes on each packet because of IPsec headers, padding, etc.
Note 2: If compression is enabled, this is the number of bytes before compression for outgoing traffic, and the number of bytes after decompression for incoming traffic.
The number of packets that have travelled through the tunnel in each direction.
Click this icon to start the tunnel.