Node

A Node is an instance of a WinGate VPN installation on a machine that has been configured to host or join a VPN.

Master Node

This is the end of the WinGate VPN that has been configured to host the VPN. (Also known as the VPN Host)

Remote/Joining Node

This is the end of the WinGate VPN that has been configured to join (or has joined) the VPN. (Also referred to as the VPN Client)

VPN Participant

A VPN Participant is a machine on the LAN behind each Node connected to a WinGate VPN, that has been configured to share and access resources across the VPN. WinGate VPN Node machines can also be configured to be a VPN Participant if required.

VPN Participation

Each VPN Node can determine how it (and its local network) will participate in any VPN it hosts or joins.

When hosting a VPN, the Master Node machine and its local network can be configured to participate (or not) in a WinGate VPN. This can be set in the Host VPN properties.

When you are configuring a Node to join a VPN, you can have either just the Node machine participate, or you can have both the Node machine and its entire local network participate.

Tunnel

When a remote Node joins a hosted VPN, a tunnel is created across the Internet between the two endpoints to secure the connection.

Encryption

WinGate VPN can encrypt the VPN tunnel with 128 bit two-fish encryption, which means the data will be come indecipherable to someone attempting to scan/hack the connection. While tunnel encryption is optional, it is provided to ensure maximum data security.

Default Gateway

In order for data to be delivered to an address that is not in the same IP address range as the local network, the device on the local network that knows how to send traffic out of the network is usually referred to as the Gateway.

All traffic in the WinGate VPN needs to know how to send data to the other side of the VPN.

To do this, VPN Participant machines in a VPN must have either of the following set in their network properties:

1. Their default gateway set to the machine on the LAN where the WinGate VPN is installed.
2. A route entry configured in the Operating System route table indicating the path to the other side of the VPN through the VPN Node machine.

Server Certificate/Fingerprint

WinGate VPN can use SSL Certificates to uniquely identify VPN server. When a certificate is generated during the Host VPN configuration process, a fingerprint is created. This value can be used by the VPN Client to validate that the correct VPN server is being connected to.

Published Routes

Routing is a central component in WinGate VPN. To extend the network, each side of the VPN needs to know the appropriate routing details in order for data to be sent back and forth across the VPN. This is why each end will publish the relevant routes required.

VPN Host

The VPN Host is an installation of WinGate VPN that has been configured to host a VPN. (Also known as the Master Node)

VPN Client

A VPN Client is an installation of WinGate VPN that has been configured to join a VPN. (Also known as a Remote Node)

Encryption schema

This is the type of encryption used to encrypt data that travels through the VPN tunnels (Strong recommended for greater security)

Control channel

The Control channel is used by WinGate VPN for session control mechanisms, such as join, disconnect, etc provided by the VPN Service. The control channel uses TCP, and is set to use port 809 by default.

Data channel

The Data channel is what WinGate VPN uses to send and receive network data, such as files, application traffic etc. The data channel uses UDP, and is set to use port 809 by default.

Port forwarding

When a WinGate VPN is hosted behind a NAT router solution that has a firewall, then incoming traffic on the ports used for VPN communications (i.e. the Control Channel and the Data channel) must be forwarded to the internal IP address of the Master Node server. (Check your router/firewall documentation on how to do this)

RIP - Routing Information Protocol

WinGate VPN can utilize RIP v2 to distribute routes across the VPN.

VPN Service

VPN Configuration file

Once a WinGate installation has been configured to host a VPN, the configuration details of the VPN can be exported to a file. This file is then distributed to the VPN Client on the remote network wishing to join the VPN, by email or some other means. Once the VPN Client has imported the file into their WinGate VPN installation, they will have the necessary details to join the VPN.