Manual Page Search Parameters
TRPT(8) MidnightBSD System Manager's Manual TRPT(8)

trpt — transliterate protocol trace

trpt [-a] [-f] [-j] [-p hex-address] [-s] [system [core]]

The trpt utility interrogates the buffer of TCP trace records created when a socket is marked for “debugging” (see setsockopt(2)), and prints a readable description of these records. When no options are supplied, trpt prints all the trace records found in the system grouped according to TCP connection protocol control block (PCB).

The following options may be used to alter this behavior:

In addition to the normal output, print the values of the source and destination addresses for each packet recorded.
Follow the trace as it occurs, waiting a short time for additional records each time the end of the log is reached.
Just give a list of the protocol control block addresses for which there are trace records.
Show only trace records associated with the protocol control block at the given address hex-address.
In addition to the normal output, print a detailed description of the packet sequencing information.

The recommended use of trpt is as follows. Isolate the problem and enable debugging on the socket(s) involved in the connection. Find the address of the protocol control blocks associated with the sockets using the -A option to netstat(1). Then run trpt with the -p option, supplying the associated protocol control block addresses. The -f option can be used to follow the trace log once the trace is located. If there are many sockets using the debugging option, the -j option may be useful in checking to see if any trace records are present for the socket in question.

If debugging is being performed on a system or core file other than the default, the last two arguments may be used to supplant the defaults.

/boot/kernel/kernel
 
/dev/kmem
 

no namelist
When the system image does not contain the proper symbols to find the trace buffer; others which should be self explanatory.

netstat(1), setsockopt(2)

The trpt utility appeared in 4.2BSD.

Should also print the data for each input or output, but this is not saved in the trace record.

The output format is inscrutable and should be described here.

February 15, 2018 midnightbsd-3.1