IPv6 Dynamic Routing Using RIPng

 

Experiment: IPv6 Dynamic Routing Using RIPng

1. Aim

To configure and implement RIPng (Routing Information Protocol next generation) for dynamic routing between two IPv6 networks using Cisco Packet Tracer and verify end-to-end IPv6 connectivity.

2. Objectives

After completing this experiment, students will be able to:

  1. Configure IPv6 addresses on routers and PCs.
  2. Enable IPv6 packet forwarding on Cisco routers.
  3. Configure RIPng on Cisco routers.
  4. Enable RIPng on appropriate router interfaces.
  5. Understand how RIPng dynamically learns remote IPv6 networks.
  6. Verify RIPng routes in the IPv6 routing table.
  7. Test connectivity using ping and tracert.
  8. Compare dynamic routing with the static routing experiment performed previously.

3. Background / Theory

What is RIPng?

RIPng (RIP Next Generation) is the IPv6 version of RIP used for dynamic routing.

RIPng allows routers to automatically exchange information about IPv6 networks rather than requiring the administrator to manually configure routes.

For example, consider:

PC0 ─ Switch0 ─ R0 ───── R1 ───── Switch1 ─ PC1
                  IPv6       IPv6

R0 initially knows only about its directly connected networks.

R1 initially knows only about its directly connected networks.

After RIPng is enabled, the routers exchange routing information:

R0  ←──────── RIPng ────────→  R1

R0 learns the network behind R1, and R1 learns the network behind R0.

4. Important Difference Between RIP and RIPng

Students should note an important configuration difference.

For IPv4 RIP:

router rip
version 2
network 192.168.1.0

For IPv6 RIPng, we do not use:

router rip

Instead, we create a RIPng process:

ipv6 router rip COLLEGE

and then enable it on each required interface:

ipv6 rip COLLEGE enable

So the basic RIPng configuration is:

ipv6 router rip COLLEGE

followed by:

interface ...
ipv6 rip COLLEGE enable

5. Network Topology

We will use a topology very similar to the IPv6 static-routing experiment.

                         IPv6 Network
                       2001:DB8:3::/64
                              |
                              |
                           G0/0
                         ┌───────┐
                         │   R0  │
                         └───┬───┘
                             |
                       S0/0/0
                             |
                 2001:DB8:10::/64
                             |
                       S0/0/0
                         ┌───┴───┐
                         │   R1  │
                         └───┬───┘
                           G0/0
                             |
                             |
                      2001:DB8:4::/64
                             |
                          Switch1
                             |
                            PC1

Complete physical topology:

 PC0                                      PC1
  |                                        |
  |                                        |
Switch0                                  Switch1
  |                                        |
  |                                        |
 G0/0                                    G0/0
  |                                        |
  R0 ----------- Serial Link ------------- R1
                2001:DB8:10::/64

6. Devices Required

DeviceQuantity
Cisco 2901/2911 Router    2
Cisco 2960 Switch    2
PC-PT    2
Copper Straight-Through Cable    4
Serial DCE/DTE Cable    1

7. IPv6 Addressing Scheme

We will use three IPv6 networks.

Network    Purpose
2001:DB8:3::/64    LAN 1
2001:DB8:10::/64R0–R1 link
2001:DB8:4::/64LAN 2

Addressing Table

DeviceInterfaceIPv6 AddressPrefix
PC0NIC2001:DB8:3::10/64
R0G0/02001:DB8:3::1/64
R0S0/0/02001:DB8:10::1/64
R1S0/0/02001:DB8:10::2/64
R1G0/02001:DB8:4::1/64
PC1NIC2001:DB8:4::10/64

PC Default Gateways

PC0:

2001:DB8:3::1

PC1:

2001:DB8:4::1

8. Important Difference from the Static Routing Experiment

In the previous experiment, we manually configured:

R0

ipv6 route 2001:DB8:4::/64 2001:DB8:10::2

R1

ipv6 route 2001:DB8:3::/64 2001:DB8:10::1

For this experiment, do not configure these static routes.

Instead, RIPng will dynamically learn the remote networks.

The students should therefore start with only directly connected routes and then observe how RIPng adds the remote routes.

9. Create the Topology in Packet Tracer

Task 1 – Place the devices

Place:

  • 2 × Cisco 2901/2911 routers
  • 2 × Cisco 2960 switches
  • 2 × PCs

Arrange:

PC0 → Switch0 → R0 → R1 → Switch1 → PC1

10. Connect the Devices

Use copper straight-through cables for the LAN connections.

LAN 1

PC0 FastEthernet0
        |
        |
Switch0
        |
        |
R0 G0/0

LAN 2

R1 G0/0
        |
        |
Switch1
        |
        |
PC1 FastEthernet0

Router-to-router link

Use a serial cable:

R0 S0/0/0 -------- S0/0/0 R1

Depending on the router model, Packet Tracer may show a slightly different serial interface number.

11. Configure PC0

Go to:

PC0 → Desktop → IP Configuration

Enter:

IPv6 Address:
2001:DB8:3::10

Prefix Length:
64

Default Gateway:
2001:DB8:3::1

12. Configure PC1

Go to:

PC1 → Desktop → IP Configuration

Enter:

IPv6 Address:
2001:DB8:4::10

Prefix Length:
64

Default Gateway:
2001:DB8:4::1

13. Configure Router R0

Open:

R0 → CLI

Enter:

enable
configure terminal

Task 2 – Enable IPv6 routing

ipv6 unicast-routing

Task 3 – Configure G0/0

interface gigabitEthernet 0/0
ipv6 address 2001:DB8:3::1/64
no shutdown
exit

Task 4 – Configure the serial interface

interface serial 0/0/0
ipv6 address 2001:DB8:10::1/64
no shutdown
exit

If R0 is the DCE side, configure:

clock rate 64000

So the configuration may be:

interface serial 0/0/0
ipv6 address 2001:DB8:10::1/64
clock rate 64000
no shutdown
exit

14. Configure Router R1

Open:

R1 → CLI

Enter:

enable
configure terminal

Task 5 – Enable IPv6 routing

ipv6 unicast-routing

Task 6 – Configure the serial interface

interface serial 0/0/0
ipv6 address 2001:DB8:10::2/64
no shutdown
exit

Do not configure clock rate here if R0 is the DCE side.

Task 7 – Configure G0/0

interface gigabitEthernet 0/0
ipv6 address 2001:DB8:4::1/64
no shutdown
exit

15. Verify the Basic IPv6 Configuration

On R0:

show ipv6 interface brief

Expected:

G0/0       2001:DB8:3::1
S0/0/0     2001:DB8:10::1

On R1:

show ipv6 interface brief

Expected:

S0/0/0     2001:DB8:10::2
G0/0       2001:DB8:4::1

Make sure the interfaces show:

up/up

16. Test the Router-to-Router Connection

From R0:

ping 2001:DB8:10::2

Expected:

Success rate is 100 percent

From R1:

ping 2001:DB8:10::1

17. Examine the Routing Table Before RIPng

This is an important teaching step.

On R0:

show ipv6 route

R0 should know about:

C 2001:DB8:3::/64
C 2001:DB8:10::/64

It should not yet know:

2001:DB8:4::/64

Similarly, R1 should know:

C 2001:DB8:4::/64
C 2001:DB8:10::/64

but not:

2001:DB8:3::/64

18. Configure RIPng on R0

Now we configure dynamic routing.

Go to R0.

enable
configure terminal

Task 8 – Create the RIPng process

Enter:

ipv6 router rip COLLEGE

Here:

COLLEGE

is simply the RIPng process name.

You can use another name, for example:

ipv6 router rip RIPNG1

The name must be used consistently on the interfaces of that router.

Exit:

exit

19. Enable RIPng on R0 Interfaces

RIPng is enabled on interfaces, unlike the IPv4 RIP configuration students may have seen earlier.

Enable RIPng on R0 G0/0

interface gigabitEthernet 0/0
ipv6 rip COLLEGE enable
exit

Enable RIPng on R0 Serial Interface

interface serial 0/0/0
ipv6 rip COLLEGE enable
exit

Return to privileged mode:

end

20. Configure RIPng on R1

Go to R1.

enable
configure terminal

Task 9 – Create the RIPng process

ipv6 router rip COLLEGE

Exit:

exit

21. Enable RIPng on R1 Interfaces

R1 Serial interface

interface serial 0/0/0
ipv6 rip COLLEGE enable
exit

R1 G0/0

interface gigabitEthernet 0/0
ipv6 rip COLLEGE enable
exit

Exit:

end

Save:

copy running-config startup-config

22. Complete RIPng Configuration – R0

For student reference:

enable
configure terminal

ipv6 unicast-routing

interface gigabitEthernet 0/0
ipv6 address 2001:DB8:3::1/64
ipv6 rip COLLEGE enable
no shutdown
exit

interface serial 0/0/0
ipv6 address 2001:DB8:10::1/64
ipv6 rip COLLEGE enable
clock rate 64000
no shutdown
exit

ipv6 router rip COLLEGE

end
copy running-config startup-config

23. Complete RIPng Configuration – R1

enable
configure terminal

ipv6 unicast-routing

interface serial 0/0/0
ipv6 address 2001:DB8:10::2/64
ipv6 rip COLLEGE enable
no shutdown
exit

interface gigabitEthernet 0/0
ipv6 address 2001:DB8:4::1/64
ipv6 rip COLLEGE enable
no shutdown
exit

ipv6 router rip COLLEGE

end
copy running-config startup-config

The RIPng process does not require network statements. The important command is ipv6 rip COLLEGE enable under each interface participating in RIPng.

24. Wait for RIPng to Converge

Allow a few seconds for the routers to exchange routing information.

Then check R0:

show ipv6 route

You should now see something similar to:

C   2001:DB8:3::/64
C   2001:DB8:10::/64
R   2001:DB8:4::/64

The important entry is:

R   2001:DB8:4::/64

where:

R = RIP

This means that R0 learned the network dynamically through RIPng.

25. Check R1

On R1:

show ipv6 route

You should see:

C   2001:DB8:4::/64
C   2001:DB8:10::/64
R   2001:DB8:3::/64

Therefore:

R1 learned 2001:DB8:3::/64 through RIPng.

26. Verify RIPng Configuration

Use:

show ipv6 protocols

This should display information about the RIPng process.

You can also use:

show ipv6 route rip

This displays routes learned through RIPng.

For R0, you should see:

R 2001:DB8:4::/64

For R1:

R 2001:DB8:3::/64

27. Test PC0 → PC1

Now go to:

PC0 → Desktop → Command Prompt

Enter:

ping 2001:DB8:4::10

Expected:

Reply from 2001:DB8:4::10

The path is:

PC0
  ↓
Switch0
  ↓
R0
  ↓
R1
  ↓
Switch1
  ↓
PC1

28. Test PC1 → PC0

From PC1:

ping 2001:DB8:3::10

Expected:

Reply from 2001:DB8:3::10

This confirms that RIPng has provided routes in both directions.

29. Trace the IPv6 Path

From PC0:

tracert 2001:DB8:4::10

You should see the packet passing through:

PC0
 ↓
R0
 ↓
R1
 ↓
PC1

30. Verify RIPng Using Routing Table

This is an important observation for students.

Before RIPng

R0:

C 2001:DB8:3::/64
C 2001:DB8:10::/64

After RIPng

R0:

C 2001:DB8:3::/64
C 2001:DB8:10::/64
R 2001:DB8:4::/64

Similarly:

Before RIPng

R1:

C 2001:DB8:4::/64
C 2001:DB8:10::/64

After RIPng

R1:

C 2001:DB8:4::/64
C 2001:DB8:10::/64
R 2001:DB8:3::/64

This makes the purpose of dynamic routing very clear.

31. Important RIPng Concept

RIPng uses hop count as its routing metric.

For example:

PC0 → R0 → R1 → PC1

There is one router-to-router hop between the two networks.

RIPng can use the hop count to determine the route.

The maximum hop count in RIP/RIPng is:

15

A metric of:

16

represents an unreachable network.

Therefore, RIPng is intended for relatively small networks.

32. Static Routing vs RIPng

This experiment is a good follow-up to the previous static-routing experiment.

FeatureStatic IPv6 RoutingRIPng
Route configurationManual    Automatic
Administrator specifies routesYes    No
Uses routing protocolNo    Yes
Automatically learns remote networksNo    Yes
Route metricAdministrative configuration    Hop count
Adaptation to topology changesManual    Automatic
Configuration complexitySimple for small networks    Useful as network grows
Routing table entryS        R

The key observation for students is:

Static routing:
S 2001:DB8:4::/64

RIPng:
R 2001:DB8:4::/64

33. Observation Table

Students can record their results:

Sl. No.TestCommandExpected Result
1R0 → R1    ping 2001:DB8:10::2    Successful
2PC0 → R0    ping 2001:DB8:3::1    Successful
3PC1 → R1    ping 2001:DB8:4::1    Successful
4R0 routing table    show ipv6 route    RIPng route appears
5R1 routing table    show ipv6 route    RIPng route appears
6PC0 → PC1    ping 2001:DB8:4::10    Successful
7PC1 → PC0    ping 2001:DB8:3::10    Successful
8PC0 → PC1    tracert 2001:DB8:4::10    R0 → R1 → PC1

34. Troubleshooting

Problem 1: RIPng route is not appearing

Check:

show ipv6 route

Then verify RIPng is enabled on the interfaces:

show ipv6 protocols

Also verify:

interface gigabitEthernet 0/0
ipv6 rip COLLEGE enable

and:

interface serial 0/0/0
ipv6 rip COLLEGE enable

Problem 2: R0 and R1 cannot communicate

Check:

show ipv6 interface brief

Verify:

R0 S0/0/0 = 2001:DB8:10::1/64
R1 S0/0/0 = 2001:DB8:10::2/64

Check the serial interface status.

If R0 is DCE:

interface serial 0/0/0
clock rate 64000

Problem 3: PC0 can reach R0 but not PC1

Check R0:

show ipv6 route

You should have:

R 2001:DB8:4::/64

If it is missing, check that RIPng is enabled on the R0 serial interface.

Problem 4: PC1 can reach R1 but not PC0

Check R1:

show ipv6 route

You should have:

R 2001:DB8:3::/64

35. Useful Commands

CommandPurpose
show ipv6 interface brief    Displays IPv6 addresses and interface status
show ipv6 route    Displays IPv6 routing table
show ipv6 route rip    Displays RIPng-learned routes
show ipv6 protocols    Displays IPv6 routing protocol information
show running-config    Displays current configuration
ping <IPv6 address>    Tests connectivity
tracert <IPv6 address>    Traces the path from a PC
ipv6 router rip COLLEGE    Creates RIPng process
ipv6 rip COLLEGE enable    Enables RIPng on an interface

36. Result

The IPv6 network consisting of two LANs connected through two routers was successfully configured in Cisco Packet Tracer. IPv6 addresses were assigned to the hosts and router interfaces, IPv6 forwarding was enabled, RIPng was configured on the participating interfaces, and the routers dynamically learned the remote IPv6 networks. End-to-end communication between PC0 and PC1 was successfully verified using ping and tracert.

Comments

Post a Comment

Popular posts from this blog

Networks Lab PCCSL507 Semester 5 KTU CS 2024 Scheme - Dr Binu V P

 About Me   Dr Binu V P Syllabus Networks lab PCCSL507 KTU 2024 scheme Learn Linux well before you start- refer blog Build a strong understanding of the theory before moving on to programming Experiments Familiarize Linux networking commands ifconfig ifplugstatus iftop ping ip traceroute mtr netstat whois nmap nmcli speedtest-cli bmon nslookup tcpdump Wireshark     Download Wireshark     Wireshark Documentaion     Setting up a capture     Capturing Live network data      Analysis of HTTP Protocol using Wireshark      Analysis of SMTP Protocol Using Wireshark      Analysis of DNS Protocol Using Wireshark Socket Programming Basic Implementation of  TCP Client Server Communication using sockets. TCP Client-Server Communication to Identify Matrix Type (Upper/Lower/Diagonal) Implementation of UDP Client-Server Communication using Sockets in C UDP Client-Server Communication for Translating “N...
Read more

Study of whois Command

   Experiment Study of whois Command 🎯 Aim To retrieve domain registration and ownership information using the whois command. 📘 Objective By the end of this experiment, students will be able to: Query domain registration details Identify domain owner and registrar Find domain creation and expiry dates Understand public domain database records 📖 Theory The whois command is used to: Fetch information about domain names and IP addresses Query public databases maintained by domain registrars 👉 It provides details such as: Domain owner (if not private) Registrar name Registration and expiry dates Name servers 👉 It works using the WHOIS protocol (TCP port 43) . 🧾 Syntax whois <domain_or_ip> 🔧 Common Usage Query a domain: whois google.com Query an IP address: whois 8.8.8.8 🧰 Prerequisites Linux system Internet connectivity whois package installed Installation: sudo apt install whois 🔬 Procedure ...
Read more

Study and Use of ifconfig Command

   Experiment  Study and Use of ifconfig Command 🎯 Aim To familiarize students with the ifconfig command in Linux for viewing and configuring network interfaces. 📘 Objective By the end of this experiment, students will be able to: Display network interface details Enable/disable network interfaces Assign IP addresses manually Understand key networking parameters 🧰 Prerequisites Linux system (e.g., Ubuntu/Debian/Kali) Basic terminal knowledge Root or sudo privileges 📖 Theory The ifconfig ( interface configuration ) command is used to: View network interface configuration Assign IP addresses Enable or disable interfaces ⚠️ Note: On modern systems, ifconfig is deprecated and replaced by the ip command (from iproute2 ), but it is still widely used for learning and legacy systems. 🧾 Syntax ifconfig [interface] [options] interface → Network interface name (e.g., eth0 , wlan0 ) options → Actions like up, down, assigning...
Read more