LOG IN |  Register | 0 item(s) in your shopping cart, USD
Download and try the latest WinGate 9 free for 30 days.

Features

Multiple simultaneous internet connections

WinGate can bypass system routing when it makes outbound connections.  This allows you to define which available internet gateways will be used on a per-service basis, and the way that multiple connections can be used (e.g. failover, or round-robin for bandwidth aggregation).  WinGate monitors gateway availability (if enabled), and automatically applies the policies you define to the list of available gateways to select which gateway to use on a connection-by-connection basis. Gateway usage
You can use multiple Internet connections at the same time with WinGate, thereby increasing your system throughput. On a per-proxy basis in WinGate, you can specify multiple methods of using these multiple connections as well.

for instance you could:

  • Specify that the WWW Proxy uses all your available internet connections
  • Specify that another proxy uses only one of the connections, but if that becomes unavailable, to fail over to the next one
WinGate monitors connections for availability, including remote gateways, so even if your Internet connections go through another router or a device such as a DSL/NAT device, you can still keep track of it.

WinGate's gateway selection features also allows you to specify on a per service basis which gateway will be used, so if you had a combination of multiple DSL/NAT devices, network gateways, modems, etc, you could still specify which connections go through which gateway, even if they are on the same physical ethernet segment.
Back to top

Bandwidth management / throttling

WinGate's bandwidth control allows you to define restrictions that will be applied to specified types of traffic.  This includes restrictions about absolute bandwidth use, or percentage of available (unused and non-reserved) bandwidth used. Bandwidth Control: Restrictions
WinGate's bandwidth control allows a selection of scheduling mechanisms depending on the user requirements.  The priority levels are used to allow some lower priority traffic to still be sent even under high loading. Bandwidth Control: Scheduling
The bandwidth control rules are used to determine the type of traffic that has restrictions applied to it.  This allows you to specify source and destination IPs and ports, and protocol type to apply to a specific restriction.  For example by setting the destination port to 80, you would be creating a rule which matched HTTP.  If you wanted to only restrict certain users, you could enter their IPs.  So in this way control is available on a per-user, per-service, per time-of-day basis. Bandwidth Control: Rules
WinGate allows you to control the way your available bandwidth is able to be used. Certain application such as streaming media players, internet radios, and others can soak up a lot of your available bandwidth, making core services such as email or web browsing suffer a performance degradation. Furthermore, restricting bandwidth available to certain applications is an effective method of discouraging people from using certain applications (such as file-sharing or peer to peer programs) without having to completely ban them (which people can often circumvent anyway).

With WinGate's bandwidth control functions, you can control bandwidth on a number of criteria:

  • Per client IP address, or range thereof
  • per source or destination port
  • Per time of day (so you can apply different restrictions at different times)
Additionally, you can specify restrictions in terms of absolute bandwidth, or as a proportion of available bandwidth.

The final control you have is scheduling priority. You can make certain services respond more quickly than others by giving a higher priority to the forwarding of packets related to that service.
Back to top

HTTP caching

WinGate's HTTP cache is a scalable and highly flexible HTTP/1.1 compliant cache.  You may create multiple cache volumes (Enterprise license required), which may reside on local or networked disks.  The Cache control policy item allows policy control over which requests may be stored or looked up from cache. HTTP cache rules allow you to control the cache lifetime of resources based on Content-Type and/or the originating site. HTTP cache panel
The WWW Proxy in WinGate creates the opportunity for networks to gain greater efficiency and performance of web browsing.

In general the term caching relates to the act of storing the results of previous operations in the hope that future operations will be able to be satisfied by looking up the stored result, rather than having to fetch the result again.

Especially on large networks, where many users look at the same web pages, reductions in Internet traffic and improvements in speed can result by storing web pages returned as a result of one user's browsing, and returning that stored copy when another user requests the same page.

WinGate has sophisticated rules which allow the system administrator to specify what sorts of requests will be cached, and how the cache will be maintained (since you can't let a cache grow forever or you will run out of disk space).
Back to top

DNS caching

WinGate's DNS client was written to provide advanced resolution capability independently of the OS DNS client.  This also includes a DNS cache.  DNS caching can greatly improve the response time for DNS lookups. DNS client
WinGate includes a custom DNS resolver, which is used by WinGate services to resolve DNS queries. This DNS resolver was written so that WinGate could gain access to all the information returned by DNS servers to DNS requests. This information contains data relating to how long DNS records may be stored before they become stale. This allows WinGate to provide an effective and correct DNS cache.

DNS caching can greatly speed up the user experience of things such as web browsing. By storing (caching) the results of previous DNS lookups, keeping track of the freshness of the information, and returning cached information to clients on subsequent requests, DNS traffic can also be greatly reduced.
Back to top