Wingate 8: Request counter ability and some problem

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

Wingate 8: Request counter ability and some problem

Postby Sergiy » Sep 11 13 1:24 am

Hi I have another features request. And the two main problem for us.

1) To limit user online traffic (as NAT, Proxy, etc.) we using “counter” with LUA script (example - for Wingate NAT when clentdisconnect run LUA script). There need for ability using from the script = option witch is have in already created counter – “store counter value between restarts”. Can you add please this in next bild?

2) There was problem with memory leak – at moment there only 3 active user (Wingate go on trial run). And MySQL was still not installed when it happened first time. All database, cache volume default = 1GB and at leak time was around 998-999MB , timeline was default (now we using MySQL database for timeline). There is narrowed problem… when cache base full – Wingate start constant devour operative memory to max – even after we did purge cache – Wingate doesn’t free memory. Need restart engine. I see this as big loop bug. Please solve this problem. Thanks/

3) And there some very persistent constant crush of management panel, even without change anything (like rules, police any option, etc.) only view (open), and after closing management panel by “x” (close) there is crush.

I send all crush dump to email “support@wingate.com“

And our Configuration:
Wingate 8.0.4608 run on virtual Windows 2008 R2 Standart SP1. (With 2 network adapter)
Memory = 4Gb
Processor = Intel Xeon E5620 @ 2.40 GHz 2.40 GHz
Sergiy
 
Posts: 17
Joined: Apr 24 13 6:53 pm

Re: Wingate 8: Request counter ability and some problem

Postby adrien » Sep 11 13 11:30 am

Hi Sergiy

thanks for reporting that, and for sending the crash dumps. I'll look at those today.

thanks also for those suggestions. We've had that issue about storing data on our radar for a while as well.

we are also chasing a memory leak. I think it may have something to do with the new cache we added for runtime objects in our script system (schema script rather than Lua or jScript, which is used in a lot of places, anywhere there are replaceable parameters - e.g. {{ ... }} or in expression evaluator).

Regards

Adrien
adrien
Qbik Staff
 
Posts: 5448
Joined: Sep 03 03 2:54 pm
Location: Auckland


Return to WinGate

Who is online

Users browsing this forum: No registered users and 9 guests