22.7 Dial Log
Prev | Chapter 22 Logs | Next

## 22.7 Dial Log

Data about dialing and hanging up the dial-up lines, and about time spent on-line.

The following items (events) can be reported in the Dial log:

1. Manual connection (from the Administration Console — see chapter 5 Network interfaces or directly from the operating system)

   `[15/Mar/2008 15:09:27] Line "Connection" dialing, console 127.0.0.1 - Admin`

   `[15/Mar/2008 15:09:39] Line "Connection" successfully connected`

   The first log item is reported upon initialization of dialing. The log always includes WinRoute name of the dialed line (see chapter 5 Network interfaces). If the line is dialed from the Administration Console, the log provides this additional information

   - where the line was dialed from (`console` — Administration Console,

   - IP address of the client (i.e. IP address of the Administration Console),

   - login name of the user who sent the dial request.

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

2. Line disconnection (manual or automatic, performed after a certain period of idleness)

   `[15/Mar/2008 15:29:18] Line "Connection" hang-up, console 127.0.0.1 - Admin`

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

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

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

3. Disconnection caused by an error (connection is dropped)

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

   The items are the same as in the previous case (the second item — the `disconnected` report).

4. Requested dialing (as a response to a DNS query)

   `[15/Mar/2008 15:51:27] DNS query for "www.microcom.com" (packet UDP 192.168.1.2:4567 -> 195.146.100.100:53) initiated dialing of line "Connection"`

   `[15/Mar/2008 15:51:38] Line "Connection" successfully connected`

   The first log item is recorded upon reception of a DNS request (the DNS forwarder has not found requested DNS record in its cache). The log provides:

   - DNS name from which IP address is being resolved,

   - description of the packet with the corresponding DNS query (protocol, source IP address, source port, destination IP address, destination port),

   - name of the line to be dialed.

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

5. On-demand dialing (response to a packet sent from the local network)

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

   `[15/Mar/2008 15:53:53] Line "Connection" successfully connected`

   The first record is logged when WinRoute finds out that the route of the packet does not exist in the routing table. The log provides:

   - description of the packet (protocol, source IP address, destination port, destination IP address, destination port),

   - name of the line to be dialed.

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

6. Connection error (e.g. error at the modem was detected, dial-up was disconnected, etc.)

   `[15/Mar/2008 15:59:08] DNS query for "www.microsoft.com" (packet UDP 192.168.1.2:4579 -> 195.146.100.100:53) initiated dialing of line "Connection"`

   `[15/Mar/2008 15:59:12] Line "Connection" disconnected`

   The first record represents a DNS record sent from the local network, from that the line is to be dialed (see above).

   The second log item (immediately after the first one) informs that the line has been hung-up. Unlike in case of a regular disconnection, time of connection and volume of transmitted data are not provided (because the line has not been connected).

Prev | Up | Next
22.6 Debug Log | Contents | 22.8 Error Log