ROUTE6D(8)
β¨ ROUTE6D(8) β¨
okay bestie so this is route6d, from the System Manager's Manual, and it's giving networking daemon in the most iconic way π
π NAME π
route6d β the RIP6 Routing Daemon, no cap π
π¨ DEPRECATION NOTICE π¨
bestie. listen to me. The route6d utility is deprecated and will be removed in FreeBSD 16.0. it's literally on its way out π not me warning you before you build your whole setup on it π
π¦ SYNOPSIS π¦
route6d [-adDhlnqsS] [-R routelog] [-A prefix/preflen,if1[,if2...]]
[-L prefix/preflen,if1[,if2...]] [-N if1[,if2...]]
[-O prefix/preflen,if1[,if2...]] [-P number] [-p pidfile]
[-Q number] [-T if1[,if2...]] [-t tag]
πΈ DESCRIPTION πΈ
So the route6d utility is a routing daemon that supports RIP over IPv6 β like, that's its whole personality π
Here are the options, and yes we're doing all of them, periodt:
-aβ turns on aging for the statically defined routes. With this on, any statically defined routes get removed unless corresponding updates show up, just as if the routes were received at the startup ofroute6d. bestie they will literally expire on you π-Rroutelog β this one makesroute6dlog the route change (add/delete) into the file routelog. receipts, but for routes π§Ύ-Aprefix/preflen,if1[,if2...] β the aggregating-routes option β¨ prefix/preflen is the prefix and the prefix length of the aggregated route. When it's advertising routes,route6dfilters out the specific routes that are covered by the aggregate and advertises the aggregated route prefix/preflen to the interfaces you listed in the comma-separated interface list, if1[,if2...]. and the characters*,?, and[in the interface list get interpreted as shell-style pattern. theroute6dutility also creates a static route to prefix/preflen with theRTF_REJECTflag, straight into the kernel routing table π-dβ turns on output of debugging messages. this option also tellsroute6dto run in foreground mode (so it does not become a daemon). lowkey my fave for watching what's happening π-Dβ turns on extensive output of debugging messages. yes, even more. and this option also tellsroute6dto run in foreground mode (does not become a daemon). it's a lot. it's giving verbose π-hβ disables the split horizon processing.-lβ so, by defaultroute6dwill not exchange site local routes, for safety reasons. why? because the semantics of site local address space are rather vague (the spec is still being worked on) and there's no good way to define the site local boundary π« with the-loption,route6dwill exchange site local routes as well. but it must not be used on site boundary routers, since-lassumes that all interfaces are in the same site. so like, careful π-Lprefix/preflen,if1[,if2...] β filters incoming routes from the interfaces if1,[if2...]. theroute6dutility will accept incoming routes that are in prefix/preflen. if you specify multiple-Loptions, any route that matches one of the options gets accepted.::/0is treated specially as the default route, not as "any route that has longer prefix length than, or equal to 0". if you'd like to accept any route, just specify no-Loption at all. for example, with-L 2001:db8::/16,if1 -L ::/0,if1theroute6dwill accept the default route and routes in the 6bone test address, but no others π―-nβ do not update the kernel routing table. hands off π ββοΈ-Nif1[,if2...] β do not listen to, or advertise, routes from/to the interfaces specified by if1,[if2...].-Oprefix/preflen,if1[,if2...] β restricts route advertisement toward the interfaces specified by if1,[if2...]. with this optionroute6dwill only advertise routes that match prefix/preflen.-Pnumber β specifies routes to be ignored in the calculation of the expiration timer. number must be1,2, or3, and it means the route flagsRTF_PROTO1,RTF_PROTO2, orRTF_PROTO3respectively. when1is specified, routes withRTF_PROTO1will never expire β³-ppidfile β specifies an alternative file in which to store the process ID. the default is/var/run/route6d.pidπ-Qnumber β specifies the flag that will be used for routes added by the RIP protocol. the default is2(RTF_PROTO2).-qβ putsroute6din listen-only mode. no advertisement is sent. it's giving lurker π-sβ makesroute6dadvertise the statically defined routes that exist in the kernel routing table whenroute6dis invoked. announcements obey the regular split horizon rule β¨-Sβ this option is the same as-sexcept that no split horizon rule applies.-Tif1[,if2...] β advertise only the default route, toward if1,[if2...].-ttag β attach the route tag tag to originated route entries. tag can be decimal, octal prefixed by0, or hexadecimal prefixed by0xπ·οΈ
omg also, upon receipt of signal SIGINT or SIGUSR1, route6d will dump the current internal state into /var/run/route6d_dump πΎ like a lil screenshot of its soul.
π FILES π
/var/run/route6d_dumpβ dumps internal state onSIGINTorSIGUSR1
π SEE ALSO π
G. Malkin and R. Minnear, RIPng for IPv6, RFC2080, January 1997. the β¨source materialβ¨ iykyk
π NOTE π
the route6d utility uses the IPv6 advanced API, defined in RFC2292, for communicating with peers using link-local addresses π¦
internally, route6d embeds the interface identifier into bit 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) π
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. like, it's exclusive π
and current route6d does not reduce the rate of the triggered updates when consecutive updates arrive β so yeah, it's just gonna go brrr π₯
and that's the whole page bestie!! this one came from the Debian manual set, dated May 20, 2025 β mwah, go touch some IPv6 routes and stay hydrated π«Άπβ¨
π¦ where this page comes from
- freebsd 14.5: base 14.5
- freebsd 15.1: base 15.1
- Copyright (c) 1996 WIDE Project. All rights reserved
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms