When using WinGate VPN, the WinGate VPN Node machine must have a working Internet connection, or at least have access to the Internet from behind an appropriate Internet router.
To assist with this, WinGate VPN has the ability to detect network interfaces as they are enabled and disabled on the WinGate VPN Node machine. Network connections (including dialup profiles) found by WinGate VPN are listed in the Network Connections panel, located at Control Panel > Network Connections in the WinGate Management console. WinGate VPN will automatically classify what type of network the interface connects to (Usage) based on its network settings.
For the purposes of WinGate VPN there are 2 different types of usage for network connections :
If the network interface has a private IP address, then WinGate will consider the interface as being safe. e.g. this adapter connects to the LAN.
If the network interface has a public IP address, then WinGate will see it as being connected to the Internet (an untrusted network).
Unless configured specifically not to, WinGate will always automatically classify the usage of any Internet connection as External.
WinGate VPN can utilize any dialup profiles that it finds on the operating system. The dialup profile needs to be configured in the operating system before WinGate VPN will use this connection to reach the Internet.
Dial up connections are not recommended when the Node machine is configured to host a VPN. This is because these type of connections are assigned a dynamic IP every time they connect to the ISP. As a result, remote VPN Client Nodes would have to change the IP address details of the Master Node server every time that it went off-line/online.
In situations where there is no alternative to using a dialup connection, it is recommended that you use a third party Dynamic DNS address to host type application on the Master Node server, so that it can help keep track of changes to the IP address every time the Master Node server dials the Internet.
External network connections in the WinGate VPN, are interfaces that have been either configured with a public IP address and so have a direct connection and are visible to the Internet. Or the network interface has a Gateway address assigned to it that enables WinGate VPN to reach the Internet (such as an interface that connects to NAT router that has a Internet connection).
External network connections will generally fall into one of three scenarios:
In this scenario WinGate will have a network interface that has a public IP address assigned to it by the ISP (Internet connection). With this connection being connected directly to the Internet, there should be no special set up requirements for this scenario. Since this interface will have a public IP address, it will automatically have its Usage marked as External in the WinGate specific properties of the Internet connection (Found on the Network Connections panel, located at Control Panel > Network Connections in the WinGate Management console).
When all machines are connected to the router that is providing the Internet connection:
Since the WinGate VPN machine is not the default gateway for the network in this scenario, there is some extra routing considerations for VPN Participants.
In this scenario the WinGate VPN machine is the only machine connected to the Internet router. The WinGate VPN will generally have two network interfaces, one that connects to the LAN, and one that connects to the router.
In any situation where the WinGate VPN machine is connected to a NAT router with the Internet connection, then you will need to ensure that the appropriate ports on the firewall of the router have been set to redirect all incoming VPN traffic to the VPN machine (Commonly referred as Port forwarding).
You can use basic Full-Text Searches against the page title and body to find matching articles. Use the following search modifiers to refine your query: