]> git.proxmox.com Git - mirror_iproute2.git/blame - man/man8/ip-monitor.8
Split up ip man page
[mirror_iproute2.git] / man / man8 / ip-monitor.8
CommitLineData
2a9721f1
SH
1.TH IP\-MONITOR 8 "20 Dec 2011" "iproute2" "Linux"
2.SH "NAME"
3ip monitor and rtmon \- state monitoring
4.SH "SYNOPSIS"
5.sp
6.ad l
7.in +8
8.ti -8
9.BR "ip monitor" " [ " all " |"
10.IR LISTofOBJECTS " ]"
11.sp
12
13.SH DESCRIPTION
14The
15.B ip
16utility can monitor the state of devices, addresses
17and routes continuously. This option has a slightly different format.
18Namely, the
19.B monitor
20command is the first in the command line and then the object list follows:
21
22.BR "ip monitor" " [ " all " |"
23.IR LISTofOBJECTS " ]"
24
25.I OBJECT-LIST
26is the list of object types that we want to monitor.
27It may contain
28.BR link ", " address " and " route "."
29If no
30.B file
31argument is given,
32.B ip
33opens RTNETLINK, listens on it and dumps state changes in the format
34described in previous sections.
35
36.P
37If a file name is given, it does not listen on RTNETLINK,
38but opens the file containing RTNETLINK messages saved in binary format
39and dumps them. Such a history file can be generated with the
40.B rtmon
41utility. This utility has a command line syntax similar to
42.BR "ip monitor" .
43Ideally,
44.B rtmon
45should be started before the first network configuration command
46is issued. F.e. if you insert:
47.sp
48.in +8
49rtmon file /var/log/rtmon.log
50.in -8
51.sp
52in a startup script, you will be able to view the full history
53later.
54
55.P
56Certainly, it is possible to start
57.B rtmon
58at any time.
59It prepends the history with the state snapshot dumped at the moment
60of starting.
61
62.SH SEE ALSO
63.br
64.BR ip (8)
65
66.SH AUTHOR
67Original Manpage by Michail Litvak <mci@owl.openwall.com>