RIPng is abbreviation for RIP next generation. It is defined in RFC 2080 and is an extension of RIPv2 for supporting of IPv6. The main enhancement in RIPng compared to RIPv2 are –
While RIPv2 supports RIPv1 updates authentication, RIPng does not.
RIPv2 encodes the next-hop into each route entry, RIPng requires specific encoding of the next hop for a set of route entries.
RIPng sends updates on UDP port 521 using the multicast group FF02::9.
To enable RIPng, no global configuration is required. However, to include commands that would affect the complete RIPng configuration like timers, maximum-paths, etc, RIPng router configuration mode is required. Also, multiple RIPng processes can be run on a single router.
Below is a sample scenario showing RIPng configuration happening between 2 IPV6 enabled Routers. The following IPV6 has been assigned to R1 and R2 Interfaces –
Notable is that both the interfaces Fa0/0 of R1 and R2 are in different subnet and still communicate RIPng Routes and communicate to each other.
R2 receives routing updates from r1 on its link local address (FE80::C000:1FF:FE78:0)
RIPng communication takes place on source and destination port 521
The communication takes place on multicast address of FF02::9
Another key command output for RIPng protocol is “show ipv6 rip”.he output of comman dis given below –
R1#show ipv6 rip
RIP process “RIP“, port 521, multicast-group FF02::9, pid 214
Administrative distance is 120. Maximum paths is 16
Updates every 30 seconds, expire after 180
Holddown lasts 0 seconds, garbage collect after 120
Split horizon is on; poison reverse is off
Default routes are not generated
Periodic updates 105, trigger updates 4