Go to main content

Administering TCP/IP Networks, IPMP, and IP Tunnels in Oracle® Solaris 11.3

Exit Print View

Updated: March 2019
 
 

Logging Actions of the IPv4 Routing Daemon

If you suspect a malfunction of the IPv4 routing daemon, routed, you can start a log that traces the daemon's activity. The log includes all of the packet transfers when you start the routed daemon.

Create a log file that traces the routing daemon's actions as follows:

# /usr/sbin/in.routed /var/log-file-name

Caution

Caution  -  On a busy network, this command can generate almost continuous output.


The following example shows the beginning of the log that is created when you perform the Logging Actions of the IPv4 Routing Daemon procedure.

-- 2003/11/18 16:47:00.000000 --
Tracing actions started
RCVBUF=61440
Add interface lo0  #1   127.0.0.1      -->127.0.0.1/32
<UP|LOOPBACK|RUNNING|MULTICAST|IPv4> <PASSIVE>
Add interface net0 #2   203.0.113.112    -->203.0.113.0/25
<UP|BROADCAST|RUNNING|MULTICAST|IPv4>
turn on RIP
Add    203.0.113.0        -->203.0.113.112      metric=0  net0  <NET_SYN>
Add    203.0.113.85/25  -->203.0.113.112      metric=0  net0  <IF|NOPROP>