Category: RIPng

RIPng

RIP itself is not as complex as the other routing protocols and is in a lot of ways inferior to them, yet the simplicity makes it suitable for Small Office Home Office routers and simple networks.  It’s widely supported with multiple vendors so an IPv6 version of RIP was created called RIP next generation (RIPng)

RIPng remains exactly the same protocol with practically no changes in the underlying protocol mechanisms currently in place.  RIPng is still a distance vector protocol using UDP port 521 instead of 520 and incrementing hop count at the destination now instead of the advertiser of an update.  It uses multicast address FF02::9 to send messages to and 16 is still infinity.

ripngheader.PNG

Authentication is not handled by RIPng instead these authentication functions are offloaded to IPSEC.  RIPng currently lacks support for several features supported by RIPv2

  • Authentication or encryption by IPSEC is not supported
  • Split Horizon can be activated or deactivated only on a per process basis, not on individual interfaces
  • Passive interfaces are not supported
  • Static neighbors cannot be configured
  • Per process offset lists are not supported

Here are the management improvements over RIPv2 seen in RIPng:

  • Multiple RIPng processes can be run on a single router
  • Route poisoning can be activated on a per process basis
  • Interfaces can be configured with a metric offset value that is added to the metric for all received advertisements allowing RIPng to operate with link costs as opposed to hop counts
  • the default route can be originated on a per interface basis including an option of suppressing all other updates over an interface.