This manual page documents briefly the rtmon command.
rtmon listens on netlink socket and monitors routing table
rtmon can be started before the first network configuration
command is issued. For example if you insert:
rtmon file /var/log/rtmon.log
in a startup script, you will be able to view the full history
later. Certainly, it is possible to start rtmon at any time. It
prepends the history with the state snapshot dumped at the moment
rtmon supports the following options:-Version
Print version and exit.
help Show summary of options.
file FILE [ all | LISTofOBJECTS ]
Log output to FILE. LISTofOBJECTS is the list of object
types that we want to monitor. It may contain 'link',
'address', 'route' and 'all'. 'link' specifies the network
device, 'address' the protocol (IP or IPv6) address on a
device, 'route' the routing table entry and 'all' does
what the name says.
-family [ inet | inet6 | link | help ]
Specify protocol family. 'inet' is IPv4, 'inet6' is IPv6,
'link' means that no networking protocol is involved and
'help' prints usage information.
-4 Use IPv4. Shortcut for -family inet.
-6 Use IPv6. Shortcut for -family inet6.
-0 Use a special family identifier meaning that no networking
protocol is involved. Shortcut for -family link.
This page is part of the iproute2 (utilities for controlling
TCP/IP networking and traffic) project. Information about the
project can be found at
If you have a bug report for this manual page, send it to
email@example.com, firstname.lastname@example.org. This page was
obtained from the project's upstream Git repository
2021-08-27. (At that time, the date of the most recent commit
that was found in the repository was 2021-08-18.) If you
discover any rendering problems in this HTML version of the page,
or you believe there is a better or more up-to-date source for
the page, or you have corrections or improvements to the
information in this COLOPHON (which is not part of the original
manual page), send a mail to email@example.com