Traffic information is displayed on a per-interface basis, thus allowing you to see how much traffic is coming in to the WinGate machine from your LAN, as well as how much is going out to the internet, and with what level of performance.
Back to top
If you see activity you do not like, you can terminate it. There are also simple shortcuts to blocking similar access in the future, for example Blacklisting the IP address
Back to top
Prior to WinGate 7, these 2 functions were performed by a single logging system, which resulted in compromises since diagnostic data was interspersed with data used for reporting on usage.
From WinGate 7 onwards, these 2 functions have been separated out so that each one can be better fulfilled. For diagnostic logging, the previous log format was extended but largely retained. For usage logging, the W3C format was adopted, as it is in widespread use and supported by a large number of log analysers.
WinGate DHCP is different from other DHCP servers, in that it can even figure out what IP addresses to allocate without the administrator having to predefine pools of addresses (scopes). It can also figure out how to set the clients' gateway and several other parameters too, which means that not even the administrator needs to be a TCP/IP expert to operate the WinGate DHCP server.
Full manual override of all automatic settings is also available in order to allow administrators to cater for their specific requirements.
Back to top
You can choose the user account that the cmd.exe process is executed in, and the input and output is transferred over the encrypted GateKeeper control channel, providing security.
Back to top
Processing of the triggered event is possible with any installed event handler, such as Flow-chart policy, Email, run application, etc. A large number of internal WinGate functions may be triggered in this way including: