1 .TH IP\-MONITOR 8 "13 Dec 2012" "iproute2" "Linux"
3 ip-monitor, rtmon \- state monitoring
9 .BR "ip monitor" " [ " all " |"
10 .IR OBJECT-LIST " ] ["
24 .BR "\-t" , " \-timestamp"
25 Prints timestamp before the event message on the separated line in format:
26 Timestamp: <Day> <Month> <DD> <hh:mm:ss> <YYYY> <usecs> usec
30 .BR "\-ts" , " \-tshort"
31 Prints short timestamp before the event message on the same line in format:
32 [<YYYY>-<MM>-<DD>T<hh:mm:ss>.<ms>] <EVENT>
37 utility can monitor the state of devices, addresses
38 and routes continuously. This option has a slightly different format.
41 command is the first in the command line and then the object list follows:
43 .BR "ip monitor" " [ " all " |"
44 .IR OBJECT-LIST " ] ["
55 is the list of object types that we want to monitor.
57 .BR link ", " address ", " route ", " mroute ", " prefix ", "
58 .BR neigh ", " netconf ", " rule " and " nsid "."
63 opens RTNETLINK, listens on it and dumps state changes in the format
64 described in previous sections.
69 option is set, a prefix is displayed before each message to
70 show the family of the message. For example:
73 [NEIGH]10.16.0.112 dev eth0 lladdr 00:04:23:df:2f:d0 REACHABLE
74 [LINK]3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default
75 link/ether 52:54:00:12:34:57 brd ff:ff:ff:ff:ff:ff
82 option is set, the program listens to all network namespaces that have a
83 nsid assigned into the network namespace were the program is running.
84 A prefix is displayed to show the network namespace where the message
88 [nsid 0]10.16.0.112 dev eth0 lladdr 00:04:23:df:2f:d0 REACHABLE
95 option is given, the program does not listen on RTNETLINK,
96 but opens the given file, and dumps its contents. The file
97 should contain RTNETLINK messages saved in binary format.
98 Such a file can be generated with the
100 utility. This utility has a command line syntax similar to
104 should be started before the first network configuration command
105 is issued. F.e. if you insert:
108 rtmon file /var/log/rtmon.log
111 in a startup script, you will be able to view the full history
115 Nevertheless, it is possible to start
118 It prepends the history with the state snapshot dumped at the moment
124 option is given, the program prints only events related to this device.
131 Original Manpage by Michail Litvak <mci@owl.openwall.com>
133 Manpage revised by Nicolas Dichtel <nicolas.dichtel@6wind.com>