diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-05-04 14:18:53 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-05-04 14:18:53 +0000 |
commit | a0e0018c9a7ef5ce7f6d2c3ae16aecbbd16a8f67 (patch) | |
tree | 8feaf1a1932871b139b3b30be4c09c66489918be /man/man8/ip-monitor.8 | |
parent | Initial commit. (diff) | |
download | iproute2-a0e0018c9a7ef5ce7f6d2c3ae16aecbbd16a8f67.tar.xz iproute2-a0e0018c9a7ef5ce7f6d2c3ae16aecbbd16a8f67.zip |
Adding upstream version 6.1.0.upstream/6.1.0upstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to '')
-rw-r--r-- | man/man8/ip-monitor.8 | 133 |
1 files changed, 133 insertions, 0 deletions
diff --git a/man/man8/ip-monitor.8 b/man/man8/ip-monitor.8 new file mode 100644 index 0000000..ec033c6 --- /dev/null +++ b/man/man8/ip-monitor.8 @@ -0,0 +1,133 @@ +.TH IP\-MONITOR 8 "13 Dec 2012" "iproute2" "Linux" +.SH "NAME" +ip-monitor, rtmon \- state monitoring +.SH "SYNOPSIS" +.sp +.ad l +.in +8 +.ti -8 +.BR "ip monitor" " [ " all " |" +.IR OBJECT-LIST " ] [" +.BI file " FILENAME " +] [ +.BI label +] [ +.BI all-nsid +] [ +.BI dev " DEVICE " +] +.sp + +.SH OPTIONS + +.TP +.BR "\-t" , " \-timestamp" +Prints timestamp before the event message on the separated line in format: + Timestamp: <Day> <Month> <DD> <hh:mm:ss> <YYYY> <usecs> usec + <EVENT> + +.TP +.BR "\-ts" , " \-tshort" +Prints short timestamp before the event message on the same line in format: + [<YYYY>-<MM>-<DD>T<hh:mm:ss>.<ms>] <EVENT> + +.SH DESCRIPTION +The +.B ip +utility can monitor the state of devices, addresses +and routes continuously. This option has a slightly different format. +Namely, the +.B monitor +command is the first in the command line and then the object list follows: + +.BR "ip monitor" " [ " all " |" +.IR OBJECT-LIST " ] [" +.BI file " FILENAME " +] [ +.BI label +] [ +.BI all-nsid +] [ +.BI dev " DEVICE " +] + +.I OBJECT-LIST +is the list of object types that we want to monitor. +It may contain +.BR link ", " address ", " route ", " mroute ", " prefix ", " +.BR neigh ", " netconf ", " rule ", " stats ", " nsid " and " nexthop "." +If no +.B file +argument is given, +.B ip +opens RTNETLINK, listens on it and dumps state changes in the format +described in previous sections. + +.P +If the +.BI label +option is set, a prefix is displayed before each message to +show the family of the message. For example: +.sp +.in +2 +[NEIGH]10.16.0.112 dev eth0 lladdr 00:04:23:df:2f:d0 REACHABLE +[LINK]3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default + link/ether 52:54:00:12:34:57 brd ff:ff:ff:ff:ff:ff +.in -2 +.sp + +.P +If the +.BI all-nsid +option is set, the program listens to all network namespaces that have a +nsid assigned into the network namespace were the program is running. +A prefix is displayed to show the network namespace where the message +originates. Example: +.sp +.in +2 +[nsid 0]10.16.0.112 dev eth0 lladdr 00:04:23:df:2f:d0 REACHABLE +.in -2 +.sp + +.P +If the +.BI file +option is given, the program does not listen on RTNETLINK, +but opens the given file, and dumps its contents. The file +should contain RTNETLINK messages saved in binary format. +Such a file can be generated with the +.B rtmon +utility. This utility has a command line syntax similar to +.BR "ip monitor" . +Ideally, +.B rtmon +should be started before the first network configuration command +is issued. F.e. if you insert: +.sp +.in +8 +rtmon file /var/log/rtmon.log +.in -8 +.sp +in a startup script, you will be able to view the full history +later. + +.P +Nevertheless, it is possible to start +.B rtmon +at any time. +It prepends the history with the state snapshot dumped at the moment +of starting. + +.P +If the +.BI dev +option is given, the program prints only events related to this device. + +.SH SEE ALSO +.br +.BR ip (8) + +.SH AUTHOR +Original Manpage by Michail Litvak <mci@owl.openwall.com> +.br +Manpage revised by Nicolas Dichtel <nicolas.dichtel@6wind.com> |