WinGate 7 - NAT feature request.

[Sergiy]

I want ability to call policy when NATed tcp connection stream is terminated or NATed UDP packed passed through WinGate to client.
At the moment i have only WinGate NAT::ClientConnect and see value of variable Session.ClientBytesIn == 0(it is quite logical though), but if i would be able to question this variable at "disconnect" time, i could log entire traffic passed through the NAT properly.

[adrien]

Hi

we could do a NAT TCP disconnect no problem.

As for UDP... it's difficult to do for each packet due to possible extreme load that policy can then place on processing every UDP packet. We could do a generic hash entry destruction one though, which would happen when a TCP connection closed, or when a UDP one timed out (which all UDP "connections" do, since it's connectionless).

Regards

Adrien

[Sergiy]

Having event on generic hash destruction associated with user would be great. However all session and user information should be available in the policy.

[Sergiy]

Could you please provide estimations these features are going to be implemented in future WinGate builds?

[adrien]

Hi Sergiy

We hope to release this with WinGate 8 before the end of July.

Regards

Adrien

[Sergiy]

Is this feature will be in Wingate 7 product line as well?

[adrien]

Hi Sergiy

we don't currently have any plans for another WG7 release. Is there any reason you want it in 7 rather than 8?

If your current license had version protection as at 1 June 2013, you are entitled to use it in WinGate 8, and it's a simple upgrade - just install over the top. Retains all settings except http caching, since that is entirely new system.

Regards

Adrien

[Sergiy]

Updated to Wingate 8. Now is testing period. Still, there is remain one huge problem for us: WinGate NAT Usage log file doesn’t have date on traffic passed through the NAT. But for us is main requirement to “have” NAT log with available values: “Date”, “Time”, “Username”, “Method”, “Bytes received”, “Bytes sent”, “Protocols”, etc. (we need almost full analog option log file’s as “WWW Proxy Server” (in Wingate8)). Since we provide to users-clients limited traffic – online update in real-time (with delay few minutes) on remaining internet traffic (as on personal page on portal). Using analytic software. And for all options it’s “critical” have detailed WinGate NAT log files (example – was used in Wingate 6). WinGate NAT logs was used as source for all of this. Since our license Professional - cant use MySQL datebase.

Is it possible add (make) in next build Wingate NAT usage log file with requested Fields?

[adrien]

Hi Sergiy

This is quite problematic, and the main reason is connection duration.

A NAT connection can stay open for hours, and transfer many GB etc. Currently we log when the connection is created. At this stage we don't have any traffic information.

If we held back logging until the session was complete, we could log data, but that could be a very long time later.

TMG/ISA adopts an approach where it makes several log entries for the connection - once when it starts, potential interim traffic log entries, and then a final one.

I think we looked into doing something similar. Not sure why we didn't adopt it though.

In the NAT diagnostic logs it logs session termination with traffic. This is what you refer to with WinGate 6?

We changed log level for traffic and request information to info level, so you no longer need to log diagnostic log at debug level to get this information.

Regards

Adrien

[Sergiy]

Is there no change to content NAT logs? Ergo impossible after all have NAT log file with line’s - bite received and sended, as in Wingate 6?

[Sergiy]

We using Wingate 8.*.** latest version is there any known for you software that can analyze NAT log. (bytes received, sent, users, etc). Except Proxy Inspector - because even latest version can't analyzy NAT logs.

[MattP]

Hi,

Have you tried Sawmill Log Analyser? That might be worth trying.

Matt

[Sergiy]

When i tryed Sawmill Log Analyser.... On first step creating report - error (bug) related to date format (of course this bug was sent to sawmill suport).
So my depression continue :'(