Wingate 5.2.2 FTP proxy accounting issue

[infofarmer]

We're using Wingate 5.2.2 on Windows 2000 Server and I've stumbled upon a serious issue. When users download files via FTP proxy with FlashGet, only a small fraction of session traffic is accounted (about 1-10%). I checked it from two different PC's. When the proxy is disabled and they browse FTP via NAT, everything seems to be fine. When I downloaded some files with Firefox via FTP proxy the traffic was also calculated correctly. So this is some issue with Flashget+Wingate, but it's very serious for those applications, where traffic accounting is vital.

I'll run a series of tests later with different download managers and Wingate 5.2.3. For the time being, I had to disable FTP proxy.

[neil]

Do you have a link to the version of FlashGet you are using so we can download it and try it here?! Also does the accounting behave differently if the connection is 'TR'd' (ie the NAT conneciton pushed through the proxy)?

Regards

Neil

[infofarmer]

Versions 1.40 and 1.50 were tested. Google for flashget, you'll find both in the first results. We used default settings, ad-sponsored versions. Yes, the connections were transparently pushed through proxy, haven't tried it any other way yet.

I guess you would like to wait another couple of days before I run all the tests and post some kind of summary here. First of all I got to upgrade to 5.2.3. It's just not very easy for me because the server is under load most of the time around the clock :-)

Still, guys, it would be by far more reliable, if you implemented a separate customizable tool into wingate, preferably open-source or shared-source, just for calculating traffic. Like Tmeter or Bwmeter or iptables+NetFilter. You know, it's not very easy for a sysop to write sth like that, not to say to implement it (e.g. to disable an account when the limit is passed), but that should not be a problem for you :-) I just have a feeling, that wingate drops some packets by the counter... Or am I paranoid?..

[infofarmer]

Upgraded to 5.2.3 yesterday. Several users complained that all VPN connections lasted for 3-10 minutes and then just disconnected. Tested myself and confirmed. Had to fall back to 5.2.2.