Lab 10 - RIP
From SOFTICE
(diff) ←Older revision | Current revision | Newer revision→ (diff)
|
Pedagogical Objectives
- Review routing and classful and classless addressing
- Enable dynamic routing through the Routing Information Protocol (RIP)
- Capture and analyze RIP traffic
Developed by:
Synopsis
Routing is the process by which networking traffic is directed to its final destination through the use of OSI Model Layer 3 information. In the previous lab, we implemented static (manually configured) routing. In this lab, we will use the Routing Information Protocol (RIP). RIP is a vendor-neutral routing protocol that can be used to enable routers to share topological information with each other, and ultimately find routes without human intervention. Routers share this information by exchanging packets.
[Briefing]
RIP is a distance vector routing protocol. What this means is that each router transmits its entire routing table to each of its neighbors. Neighbors are defined as routers which have interfaces on the same subnet. In transmitting these routing tables, RIP version 1 omits all subnet mask information. Therefore, RIP version 1 is a classful routing protocol. RIP version 2 corrects this deficiency, and is therefore considered to be a classless routing protocol. In this lab, we examine both version of RIP.
[Solved]
Complete the following solved exercises, recording your findings, and the procedures used to obtain them in your log. By doing this, you may be able to obtain partial credit if you are unable to complete any of the exercises.
Note: Before disconnecting from SOFTICE, be sure to shut your virtual hosts down. This procedure is described in Exercise 1-3: Shutdown the Network. This must be done in order to conserve system resources on the SOFTICE cluster.
[Solved] 10-1: Enable RIP
Enable RIP on the lakeland host.
1. The Two Locations Network has already been assigned IP addresses. Use the unedited twoLocations.mln file located in your mln/mln_files directory to build the Two Locations Network, then start it up:
mln build -f mln/mln_files/twoLocations.mln mln start -p twoLocations
2. Login to the lakeland host, then set the router configuration environment's password to usf:
cd /etc/quagga echo "password usf" > ripd.conf echo "password usf" > zebra.conf
3. Edit the /etc/quagga/daemons file, updating the following lines:
zebra=yes ripd=yes
4. Set RIP to startup when the system boots:
update-rc.d -f quagga defaults
5. Reboot to make the changes that you've just made take effect:
reboot
[Solved] 10-2: Configure RIP
Configure the lakeland host to use RIP version 1, and advertise all directly connected subnets.
1. Telnet into the lakeland host's router configuration environment. When prompted for a password, enter usf:
lakeland:~# telnet localhost ripd Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Hello, this is Quagga (version 0.98.3). Copyright 1996-2005 Kunihiro Ishiguro, et al. User Access Verification Password: lakeland>
2. Enter privileged mode. This mode enables you to manipulate the router, and it required to enter terminal configuration mode:
lakeland> enable lakeland#
3. Enter terminal configuration mode. This allows you to make configuration changes to the router, and is required to enter RIP configuration mode:
lakeland# conf t lakeland(config)#
4. Enter RIP configuration mode:
lakeland(config)# router rip lakeland(config-router)#
5. Instruct the router to use RIP version 1:
lakeland(config-router)# version 1
6. Instruct the router to advertise both of the networks that it is connected to:
lakeland(config-router)# network 10.0.0.0/24 lakeland(config-router)# network 10.0.3.0/24
7. Return to privileged mode:
lakeland(config-router)# exit lakeland(config)# exit lakeland#
8. Save your changes. If you skip this setup, your changes will be lost the next time this router is rebooted:
lakeland# copy run start
9. Exit the lakeland host's router configuration environment:
lakeland# exit
[Exercises]
Complete the following exercises, recording your findings, and the procedures used to obtain them in your log.
Note: Before disconnecting from SOFTICE, be sure to shut your virtual hosts down. This procedure is described in Exercise 1-3: Shutdown the Network. This must be done in order to conserve system resources on the SOFTICE cluster.
Exercise 10-1: Intercept RIP Version 1
1. Start tcpdump on the tampa host to intercept RIP traffic originating from the lakeland host. You may want to consult tcpdump's man page by running the man tcpdump command on any of the Two Locations Network's hosts:
man tcpdump
2. After you've enabled tcpdump, and see RIP packets being logged, reboot the lakeland host. Continue to run tcpdump for a few minutes after the lakeland host comes back up:
reboot
2. At what regular interval does RIP send out packets? Is there more than one type of packet being sent out?
4. Paste an example RIP version 1 packet captured by tcpdump into your log. What information does tcpdump reveal about the captured packet?
Exercise 10-2: Intercept RIP Version 2
1. Modify the lakeland host's RIP's configuration so that it runs RIP version 2 (hint: take a look at Solved Exercise 10-2 and change one detail).
2. Start tcpdump on the tampa host to intercept RIP traffic originating from the lakeland host.
3. Paste an example RIP version 2 packet captured by tcpdump into your log. What information does tcpdump reveal about the captured packet? How does this differ from the information you extracted from a captured RIP version 1 packet earlier?
Exercise 10-2: Extra Credit: RIP Packet Destination Addresses
1. Compare the destination addresses of the RIP version 1 and 2 packets you captured, and recorded in your log in the previous exercises. Explain what type of address each packet is addressed to, and why you believe this difference exists. What advantage and disadvantage do each of these types of addresses offer?
