1 .\" Copyright (c) 1983, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" @(#)route.8 8.3 (Berkeley) 3/19/94
36 .Nd manually manipulate the routing tables
48 utility is used to manually manipulate the network
50 It normally is not needed, as a
51 system routing table management daemon, such as
53 should tend to this task.
57 utility supports a limited number of general options,
58 but a rich command language, enabling the user to specify
59 any arbitrary request that could be delivered via the
60 programmatic interface discussed in
63 The following options are available:
64 .Bl -tag -width indent
68 address family as family hint for subcommands.
72 address family as family hint for subcommands.
74 Run in debug-only mode, i.e., do not actually modify the routing table.
76 Bypass attempts to print host and network names symbolically
77 when reporting actions.
78 (The process of translating between symbolic
79 names and numerical equivalents can be quite time consuming, and
80 may require correct operation of the network; thus it may be expedient
81 to forget this, especially when attempting to repair networking operations).
83 Run in test-only mode.
85 is used instead of a socket.
87 (verbose) Print additional details.
89 Suppress all output from the
90 .Cm add , change , delete ,
98 utility provides the following commands:
100 .Bl -tag -width Fl -compact
106 Delete a specific route.
112 Change aspects of a route (such as its gateway).
114 Lookup and display the route for a destination.
116 Continuously report any changes to the routing information base,
117 routing lookup misses, or suspected network partitionings.
124 The monitor command has the syntax:
126 .Bd -ragged -offset indent -compact
129 .Cm monitor Op Fl fib Ar number
132 The flush command has the syntax:
134 .Bd -ragged -offset indent -compact
137 .Cm flush Oo Ar family Oc Op Fl fib Ar number
142 command is specified,
144 will ``flush'' the routing tables of all gateway entries.
145 When the address family may is specified by any of the
149 modifiers, only routes having destinations with addresses in the
150 delineated family will be deleted.
155 can be used as aliases for
162 option is specified, the operation will be applied to
166 The add command has the following syntax:
168 .Bd -ragged -offset indent -compact
172 .Op Fl net No \&| Fl host
173 .Ar destination gateway
178 and the other commands have the following syntax:
180 .Bd -ragged -offset indent -compact
184 .Op Fl net No \&| Fl host
186 .Op Ar gateway Op Ar netmask
192 is the destination host or network,
194 is the next-hop intermediary via which packets should be routed.
195 Routes to a particular host may be distinguished from those to
196 a network by interpreting the Internet address specified as the
199 The optional modifiers
203 force the destination to be interpreted as a network or a host, respectively.
207 .Dq local address part
213 is the symbolic name of a network, then the route is
214 assumed to be to a network; otherwise, it is presumed to be a
218 could also be specified in the
219 .Ar net Ns / Ns Ar bits
225 .Fl host Li 128.0.0.32 ;
228 .Fl host Li 128.32.0.130 ;
232 .Fl net Li 128.32.130
238 .Fl net Li 192.168.64 Fl netmask Li 255.255.240.0 .
244 is a synonym for the default route.
248 .Fl net Fl inet Li 0.0.0.0 ,
252 .Fl net Fl inet6 Li :: .
254 If the destination is directly reachable
255 via an interface requiring
256 no intermediary system to act as a gateway, the
258 modifier should be specified;
259 the gateway given is the address of this host on the common network,
260 indicating the interface to be used for transmission.
261 Alternately, if the interface is point to point the name of the interface
262 itself may be given, in which case the route remains valid even
263 if the local or remote addresses change.
268 to achieve the effect of an OSI ESIS
269 redirect with the netmask option,
270 or to manually add subnet routes with
271 netmasks different from that of the implied network interface
272 (as would otherwise be communicated using the OSPF or ISIS routing protocols).
273 One specifies an additional ensuing address parameter
274 (to be interpreted as a network mask).
275 The implicit network mask generated in the AF_INET case
276 can be overridden by making sure this option follows the destination parameter.
283 is available instead of the
285 qualifier because non-continuous masks are not allowed in IPv6.
288 specifies that a network mask of
289 .Li ffff:ffff:0000:0000:0000:0000:0000:0000
291 The default prefixlen is 64.
292 However, it is assumed to be 0 if
296 Note that the qualifier works only for
300 Routes have associated flags which influence operation of the protocols
301 when sending to destinations matched by the routes.
302 These flags may be set (or sometimes cleared)
303 by indicating the following corresponding modifiers:
305 -xresolve RTF_XRESOLVE - emit mesg on use (for external lookup)
306 -iface ~RTF_GATEWAY - destination is directly reachable
307 -static RTF_STATIC - manually added route
308 -nostatic ~RTF_STATIC - pretend route added by kernel or daemon
309 -reject RTF_REJECT - emit an ICMP unreachable when matched
310 -blackhole RTF_BLACKHOLE - silently discard pkts (during updates)
311 -proto1 RTF_PROTO1 - set protocol specific routing flag #1
312 -proto2 RTF_PROTO2 - set protocol specific routing flag #2
315 The optional modifiers
325 provide initial values to quantities maintained in the routing entry
326 by transport level protocols, such as TCP or TP4.
327 These may be individually locked by preceding each such modifier to
331 meta-modifier, or one can
332 specify that all ensuing metrics may be locked by the
338 accepts expiration time of the route as the number of seconds since the
341 When the first character of the number is
345 it is interpreted as a value relative to the current time.
347 The optional modifier
349 specifies that the command will be applied to a non-default FIB.
352 must be smaller than the
356 When this modifier is not specified,
357 or a negative number is specified,
358 the default FIB shown in the
365 allows multiple FIBs by a comma-separeted list and/or range
369 means the FIB number 2, 4, and 6.
371 .Qq Fl fib Li 1,3-5,6
372 means the 1, 3, 4, 5, and 6.
378 command where the destination and gateway are not sufficient to specify
379 the route (as in the ISO case where several interfaces may have the
384 modifiers may be used to determine the interface or interface address.
386 All symbolic names specified for a
390 are looked up first as a host name using
391 .Xr gethostbyname 3 .
392 If this lookup fails,
394 is then used to interpret the name as that of a network.
398 utility uses a routing socket and the new message types
399 .Dv RTM_ADD , RTM_DELETE , RTM_GET ,
402 As such, only the super-user may modify
405 .Fx provides support for scalable multipath routing.
406 It is activated by default, but can be turned off by setting the
407 .Va net.route.multipath
411 There are multiple route lookup algorithms available.
412 They can be configured by setting
413 .Va net.route.algo.inet.algo
415 .Va net.route.algo.inet6.algo
420 A list of available algorithms can be obtained by accessing the
424 .Va net.route.algo.inet.algo_list
426 .Va net.route.algo.inet6.algo_list
429 The following algorithms are available:
430 .Bl -tag -width radix_lockless
432 Base system radix backend.
434 Lockless binary search in a special IP array, tailored for a small FIB
436 This algorithm is only available for IPv4.
438 Lockless immutable radix, re-created on every rtable change,
439 tailored for a small FIB with <1000 routes.
441 DPDK DIR24-8-based lookups, lockless datastructure, optimized
443 In order to use the dpdk_lpm algorithm one or both of the
444 following kernel modules must be loaded via
446 .Bl -tag -width dpdk_lpm6.ko -compact
448 DPDK implementation for IPv4.
450 DPDK implementation for IPv6.
454 The algorithms are selected automatically based on the size of the routing
456 They can be changed, but not every algorithm performs best for every
461 Add a default route to the network routing table.
462 This will send all packets for destinations not available in the routing table
463 to the default gateway at 192.168.1.1:
465 .Dl route add -net 0.0.0.0/0 192.168.1.1
467 A shorter version of adding a default route can also be written as:
469 .Dl route add default 192.168.1.1
471 Add a static route to the 172.16.10.0/24 network via the 172.16.1.1 gateway:
473 .Dl route add -net 172.16.10.0/24 172.16.1.1
475 Change the gateway of an already established static route in the routing table:
477 .Dl route change -net 172.16.10.0/24 172.16.1.2
479 Display the route for a destination network:
481 .Dl route show 172.16.10.0
483 Delete a static route from the routing table:
485 .Dl route delete -net 172.16.10.0/24 172.16.1.2
487 Remove all routes from the routing table:
491 List all routing tables:
496 .It "add [host \&| network ] %s: gateway %s flags %x"
497 The specified route is being added to the tables.
499 values printed are from the routing table entry supplied
503 If the gateway address used was not the primary address of the gateway
504 (the first one returned by
505 .Xr gethostbyname 3 ) ,
506 the gateway address is printed numerically as well as symbolically.
507 .It "delete [ host \&| network ] %s: gateway %s flags %x"
508 As above, but when deleting an entry.
512 command is specified, each routing table entry deleted
513 is indicated with a message of this form.
514 .It "Network is unreachable"
515 An attempt to add a route failed because the gateway listed was not
516 on a directly-connected network.
517 The next-hop gateway must be given.
519 A delete operation was attempted for an entry which
520 was not present in the tables.
521 .It "routing table overflow"
522 An add operation was attempted, but the system was
523 low on resources and was unable to allocate memory
524 to create the new entry.
525 .It "gateway uses the same route"
528 operation resulted in a route whose gateway uses the
529 same route as the one being changed.
530 The next-hop gateway should be reachable through a different route.
545 The first paragraph may have slightly exaggerated
549 Currently, routes with the
551 flag set need to have the gateway set to an instance of the
555 option, for the flag to have any effect; unless IP fast forwarding
556 is enabled, in which case the meaning of the flag will always