1 .TH IP\-MONITOR 8 "20 Dec 2011" "iproute2" "Linux"
3 ip-monitor and rtmon \- state monitoring
9 .BR "ip monitor" " [ " all " |"
10 .IR LISTofOBJECTS " ]"
16 utility can monitor the state of devices, addresses
17 and routes continuously. This option has a slightly different format.
20 command is the first in the command line and then the object list follows:
22 .BR "ip monitor" " [ " all " |"
23 .IR LISTofOBJECTS " ]"
26 is the list of object types that we want to monitor.
28 .BR link ", " address " and " route "."
33 opens RTNETLINK, listens on it and dumps state changes in the format
34 described in previous sections.
37 If a file name is given, it does not listen on RTNETLINK,
38 but opens the file containing RTNETLINK messages saved in binary format
39 and dumps them. Such a history file can be generated with the
41 utility. This utility has a command line syntax similar to
45 should be started before the first network configuration command
46 is issued. F.e. if you insert:
49 rtmon file /var/log/rtmon.log
52 in a startup script, you will be able to view the full history
56 Certainly, it is possible to start
59 It prepends the history with the state snapshot dumped at the moment
67 Original Manpage by Michail Litvak <mci@owl.openwall.com>