1in.ripngd(1M) System Administration Commands in.ripngd(1M)
2
6 in.ripngd - network routing daemon for IPv6
7
9 /usr/sbin/in.ripngd [-s] [-q] [-t] [-p n] [-P] [-v ]
10 [logfile]
11
14 in.ripngd is the IPv6 equivalent of in.routed(1M). It is invoked at
15 boot time to manage the network routing tables. The routing daemon uses
16 the Routing Information Protocol for IPv6.
17 in.ripngd is managed by the service management facility (SMF), by means
20 of the service identifier:
21 svc:/network/routing/ripng:default
23 In normal operation, in.ripngd listens on the udp(7P) socket port 521
28 for routing information packets. If the host is an internetwork router,
29 it periodically supplies copies of its routing tables to any directly
30 connected hosts and networks.
31 When in.ripngd is started, it uses the SIOCGLIFCONF ioctl(2) to find
34 those directly connected IPv6 interfaces configured into the system and
35 marked "up"; the software loopback interface is ignored. If multiple
36 interfaces are present, it is assumed the host will forward packets
37 between networks. in.ripngd then multicasts a request packet on each
38 IPv6 interface and enters a loop, listening for request and response
39 packets from other hosts.
40 When a request packet is received, in.ripngd formulates a reply based
43 on the information maintained in its internal tables. The response
44 packet contains a list of known routes. With each route is a number
45 specifying the number of bits in the prefix. The prefix is the number
46 of bits in the high order part of an address that indicate the subnet
47 or network that the route describes. Each route reported also has a
48 "hop count" metric. A count of 16 or greater is considered "infinity."
49 The metric associated with each route returned provides a metric rela‐
50 tive to the sender.
51 The request packets received by in.ripngd are used to update the rout‐
54 ing tables if one of the following conditions is satisfied:
55 o No routing table entry exists for the destination network or
57 host, and the metric indicates the destination is "reach‐
58 able", that is, the hop count is not infinite.
59 o The source host of the packet is the same as the router in
61 the existing routing table entry. That is, updated informa‐
62 tion is being received from the very internetwork router
63 through which packets for the destination are being routed.
64 o The existing entry in the routing table has not been updated
66 for a period of time, defined to be 90 seconds, and the
67 route is at least as cost-effective as the current route.
68 o The new route describes a shorter route to the destination
70 than the one currently stored in the routing tables; this is
71 determined by comparing the metric of the new route against
72 the one stored in the table.
73 When an update is applied, in.ripngd records the change in its internal
76 tables and generates a response packet to all directly connected hosts
77 and networks. To allow possible unstable situations to settle, in.rip‐
78 ngd waits a short period of time (no more than 30 seconds) before modi‐
79 fying the kernel's routing tables.
80 In addition to processing incoming packets, in.ripngd also periodically
83 checks the routing table entries. If an entry has not been updated for
84 3 minutes, the entry's metric is set to infinity and marked for dele‐
85 tion. Deletions are delayed an additional 60 seconds to insure the
86 invalidation is propagated throughout the internet.
87 Hosts acting as internetwork routers gratuitously supply their routing
90 tables every 30 seconds to all directly connected hosts and networks.
91
93 in.ripngd supports the options listed below. Listed with the options
94 are the equivalent SMF property values. These are set for the
95 ripng:default service with a command of the form:
96 # routeadm -m ripng:default key=value
98 -p n Send and receive the routing packets from other routers using
102 the UDP port number n. Use of this option is equivalent to
103 setting the udp_port property.
104 -P Do not use poison reverse. Use of this option is equivalent to
107 setting the poison_reverse property to false.
108 -q Do not supply routing information. Use of this option is equiv‐
111 alent to setting the quiet_mode property to true.
112 -s Force in.ripngd to supply routing information whether it is
115 acting as an internetwork router or not. Use of this option is
116 equivalent to setting the supply_routes property to true.
117 -t Print all packets sent or received to standard output. in.rip‐
120 ngd will not divorce itself from the controlling terminal.
121 Accordingly, interrupts from the keyboard will kill the
122 process. Not supported by the ripng service.
123 -v Print all changes made to the routing tables to standard output
126 with a timestamp. Use of this option is equivalent to setting
127 the verbose property to true.
128 Any other argument supplied to this option is interpreted as
130 the name of the file in which the actions of in.ripngd, as
131 specified by this option or by -t, should be logged instead of
132 being sent to standard output.
133 The logfile can be specified for the ripng service by means of
135 the log_file property.
136
139 See attributes(5) for descriptions of the following attributes:
140 ┌─────────────────────────────┬─────────────────────────────┐
145 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
146 ├─────────────────────────────┼─────────────────────────────┤
147 │Availability │SUNWroute │
148 └─────────────────────────────┴─────────────────────────────┘
149
151 in.routed(1M), routeadm(1M), svcadm(1M), ioctl(2), attributes(5),
152 smf(5), udp(7P)
153 G. Malkin, R. Minnear, RFC 2080, RIPng for IPv6, January 1997.
156
158 The kernel's routing tables may not correspond to those of in.ripngd
159 for short periods of time while processes that utilize existing routes
160 exit; the only remedy for this is to place the routing process in the
161 kernel.
162 in.ripngd currently does not support all of the functionality of
165 in.routed(1M). Future releases may support more if appropriate.
166 in.ripngd initially obtains a routing table by examining the interfaces
169 configured on a machine. It then sends a request on all directly con‐
170 nected networks for more routing information. in.ripngd does not recog‐
171 nize or use any routing information already established on the machine
172 prior to startup. With the exception of interface changes, in.ripngd
173 does not see any routing table changes that have been done by other
174 programs on the machine, for example, routes added, deleted or flushed
175 by means of the route(1M) command. Therefore, these types of changes
176 should not be done while in.ripngd is running. Rather, shut down
177 in.ripngd, make the changes required, and then restart in.ripngd.
178SunOS 5.11 26 Jan 2007 in.ripngd(1M)