State monitoring, monitor the state of devices, addresses and routes continuously.
Syntax ip monitor [ all | LISTofOBJECTS ] Key LISTofOBJECTS is the list of object types that we want to monitor. It may contain link, address and route. If no file argument is given, ip opens RTNETLINK, listens on it and dumps state changes in the format described in previous sections.
If a file name is given, it does not listen on RTNETLINK, but opens the file containing RTNETLINK messages saved in binary format and dumps them. Such a history file can be generated with the rtmon utility. This utility has a command line syntax similar to ip monitor. Ideally, rtmon should 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 of starting.
“I can't change the direction of the wind, but I can adjust my sails to always reach my destination” ~ Jimmy Dean
ip - Routing, devices and tunnels.
Equivalent Windows command: ROUTE - Manipulate network routing tables.