@@ -246,10 +246,16 @@
.I policy routing
-.SS ip route add - add new route
-.SS ip route change - change route
-.SS ip route replace - change or add new one
+ip route add
+add new route
+ip route change
+ip route replace
+change or add new one
.BI to " TYPE PREFIX " (default)
the destination prefix of the route. If
@@ -502,9 +508,12 @@
pretend that the nexthop is directly attached to this link,
even if it does not match any interface prefix.
-.SS ip route delete - delete route
+ip route delete
.B ip route del
has the same arguments as
.BR "ip route add" ,
@@ -518,8 +527,12 @@
If no route with the given key and attributes was found,
.B ip route del
-.SS ip route show - list routes
+ip route show
the command displays the contents of the routing tables or the route(s)
selected by some criteria.
@@ -628,8 +641,12 @@
.BI realms " FROMREALM/TOREALM"
only list routes with these realms.
-.SS ip route flush - flush routing tables
+ip route flush
+flush routing tables
this command flushes routes selected by some criteria.
@@ -652,8 +669,12 @@
.B ip route flush
also dumps all the deleted routes in the format described in the
-.SS ip route get - get a single route
+ip route get
+get a single route
this command gets a single route to a destination and prints its
contents exactly as the kernel sees it.
@@ -707,21 +728,30 @@
argument, the kernel pretends that a packet arrived from this interface
and searches for a path to forward the packet.
-.SS ip route save - save routing table information to stdout
-this command behaves like
+ip route save
+save routing table information to stdout
+This command behaves like
.BR "ip route show"
except that the output is raw data suitable for passing to
.BR "ip route restore" .
-.SS ip route restore - restore routing table information from stdin
-this command expects to read a data stream as returned from
+ip route restore
+restore routing table information from stdin
+This command expects to read a data stream as returned from
.BR "ip route save" .
It will attempt to restore the routing table information exactly as
it was at the time of the save, so any translation of information
in the stream (such as device indexes) must be done first. Any existing
routes are left unchanged. Any routes specified in the data stream that
already exist in the table will be ignored.