home

Supported platforms

Getting startedOverviewArchitectureSupported platformsRelease notesWhite papers
Getting startedOverviewArchitectureSupported platformsRelease notesWhite papers

Vyatta documentation

Learn how to install, configure, and operate the Vyatta Network Operating System (Vyatta NOS) and Orchestrator, which help drive our virtual networking and physical platforms portfolio.

Show On this page:

Show Page Sections

thumbnailSupported platforms

RIPng

RIPng Configuration

RIPng overview

RIPng is a dynamic routing protocol that is suitable for small, homogenous IPv6 networks. It is classified as an interior gateway protocol (IGP) and employs the distance-vector routing algorithm. RIPng determines the best path by counting the hops to the destination. The maximum hop count is 15 (16 is considered an infinite distance), making RIPng less suitable for large networks. RIPng is an extension of RIP version 2 for IPv6.

Supported standards

The vRouter implementation of RIPng complies with the following standards:

  • RFC 2080: RIPng for IPv6
  • RFC 2081: RIPng Protocol Applicability Statement

Configuring RIPng

This section presents the following topics:

  • Enable forwarding on R1 and R2
  • Enable RIPng on an interface
  • Advertise connected networks
  • Confirm visibility of remote networks

This section presents an example configuration of RIPng. The configuration example is based on the reference diagram in the following figure. This example shows the configuration of the nodes by using dynamic IPv6 routing with RIPng to enable R3 and R4 to communicate through R1 and R2.

Figure 1. Dynamic IPv6 routing example in RIPng

Enabling forwarding on R1 and R2

For R1 to pass data between the dp0p1p1 and dp0p1p3 interfaces and R2 to pass data between the dp0p1p1 and dp0p1p2 interfaces, R1 and R2 must be configured to enable forwarding. To enable forwarding on R1, perform the following step in configuration mode.

Table 1. Enabling forwarding on R1
StepCommand
Enable forwarding on R1. 

vyatta@R1# delete system ipv6 disable-forwarding
Commit the change. 

vyatta@R1# commit

To enable forwarding on R2, perform the following steps in configuration mode.

Table 2. Enabling forwarding on R2
StepCommand
Enable forwarding on R2. 

vyatta@R2# delete system ipv6 disable-forwarding
Commit the change. 

vyatta@R2# commit

Enabling RIPng on an interface

To allow dynamic routing by using RIPng, RIPng must be enabled on the interfaces that are to use it. To enable RIPng on R1, perform the following steps in configuration mode.

Table 3. Enable RIPng on R1
Step Command
Enable RIPng on dp0p1p1. 

vyatta@R1# set interfaces dataplane dp0p1p1 ipv6 ripng enable
Enable RIPng on dp0p1p3. 

vyatta@R1# set interfaces dataplane dp0p1p3 ipv6 ripng enable
Commit the change. 

vyatta@R1# commit
Change to operational mode. 

vyatta@R1# exit
vyatta@R1:~$
Verify the status of RIPng. 

vyatta@R1:~$ show ipv6 ripng status 
  Routing Protocol is "RIPng"
    Sending updates every 30 seconds with +/-50%, next due in 4 seconds
    Timeout after 180 seconds, garbage collect after 120 seconds
    Outgoing update filter list for all interface is not set
    Incoming update filter list for all interface is not set
    Default redistribution metric is 1
    Redistributing:
  Interface
      dp0p1p1
      dp0p1p2
Display information for RIPng interfaces. 

vyatta@R1:~$ show ipv6 ripng interface 
dp0p1p1 is up, line protocol is up
  Routing Protocol: RIPng
    Passive interface: Disabled
    Split horizon: Enabled with Poisoned Reversed
    IPv6 interface address:
      fe80::5054:ff:fe8b:1/64
dp0p1p2 is up, line protocol is up
  Routing Protocol: RIPng
    Passive interface: Disabled
    Split horizon: Enabled with Poisoned Reversed
    IPv6 interface address:
      fe80::5054:ff:fe98:2/64

Advertising connected networks

The redistribute command is then used to advertise the connected networks. To advertise connected networks on R1, perform the following steps in configuration mode.

Table 4. Advertising connected networks on R1
Step Command

Advertise connected networks through RIPng.

 

vyatta@R1# set protocols ripng redistribute connected

Commit the change. 


vyatta@R1# commit

Verify the redistribution. 


vyatta@R1:~$ show ipv6 ripng status
Routing Protocol is "RIPng"
Sending updates every 30 seconds with +/-50%, next due in
4 seconds
Timeout after 180 seconds, garbage collect after 120 seconds
Outgoing update filter list for all interface is not set
Incoming update filter list for all interface is not set
Default redistribution metric is 1
Redistributing: connected
Interface
dp0p1p1
dp0p1p2

Confirming visibility of remote networks

After enabling RIPng on the other interfaces of R2, R3, and R4 and advertising connected networks on R2, check the routing table of R4 to verify that it has learned the network. To confirm visibility of remote networks on R4, perform the following step in operational mode.

Table 5. Confirming visibility of remote networks on R4
Step Command
Trace the route from R2 to R4. 

vyatta@R4:~$ show ipv6 route
IPv6 Routing Table
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
       IA - OSPF inter area, E1 - OSPF external type 1,
       E2 - OSPF external type 2, I - IS-IS, B - BGP
       > - selected route, * - FIB route, p - stale info
Timers: Uptime
S>* ::/0 [1/0] via 2001:db8:1::1, dp0s1
C>* ::1/128 is directly connected, lo
C>* 2001:db8:1::/64 is directly connected, dp0s1
R>* 2001:db8:2::/64 [120/2] via fe80::20c:29ff:fed6:816c,
dp0s1, 00:43:00
R>* 2001:db8:3::/64 [120/3] via fe80::20c:29ff:fed6:816c,
dp0s1, 00:00:03
C>* fe80::/64 is directly connected, dp0s1

The R in the first column indicates that two routes have been learned from RIPng. Because a route now exists for 2001:db8:3::/64, R3 can be pinged. To confirm connectivity, perform the following steps in operational mode.

Table 6. Confirming connectivity between R4 and R3
Step Command
Ping R3 from R4. 

vyatta@R4:~$ ping 2001:db8:3::3
PING 2001:db8:3::3(2001:db8:3::3) 56 data bytes
64 bytes from 2001:db8:3::3: icmp_seq=1 ttl=62 time=5.98 ms
64 bytes from 2001:db8:3::3: icmp_seq=2 ttl=62 time=0.603 ms
^C
--- 2001:db8:3::3 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1011ms
rtt min/avg/max/mdev = 0.603/3.294/5.986/2.692 ms
Display the RIPng status. 

vyatta@R4:~$ show ipv6 ripng
Codes: R - RIP, Rc - RIP connected, Rs - RIP static, Ra - RIP aggregated,
       Rcx - RIP connect suppressed, Rsx - RIP static suppressed,
       K - Kernel, C - Connected, S - Static, O - OSPF, I - IS-IS, B - BGP
   Network                     Next Hop                  If     Met Tag  Time
C  2001:db8:1::/64            ::                        dp0p1p1   1   0 
R  2001:db8:2::/64            2001:db8:1::1                        dp0p1p1   1   0 
R  2001:db8:3::/64            2001:db8:1::1                        dp0p1p1   1   0

Last updated: May 7, 2021