So it's that time again for me to renew my Cisco Certifications. As a result, this post will is based on my preparation for the CCNP Route Exam (300-101).
In this post I will be focusing on Configuring and Verifying RIPng
- Interface e1/0 - connected to ISP1 - IPv6 2001::1/64
- Interface e1/1 - connected to ISP2 - IPv6 2002::1/64
- Interface lo3 - INTERNET ADDRESS - IPv6 2003::1/128
- Interface e1/0 - connected to ISP1 - IPv6 2001::2/64
- Interface e1/1 - connected to ISP2 - IP IPv6 2005::1/64
- Interface e1/0 - connected to ISP1 - IP IPv6 2002::1/64
- Interface e1/1 - connected to ISP2 - IP IPv6 2004::1/64
- Interface e1/0 - connected to ISP2 - IPv6 2004::2/64
- Interface e1/1 - connected to ISP1 - IPv6 2005::2/64
- Interface fa0/0 - connected to LAN - IPv6 200a::1/64
Kali Host on Local_site
eth0 - IPv6 200a::2/64
Default Gateway - IPv6 200a::1/64
Now that we have our topology in place, the first thing is to enable "ipv6 unicast-routing". This will need to be enabled on all routers in the topology.
Next, let's enable RIPng
Interface and RIPng Configuration:
In RIP version 1 and 2, to enable an interface to participate in the RIP network, we used the "network" command. In RIPng, RIP is enabled on the interface with "IPv6 rip" RIP Network "enable"
Let's verify the configuration from LOCAL_SITE perspective:
From the 2 diagrams above, we see that interfaces e1/0, e1/1 and Fa0/0 are participating in the RIP network. We also see in the additional RIP information.
From above, we see the list of routes learned via RIPng.
Let's see if our end system (kali) can reach the internet 2003::1/128
From the above, we see we can successfully trace from our Kali host internet 2003::1
From the above, we also see we can successfully ping from our Kali host to internet 2003::1. I will take the results of traceroute and ping to conclude that RIPng is working as expected.
Lastly, let's peek into the RIP packet.
Above, we see a RIPng packet containing the networks being advertised to the Internet Router.
That's all for RIPng!!