26.1.5 RIPng functions
RIPng sets the prefix length of advertised routes in the routing information, allowing variable-length prefix lengths to be handled. The following describes the RIPng features.
- <Structure of this section>
(1) Authentication function
The Switch does not support the authentication functionality.
(2) Route tag
In the Switch, route tags are written to routing tables if set in the routing information reported in a response message. The route tag of the corresponding entry in the routing table is set as the route tag in the routing information in the response message sent by the Switch. The range that can be used is 1 to 65535 (decimal).
RIPng does not support filtering by using route tags in the import filter or changing of route tags in the export filter (distribution of routes to RIPng from another protocol).
(3) Prefix
In the Switch, the prefix length of the routing information reported in a response message is written to the routing table. The prefix length of the corresponding entry in the routing table is set as the prefix length in the routing information in the response message sent by the Switch.
(4) Next hop
In the Switch, next-hop information is written to the routing tables if set in the routing information reported in a response message. If no next-hop information is set, the originating gateway is regarded as the next hop.
The next-hop information in the routing information is not set in a response message sent from the Switch. Accordingly, a router that received a route from the Switch via RIPng uses the source interface address as the next hop.
(5) Using link-local multicast addresses
The Switch supports link-local multicasting to reduce the unnecessary load on the hosts that do not receive RIPng messages. The link-local multicast address used for transmitting RIPng messages is the multicasting address for all RIPng routers (ff02::9).