Technical article 109661

What do the fields in the Morning Star PPP pppd.log file signify?

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4

Written · Last revised

Problem

I am having trouble reading the pppd.log file for SCO PPP from Morning Star. What do the various fields represent?

Solution

Generally, the format of the log is as follows:

Type code (type of log entry) Timestamp (seconds from epoch time) Protocol (TCP, UDP, ICMP) Local IP and port Direction of packet flow Remote IP and port Packet size (bytes) TCP flags (SYN, ACK, FIN, etc.) Firewall (filter) action Tag (information about the packet, compression, etc.)

Some log entries (such as when the modem dials and the chat script is executed; and LCP, IPCP, and CCP negotiation when the link is first being brought up) are logged in clear text and usually need no explanation.

The examples below show three common log entries (from debug
level 7 or higher).  (Note that the Timestamp field has been
converted using the "readlog" script found in ta109543, "Script
to convert Morning Star PPP's /usr/adm/pppd.log timestamps from
epoch time.").

Example #1, ping remote PPP IP address to bringup the link:

5000:(08:24:18 09/15/98 PDT)::8/0/icmp 206.231.9.126 -> 127.0.0.5 84 dial failed (8)

In this entry, the following is seen:

1. The code 5000, indicating normal TCP/IP traffic. 2. Time and datestamp. 3. The packet is an ICMP message with codes 8 and 0. All the ICMP messages are outlined in the file /usr/include/sys/netinet/ip_icmp.h (if you have the Development System installed), as well as RFCs 792, 1122, and 1812. In this case, the results are 8 (source host isolated) and 0 (destination network unreachable) which indicates that the ping failed. 4. The local machine's PPP IP address is next, showing 206.231.9.126 as the IP in use. 5. The packet is outgoing, as indicated by the arrow pointing to the destination IP. 6. The destination IP of 127.0.0.5. With Morning Star PPP, a remote address on the 127.x.x.x network indicates that the link is using "dynamic" IP addressing. In other words, I expect the remote server to assign a valid IP address for the destination. 7. The field "84" in this case indicates the size in bytes. 8. Finally, the "dial failed (8)" keywords indicate there was a problem bringing up the link. In this case, a closer examination of the log might reveal a problem with the modem, the PPP login, PPP parameter negotiation, or some other fatal negotiation error.

Example #2, receipt of UDP routing update:

5000:(08:24:18 09/15/98 PDT)::udp 132.147.170.41/route <- 132.147.228.19/route 532 !keepup (8)

In this entry, the following is seen:

1. The code 5000, indicating normal TCP/IP traffic. 2. Time and datestamp. 3. The packet is a UDP datagram. 4. Our local address is 132.147.170.41 and the port is "route". In checking the file /etc/services, I can see that the keyword "route" actually refers to the UDP port number 520. If Morning Star PPP can convert the number into a name using the getservbyport() call, it will do so in the logfile for readability. 5. The packet is incoming, as indicated by the left-facing arrow. 6. The remote address is 132.147.228.19, and it is also using the "route" port number of UDP 520. In this case, the source and destination ports are the same, but that will often not be the case. 7. The size of this routing update is 532 bytes. 8. The firewall (filtering) options configured in /usr/lib/mstppp/Filter know that this packet should not reset the keepup timer. That is, this particular type of traffic is not enough to maintain the connection to the remote server.

Example #3, FTP "get" from remote server:

5000:(09:18:18 09/15/98 PDT)::tcp 132.147.171.53/1050 <- 132.147.106.20/ftp-data 1500 (u) (8)

In this entry, the following is seen:

1. The code 5000, indicating normal TCP/IP traffic. 2. Time and datestamp. 3. The packet is a TCP message. 4. The local IP address is 132.147.171.53 and the port is 1050. 5. The packet is incoming, as indicated by the left-facing arrow. 6. The remote server is 132.147.106.20 and it is using the "ftp-data" port, so I know this is an FTP data transfer. Looking at /etc/services again, I can see that the FTP data port is 21, and the administrative port is 20. 7. The size of the packet is 1500, which is the maximum size for an Ethernet frame. Note that the actual HDLC PPP frames can be larger than this. 8. Finally, there is a keyword "(u)" which indicates that the frame headers were not compressed using VJ header compressed. If the headers were compressed, you would see "(c)" instead.

See also

Manual pages for ppp.Filter(MST_PPP), pppd(MST_PPP).  Also, see
the following RFCs:  RFC 1661, RFC 1549, RFC 1332, RFC 1333,
RFC 1334, RFC 1172, RFC 1144, and RFC 1055.

From the Xinuos technical article database, record 109661. Reproduced with permission. The original is at www.sco.com/ta/109661, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.