next up previous contents
Next: Statistics: Up: ip route show Previous: Examples:   Contents

Output format:

The output of this command consists of per route records separated by line feeds. However, some records may consist of more than one line: particularly, this is the case when the route is cloned or you requested additional statistics. If the -o option was given, then line feeds separating lines inside records are replaced with the backslash sign.

The output has the same syntax as arguments given to ip route add, so that it can be understood easily. F.e.

kuznet@amber:~ $ ip ro ls 193.233.7/24
193.233.7.0/24 dev eth0  proto gated/conn  scope link \
    src 193.233.7.65 realms inr.ac 
kuznet@amber:~ $

If you list cloned entries, the output contains other attributes which are evaluated during route calculation and updated during route lifetime. An example of the output is:

kuznet@amber:~ $ ip ro ls 193.233.7.82 tab cache
193.233.7.82 from 193.233.7.82 dev eth0  src 193.233.7.65 \
  realms inr.ac/inr.ac 
    cache <src-direct,redirect>  mtu 1500 rtt 300 iif eth0
193.233.7.82 dev eth0  src 193.233.7.65 realms inr.ac 
    cache  mtu 1500 rtt 300
kuznet@amber:~ $
1cm NB. The route looks a bit strange, doesn't it? Did you notice that it is a path from 193.233.7.82 back to 193.233.82? Well, you will see in the section on ip route get (p.[*]) how it appeared.

The second line, starting with the word cache, shows additional attributes which normal routes do not possess. Cached flags are summarized in angle brackets:

Then some optional attributes follow:


next up previous contents
Next: Statistics: Up: ip route show Previous: Examples:   Contents