utility is a routing daemon which
supports RIP over IPv6.
The options are as follows:
- This option is used for aggregating routes.
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
to the interfaces specified in the comma-separated interface list
route6d creates a static route to
RTF_REJECT flag set, into the
kernel routing table.
- 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
- 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).
- Enables output of debugging messages. This option also
instructs route6d to run in foreground mode
(i.e. it does not become a daemon process).
- Disables split horizon processing.
- Filter incoming routes from interfaces
route6d will accept incoming routes that are
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
- 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
- Do not listen to, or advertise, route from/to interfaces
- Do not update the kernel routing table.
- Restrict route advertisement toward interfaces specified by
With this option route6d will only advertise
routes that match
- Makes route6d use listen-only
mode. No advertisement is sent.
- This option is the same as -s,
except that the split horizon rule does apply.
- 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.
- Advertise only the default route toward
- Attach the route tag tag
to originated route entries. tag can be
decimal, octal prefixed by
0, or hexadecimal
- Always log route updates (insertions and deletions). Route
updates are always prefixed with “RTADD” or
Upon receipt of signal
will log a dump of the current internal
G. Malkin and
R. Minnear, RIPng for IPv6,
RFC 2080, January
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.
obeys the WIDE Hydrangea/KAME
IPv6 kernel, and will not be able to run on other platforms.
does not reduce the rate of the
triggered updates when consecutive updates arrive.