Recommendation for analyzing Wingate log data.

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

Moderator: Qbik Staff

Recommendation for analyzing Wingate log data.

Postby Gavriel Gery » May 15 07 9:29 am

Shalom to all.

I have problems with our ISP. In bad days our ISP disconnects our line tens of times. The best policy should be to leave them and go work with another ISP, but we can't. Wingate has a problem reconnecting. A problematic situation.

My intention is to conduct an automated survey for a while. Next we analyze the results and then we decide. Do we fight with our ISP, take another ISP just for the dry hours of the day, or something else. A simple way to it is to analyze the Wingate server log data.

The logic in it is to intercept requests from client machines that are not properly serviced. In the dry hours requests are pushed into the server and aren't matched by traffic pulled in from the Internet. The server fails to accommodate for those requests not sensing the fact that the line is down. I peeped into the history files namely "HISTORY.DBF" and "HISTORY.CDX". In the "LOGS" directory there are at least 100 log files. It's not a problem to feed them into Excel. The problem is to know what to look for.

Can any one recommend which of the history or log files contain information that represents traffic halts best. What do I have to search for in those files?

Thanks in advance.
Regards
Gavriel Gery.
Gery Engineering(ha)Ltd.
93 Hertzl str. Nahariya 22100,POBox 363,ISRAEL;
TelFax +972(0)49 926517;Mobile +972(0)544 926517;SkyPe gabigery
email gery_eng@geryeng.com, gavrielgery@iib.ws;
Gavriel Gery
 
Posts: 1
Joined: Feb 26 07 3:57 pm

Postby logan » May 15 07 2:07 pm

I believe you may be able to use "traffic" log entries in your situation. A traffic entry indicates the amount of data sent to and received from the client computer and the end server.

Traffic 6572 393 364 6566 1s
Bytes (sent to, received from, sent for, received for) client, time in seconds

Basically, the first 2 numbers represent communication with the client and the second 2 represent communication with the server. If the second 2 numbers are blank, then no traffic was sent/received from the end server for the client. This would indicate some form of connection problem. In some situations this is normal though, so you will still need to judge which entries are related to a broken internet connection and which are simply failing.

Traffic 6572 393 0 0 1s.
logan
Qbik Staff
 
Posts: 671
Joined: Oct 19 06 2:49 pm
Location: Auckland, New Zealand


Return to WinGate

Who is online

Users browsing this forum: No registered users and 5 guests

cron