ROUTE6D(8) | System Manager's Manual | ROUTE6D(8)

# NAME

`route6d` — Routing Information Protocol (RIP) for IPv6 daemon

# SYNOPSIS

`route6d` | [`-aDdhlnqSsu`] [`-A` prefix/preflen,if1[,if2,...]] [`-L` prefix/preflen,if1[,if2,...]] [`-N` if1[,if2,...]] [`-O` prefix/preflen,if1[,if2,...]] [`-T` if1[,if2,...]] [`-t` tag]

# DESCRIPTION

The `route6d` utility is a routing daemon which supports RIP over IPv6.

The options are as follows:

`-A` prefix/preflen,if1[,if2,...]
  This option is used for aggregating routes. prefix/preflen specifies the prefix and the prefix length of the aggregated route. When advertising routes, `route6d` filters specific routes covered by the aggregate and advertises the aggregated route prefix/preflen to the interfaces specified in the comma-separated interface list if1[,if2,...]. `route6d` creates a static route to prefix/preflen, with the `RTF_REJECT` flag set, into the kernel routing table.
`-a`
  Enables aging of the statically defined routes. With this option, any statically defined routes will be removed unless corresponding updates arrive as if the routes are received at the startup of `route6d`.
`-D`
  Enables extensive output of debugging messages. This option also instructs `route6d` to run in foreground mode (i.e. it does not become a daemon process).
`-d`
  Enables output of debugging messages. This option also instructs `route6d` to run in foreground mode (i.e. it does not become a daemon process).
`-h`
  Disables split horizon processing.
`-L` prefix/preflen,if1[,if2,...]
  Filter incoming routes from interfaces if1[,if2,...]. `route6d` will accept incoming routes that are in prefix/preflen. If multiple `-L` options are specified, all routes that match any of the options are accepted. `::/0` is treated specially as the default route, not “any route that has longer prefix length than, or equal to, 0”. For example, with “-L 2001:db8::/32,if1 -L ::/0,if1”, `route6d` will accept the default route and routes in the 2001:db8::/32 address range, but no others. To accept any route, simply do not specify the `-L` option.
`-l`
  By default, `route6d` will not exchange site local routes for safety reasons. This is because the semantics of site local address space are rather vague, as the specification is still being worked on, and there is no good way to define the site local boundary. With `-l`, `route6d` will exchange site local routes as well. It must not be used on site boundary routers, since `-l` assumes that all interfaces are in the same site.
`-N` if1[,if2,...]
  Do not listen to, or advertise, route from/to interfaces specified by if1[,if2,...].
`-n`
  Do not update the kernel routing table.
`-O` prefix/preflen,if1[,if2,...]
  Restrict route advertisement toward interfaces specified by if1[,if2,...]. With this option `route6d` will only advertise routes that match prefix/preflen.
`-q`
  Makes `route6d` use listen-only mode. No advertisement is sent.
`-S`
  This option is the same as `-s`, except that the split horizon rule does apply.
`-s`
  Makes `route6d` advertise the statically defined routes which exist in the kernel routing table when `route6d` is invoked. Announcements obey the regular split horizon rule.
`-T` if1[,if2,...]
  Advertise only the default route toward if1[,if2,...].
`-t` tag
  Attach the route tag tag to originated route entries. tag can be decimal, octal prefixed by `0`, or hexadecimal prefixed by `0x`.
`-u`
  Always log route updates (insertions and deletions). Route updates are always prefixed with “RTADD” or “RTDEL”.

Upon receipt of signal `SIGINT` or `SIGUSR1`, `route6d` will log a dump of the current internal state.

# SEE ALSO

ripd(8)

# STANDARDS

G. Malkin and R. Minnear, RIPng for IPv6, RFC 2080, January 1997.

# NOTES

`route6d` uses the advanced IPv6 API, defined in RFC 3542, for communicating with peers using link-local addresses.

Routing table manipulation differs from IPv6 implementation to implementation. Currently `route6d` obeys the WIDE Hydrangea/KAME IPv6 kernel, and will not be able to run on other platforms.

Currently, `route6d` does not reduce the rate of the triggered updates when consecutive updates arrive.

March 4, 2023 | Debian