327
RIPng packet processing procedure
Request packet
When a RIPng router first starts or must update some entries in its routing table, generally a
multicast request packet is sent to ask for needed routes from neighbors.
The receiving RIPng router processes RTEs in the request. If there is only one RTE with the IPv6
prefix, with the prefix length both being 0 and with a metric value of 16, then the RIPng router
will respond with the entire routing table information in response messages. If there are multiple
RTEs in the request message, the RIPng router will examine 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
Configuring RIPng basic functions
This section presents the information to configure the basic RIPng features.
You must enable RIPng first before configuring other tasks, but it is not necessary for RIPng-related
interface configurations, such as assigning an IPv6 address.
Prerequisites
•
Enable IPv6 packet forwarding.
•
Configure an IP address for each interface, and ensure all nodes are reachable to one
another.
To do…
Use the command…
Remarks
Step 1
Enter system view
system-view
––
Step 2
Create a RIPng process
and enter RIPng view
ripng
[
process-id
]
Required
Not created by default