WinGate provides optional TCP Mapping services that you can use to redirect client connections received on a particular service port and network interface, to a preset destination.
By simply specifying the IP address of the WinGate server and the service port used by the mapping service in their connection, WinGate users will be redirected to the server destination specified in the mappings properties.
Each TCP mapping service can be made to redirect all user connections it receives to one default server, or it can redirect each individual connection to a different mapping based on the user that connects or the location they make the connection from.
|
Service setting |
Default value |
|---|---|
Service port |
Each mapping is set to 0 by default. When you install a mapping service you are REQUIRED to select the service port that users can connect to the mapping service on.
|
Bindings |
TCP mapping services will automatically bind to any network interfaces that have their usage marked as Internal by WinGate. This allows LAN WinGate clients to simply specify the local IP address of the WinGate server (and appropriate service port) in order to connect to the mapping. |
Registered events |
ClientConnect, ClientDisconnect |
To use a mapping service WinGate clients have to specify in their connection:
The service port that has been set for the mapping service.
It is possible to have a TCP mapping service intercept ALL connections made to WinGate on the network interface and service port it is using, rather then clients having to manually enter the IP address of the WinGate server in their connection as mentioned above.
Each TCP mapping has a Intercepting proxy configuration where you can set all the ports that the mapping service will intercept, regardless of the type of connection or specified destination clients connect to WinGate with. This means that when a connection is made to WinGate on a service port set in a TCP mapping, the connection will be directed to the destination set in that particular mapping. (See the Advanced TCP Mapping features section below).
When you install a TCP mapping service, you need to specify a destination server and port that the mapping will connect to. This can be set in the Default mapping section on the General tab of the TCP Mapping properties.
Within each TCP Mapping service there is the Mappings tab where you can specify individual mapped links depending on the user who has connected to the mapping, or the location where they connect from. This means that the final mapped link destination that the connection will be sent to, can be determined by user, or by their location.
TCP Mapping services allow WinGate to use several advanced features in their configuration to help with the control and security of the mapping.
You can specify whether TCP Mapping should use SSL/TLS when it connects to the destination server specified in the mapping. Obviously the destination server will be required to support SSL connections. This can also include using SSL mappings to connect to other WinGate servers that have service bindings configured to accept SSL connections.
SSL connections can be enabled in two ways in a TCP Mapping configuration:
With TCP mapping services you can utilize the Intercepting proxy found on the Intercepting tab, to intercept any connection made to WinGate on a specified port (and network interface bound to the TCP Mapping) and force it through the mapping service. You can set any number of ports in the Intercepting proxy for each mapping service, so long as they are not currently in use by any other network service.
This means that rather then specifying the IP address and service port to access the mapping service, all user connections that are made to WinGate using the network interface, and service port listed in the Intercepting proxy configuration, will be intercepted and forced through the mapping service automatically.
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:
