Overview

Logs keep information records of selected events occurred in or detected by Kerio Control. Each log is displayed in a window in the Logs section. This article serves as a reference for the content found in Kerio Control's Dial logs.

Environment

Kerio Control's administration console

Reference Information

The Dial log displays data about dialing and hanging up the dial-up lines, and about time spent online.

Sample logs and message formats:

• Manual connection (from Kerio Control administration or Kerio Control client interface):
  
  

  Log item is reported upon initialization of dialing. The log provides information about the line name, IP address, and username.

  [31/Jul/2013 11:41:48] Line "Connection" dialing manually from IP 10.10.10.60, user admin.

  The event is logged upon a successful connection (e.g. when the line is dialed, upon authentication on a remote server, etc.).

  [31/Jul/2013 11:42:04] Line "Connection" connected

  
  
  
• Automatic connections:
  
  

  Automatic dialing due to time range is logged as:

  [10/Jul/2013 14:19:22] Line "Kerio PPPoE" dialing due to configured connect time.

  Automatic dialing due to configured connectivity options (e.g. Link Load Balancing) is logged as:

  [10/Jul/2013 14:34:44] Line "Kerio PPPoE" dialing, required by internet connectivity.

  
  
  
• Line disconnection (manual or automatic, performed after a certain period of idleness:
  
  

  Log item is recorded upon reception of a hang-up request. The log provides information about the interface name, client type, IP address, and username.

  15/Mar/2013 15:29:18] Line "Connection" hanging up, manually from IP 10.10.10.60, user Admin.

  The event is logged upon a successful hang-up. The log provides information about interface name, time of connection (connection time), the volume of incoming and outgoing data in bytes (bytes received and bytes transmitted).

  [15/Mar/2013 15:29:20] Line "Connection" disconnected, connection time 00:15:53, 1142391 bytes received, 250404 bytes transmitted.

  
  
  
• Disconnection caused by an error (connection is dropped):
  
  

  The items are similar to the Line disconnection report, the second example.

  [15/Mar/2013 15:42:51] Line "Connection" dropped, connection time 00:17:07, 1519 bytes received, 2504 bytes transmitted.

  
  
  
• Dialing the link to respond to a packet from the local network:
  
  

  The log provides a description of the packet (protocol, source IP address, destination port, destination IP address, destination port) and the name of the line to be dialed.

  [15/Mar/2013 15:53:42] Packet TCP 192.168.1.3:8580 > 212.20.100.40:80 initiated dialing of line "Connection".

  Another event is logged upon a successful connection (i.e. when the line is dialed, upon authentication on a remote server, etc.).

  [15/Mar/2013 15:53:53] Line "Connection" successfully connected.