RIP6 routing daemon
route6d [-aDdhlqSs] [-A prefix/preflen,if1[,if2...]]
[-N if1[,if2...]] [-O prefix/preflen,if1[,if2...]]
[-R routelog] [-T if1[,if2...]] [-t tag]
- -A prefix/preflen,if1[,if2...]
- Allow routes to be aggregated, where
prefix specifies the prefix, and preflen 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,
A static route to prefix/preflen with the RTF_REJECT flag is created
in the kernel routing table.
- Enable the aging of the statically-defined routes.
Remove any statically-defined routes unless the
corresponding updates arrive as if the routes are received at the startup of route6d.
- Enable extensive output of debugging messages and
instruct route6d to run in the foreground (don't become a daemon).
- Enable the output of debugging message and
instruct route6d to run in the foreground (don't become daemon).
- Disable the split-horizon processing.
- -L prefix/preflen,if1[,if2...]
- Filter incoming routes from interfaces if1,[if2...] and
accept incoming routes that are in prefix/preflen.
If you'd like to accept any route, don't specify this option.
If multiple -L options are specified, any routes that match one of the options is accepted.
If ::/0 is specified, it's treated as the default route,
not "any route that has longer prefix length than, or equal to 0."
For example, route6d accepts the default route and routes in the 6bone test address, but in no others,
if you specify:
-L 3ffe::/16,if1 -L ::/0,if1
- Exchange site-local routes as well.
By default, they aren't exchanged because of safety reasons.
The semantics of the site-local address space is rather vague (the specification is still being worked on),
and there's no good way to define site-local boundaries.
It must not be used on site-boundary routers,
since this option assumes that all interfaces are in the same site.
- -N if1[,if2...]
- Don't listen to, or advertise, routes from or to interfaces specified by if1,[if2...].
- -O prefix/preflen,if1[,if2...]
- Restrict route advertisements toward interfaces specified by if1,[if2...]
and only advertise routes that match prefix/preflen.
- Listen-only mode. Don't send advertisements.
- -R routelog
- Log the route change (add/delete) to the file routelog.
- Same as -s, except that the split-horizon rule doesn't apply.
- Advertise the statically defined routes that exist in the kernel routing table when route6d invoked.
Announcements obey the regular split-horizon rule.
- -T if1[,if2...]
- Advertise only default routes toward if1,[if2...].
- -t tag
- Attach this route tag to originated route entries.
You can specify tag in decimal, octal (prefixed by 0), or hexadecimal (prefixed by 0x).
The route6d utility is a routing daemon which supports
Routing Information Procotol (RIP) over IPv6.
When a SIGINT or SIGUSR1 signal is received,
route6d dumps the current internal state into /var/run/route6d_dump.
The route6d utility uses IPv6 advanced API, defined in RFC2292,
for communicating with peers using link-local addresses.
Internally route6d embeds the interface identifier into bits 32 to 63 of
link-local addresses (fe80::xx and ff02::xx) so they'll be visible
on the internal state dump file (/var/run/route6d_dump).
The routing table manipulation differs from IPv6 implementation to implementation.
Currently route6d obeys WIDE Hydrangea/KAME IPv6 kernel.
Currently, route6d doesn't reduce the rate of the triggered updates when
consecutive updates arrive.
- Dump internal state on SIGINT or SIGUSR1.
G. Malkin, and R. Minnear, RIPng for IPv6, RFC2080, January 1997.