26.1.6 Notes
Note the following restrictions when configuring a network that uses RIPng.
- <Structure of this section>
(1) Difference from RFC
The Switch complies with RFC 2080 (RIPng version 1). However, there are some differences due to the functional limitations of the software. The following table describes the differences with the RFC.
|
RFC |
Switch |
|
|---|---|---|
|
must be zero field |
Nothing is specified for processing. |
The Switch does not check the value of the must be zero field. This field is set to 0 when sending information. |
|
Network prefix |
Nothing is specified for the status of the address field after the prefix length. |
If the address field after the prefix length in routing information in the received RIPng packet is not cleared to zero, the addresses after the prefix length are cleared to zero. |
|
Triggered update |
After triggered update, a random timer of 1-5 seconds should be configured, and updates will be performed upon timeout, even if there is a change to send an update prior to the timeout. |
The random timer of 1 to 5 seconds is not set after triggerd update, and triggered update is performed whenever routing information is changed. |
|
If there is a normal update during the random timer activation of 1 to 5 seconds after triggered update, triggered update may be suppressed. |
Triggered updates are not suppressed. |
|
|
Split horizon |
The split horizon setting must be capable of being changed for an interface. |
The Switch does not support changing of the split horizon setting for an interface. |
|
Specification of next-hop information for routes |
Next-hop information for a route can be explicitly specified. |
RIPng packets sent by the Switch does not contain next-hop information. If the Switch receives an RIPng packet with explicitly specified next-hop information, the specified value is used as the next hop. |
|
Destination of a response packet |
If ff02::9 is not an appropriate destination (for example, NBMA network), the destination depends on the implementation. |
The Switch does not support RIPng operations on the NBMA network. |
|
Per |
An IPv6 authentication header and encrypted header are used to authenticate a packet. |
The Switch does not support packet authentication that uses an IPv6 authentication header and encrypted header. |
|
Sending response packets when request packets are received via unicast from any port other than source port 521 |
Response packets can be directly sent to the source address. |
The Switch sends response packets only for request packets for which a link-local address is specified as the source address. |