route

Manually manipulate the routing tables

Syntax:

route [-f] [-n] [-q] [-v] command { [[modifiers] args] }

Options:

-f
Remove all routes (as per flush). If used in conjunction with the add, change, delete, or get commands, route removes the routes before performing the command.
-n
Don't print host and network names symbolically when reporting actions. (The process of translating between symbolic names and numerical equivalents can be quite time consuming, and may require correct operation of the network; thus it may be expedient to forgo this, especially when attempting to repair networking operations.)
-q
Be quiet: suppress all output.
-v
Be verbose: print additional details.
command [[modifiers] args]
Valid commands are: add, change, delete, flush, and show. See the "Description" section for the syntax and description of each command.

Description:

You use the route utility to manually manipulate the network routing tables. Because the routing tables are usually taken care of by the routed daemon, you rarely need to use this utility.

command options

The route utility accepts the following commands: add, change, delete, flush, get, monitor, and show.

Here's the syntax and the description for each command:

[-n] add [-net|-host] destination gateway
Add a route.
[-n] change [-net|-host] destination gateway
Change aspects of a route (such as its gateway).
[-n] delete [-net|-host] destination gateway
Delete a specific route.
[-n] flush [family]
(INET and INET6 only) Flush the routing tables of all gateway entries. If you want to delete only routes having destinations with addresses in a specified family, specify INET or INET6 as the family variable.
[-n] get [-net|-host] destination gateway
Look up and display the route for a destination.
[-n] monitor
Report changes to the routing information on a continuing basis.
[-n] show
Display route table (similar to netstat -r).
destination
The destination host or network.
gateway
The next-hop gateway that packets should be addressed to.

If the keyword, default, or the network address, 0.0.0.0, is specified, then all packets sent to a remote network that's not defined in the routing tables, are sent to the specified gateway.

If you have an Internet Service Provider (ISP), packets sent to hosts on the Internet are sent to a gateway provided by the ISP. See the defaultroute option in pppd .

Routes to a particular host are distinguished from those to a network by interpreting the Internet address associated with destination. Specifying the optional keywords -net and -host force the destination to be interpreted as a network or a host, respectively.

If the destination has a "local address part" of INADDR_ANY, or if the destination is the symbolic name of a network, then the route is assumed to be to a network; otherwise, the route is assumed to be to a host. For example:

This destination: Is interpreted as:
128.32 -host 128.0.0.32
128.32.130 -host 128.32.0.130
-net 128.32 128.32.0.0
-net 128.32.130 128.32.130.0.

If the route is via an interface rather than via a gateway, you should specify the -interface modifier; the gateway given is the address of this host on the common network, indicating the interface to be used for transmission.

You can use the optional -netmask modifier to specify an additional address parameter that's interpreted as a network mask. You can use this like an OSI ESIS redirect with the netmask option, or to manually add subnet routes with netmasks different from that of the implied network interface (as would otherwise be communicated using the OSPF or ISIS routing protocols). After -netmask, enter the address parameter you want interpreted as the network mask.

You can override the implicit network mask generated in the INET case by placing this option after the destination parameter.

Similarly, you can use the -prefixlen modifier for IPv6.

Routes have associated flags which influence operation of the protocols when sending to destinations matched by the routes. These flags may be set (or sometimes cleared) by indicating the following corresponding modifiers:

-cloning
RTF_CLONING — generates a new route on use
-xresolve
RTF_XRESOLVE — emit mesg on use (for external lookup)
-iface
~RTF_GATEWAY — destination is directly reachable
-static
RTF_STATIC — manually added route
-nostatic
~RTF_STATIC — pretend route added by kernel or daemon
-reject
RTF_REJECT — emit an ICMP unreachable when matched
-blackhole
RTF_BLACKHOLE — silently discard pkts (during updates)
-proto1
RTF_PROTO1 — set protocol specific routing flag #1
-proto2
RTF_PROTO2 — set protocol specific routing flag #2
-llinfo
RTF_LLINFO — validly translates proto addr to link addr

The optional modifiers:

  • -expire
  • -hopcount
  • -mtu
  • -recvpipe
  • -rtt
  • -rttvar
  • -sendpipe
  • -ssthresh

provide initial values to metrics maintained in the routing entry. To lock any of these modifiers, precede the modifier with the -lock meta-modifier; you can also specify the -lockrest meta-modifier to lock all ensuing metrics.

All symbolic names specified for a destination or gateway are looked up first as a hostname using gethostname(). If this lookup fails, getnetbyname() is then used to interpret the name as that of a network.

The route utility uses a routing socket and the new message types RTM_ADD, RTM_DELETE, and RTM_CHANGE. As such, only the superuser may modify the routing tables.

Diagnostics

add [host | network ] %s: gateway %s flags %x
The specified route is being added to the tables. The values printed are from the routing table entry supplied in the ioctl() call. If the gateway address used isn't the primary address of the gateway—the first one returned by gethostname() — the gateway address is printed numerically as well as symbolically.
delete [ host &| network ] %s: gateway %s flags %x
As above, but when deleting an entry.
%s %s done
A routing table entry is being deleted by the flush command.
Network is unreachable
An attempt to add a route failed because the gateway listed wasn't on a directly connected network. The next-hop gateway must be given.
not in table
A delete operation was attempted for an entry not present in the tables.
routing table overflow
An add operation was attempted, but the system was low on resources and couldn't allocate memory to create the new entry.
Permission denied
The attempted operation is privileged. Only root may modify the routing tables. These privileges are enforced by the kernel.

License:

This utility is based on copyright software of the Regents of the University of California and of Christos Zoulas; for licensing information, see the Third Party License Terms List at http://licensing.qnx.com/third-party-terms/ .

Last modified: 2013-12-21

comments powered by Disqus