Network Connections

WinGate has been designed as a comprehensive network management application, so its ability to control network interfaces plays a crucial role in WinGate functioning correctly. When using WinGate, the term network interface is used to refer to any network connections that exist in the operating system of the WinGate server.

These can be:

• Hardware based network interfaces in the Operating System such as Ethernet cards, wireless adapters, ISDN, T1 etc.
• Software based network connections that have been configured in Windows such as dialup profiles, Microsoft VPN connections etc.

WinGate will also define what type of physical network connection it is :

1. LAN or High-Speed Internet connections

   These are network interfaces that are connected to a TCP/IP network on full time basis. This includes any network connections, and network interface cards, that are configured with an IP address or obtain one automatically from a DHCP server.

2. Dial on demand

   These types of interfaces only connect to a network when requested. These are generally the software connections (such as dialup profiles and MS VPN connections) in Windows, but also include dialup modems and dialup hardware (such as some DSL cards and certain hi-speed modems).

   WinGate has a Dialer Settings configuration to help manage using dialup connections in WinGate.

Network interface classifications

WinGate has the ability to automatically discover any available network connections on the machine where it is installed. WinGate will constantly monitor the operating system for new interfaces, and changes to existing connections.

When it discovers an available network interface, WinGate will automatically try to determine what type of network the interface is connected to based on the IP address details that have been set on the interface. This allows WinGate to classify the usage of the interface for the purpose of handling client Internet requests.

There are three different types of network interface usage that WinGate automatically try to set:

1. Internal (protected network)

   If the network interface has a private class IP address, then WinGate will consider the interface as being safe. e.g. this adapter connects to the LAN. This includes the autonet range of IP addresses (169.254.*.*).

2. External (untrusted network)

   If the network interface has a public IP address then WinGate will deem it to be connected to the Internet (an untrusted network).

   Note

   If an interface has no IP details configured at all then the interface will be marked as External since the type of network address is undefined. This includes all Dial on demand type connections (Dialup profiles etc.).

3. External (secure network)

   This classification is for interfaces that are part of a DMZ (Demilitarized Zone).

   License restriction:The External (secure network - DMZ) usage classification is only available with a  WinGate Professional or WinGate Enterprise license.

Manual classifications

When an interface becomes available and is classified by WinGate, it will be listed on the Network Connections panel, located in the Control Panel of the WinGate Management console. You can set the usage of each network interface manually in the WinGate properties for the appropriate network interface, but be aware that the usage classification of the network interface is important to way that WinGate handles all traffic. Be careful of the usage type you assign to a network interface.

Read more about the Network Connections configuration in WinGate

Classification usage

WinGate uses these classifications for wide range of purposes through out its operation. The most common are:

1. Connection types

   To help the ENS firewall determine what type of connection is being received on a WinGate network interface. This enables it to allow, deny, or redirect the traffic as required.

2. Dynamic service bindings

   WinGate network services use network interfaces to listen for and respond to requests from clients. WinGate will automatically bind adapters marked as Internal to most network services, so they can begin listening and responding automatically to client requests from the LAN without further configuration.

Note