subnet ether.home . 192.168.2.0 ff:ff:ff:00 ether
10.50 trace
10.50.1Syntax
trace [<option>]
10.50.2Description
Turns on an IP tracing option, or lists the available options. Note that tracing messages are written to background output, so with the standard console one must use the event commands to see them.
An option can be:
•One of various keywords. The details of just what tracing messages are enabled by each keyword are not documented here; examine the source code for more information.
•An association number (see the command files on page 170). For a TCP association this turns on detailed tracing of events (including all packet transmission and reception) on that association; for a UDP association it has no effect. The files command shows (by appending TRACE) whether each association has tracing enabled.
•An interface name (see the command device on page 162). This turns on tracing of every packet sent or received through the interface (one line per packet). The device command shows (by appending TRACE) whether each interface has tracing enabled.
•ip. This turns on tracing for all interfaces.
•all. This turns on all tracing.
Note – trace does not display which associations and interfaces are being traced; one must use the files and device commands for that.
The trace command is hidden, not shown by ip help. It is useful mainly for debugging and troubleshooting.
10.50.3Example
mymachine> ip trace
ip: try trace - <assoc no> <i/f name> all ip errors resolve ipatm atmarp iploop arp ipether icmp udp tcp tcphdr tcpstate routes riptx riprx names ip: currently tracing nothing
mymachine> ip trace tcp
ip: currently tracing tcp
