The receiving RIPng router processes RTEs in the request. If only one RTE exists with the IPv6 prefix and
prefix length both being 0 and with a metric value of 16, the RIPng router responds with the entire routing
table information in response messages. If multiple RTEs exist in the request message, the RIPng router
examines each RTE, update its metric, and send the requested routing information to the requesting router
in the response packet.
Response packet
The response packet containing the local routing table information is generated as follows:
A response to a request
•
•
An update periodically
A trigged update caused by route change
•
After receiving a response, a router checks the validity of the response before adding the route to its
routing table, such as whether the source IPv6 address is the link-local address and whether the port
number is correct. The response packet that failed the check is discarded.
Protocols and standards
RFC 2080, RIPng for IPv6
•
RFC 2081, RIPng Protocol Applicability Statement
•
RIPng configuration task list
Task
Configuring RIPng basic functions
Configuring RIPng route control
Tuning and optimizing the RIPng
network
Applying IPsec policies for RIPng
Configuring RIPng basic functions
This section presents the information to configure the basic RIPng features.
You must enable RIPng first before you configure other tasks, but it is not necessary for RIPng-related
interface configurations, such as assigning an IPv6 address.
Configuring an additional routing metric
Configuring RIPng route summarization
Advertising a default route
Configuring a RIPng route filtering policy
Configuring a priority for RIPng
Configuring RIPng route redistribution
Configuring RIPng timers
Configuring split horizon and poison reverse
Configuring zero field check on RIPng packets
Configuring the maximum number of ECMP routes
279
Remarks
Required.
Optional.
Optional.
Optional.
Optional.
Optional.
Optional.
Optional.
Optional.
Optional.
Optional.
Optional.