28.06.2014 Views

Learning by Doing: CISCO Certified Network ... - SCN Research

Learning by Doing: CISCO Certified Network ... - SCN Research

Learning by Doing: CISCO Certified Network ... - SCN Research

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Protocol Deathmatch: RIP versus RIPv2<br />

Objectives:<br />

To be able to discern between RIP and RIPv2 and when to use each. (A good review of<br />

part 2)<br />

Lab Design:<br />

Workstation “A”<br />

Router name: robert morris worm<br />

Workstation “B”<br />

Step-<strong>by</strong>-Step Instructions for RIP:<br />

1. Set up the network shown using a 24-bit mask with a Class “C” private address using<br />

RIP as the routing protocol. Don’t forget to advertise the routes.<br />

2. Test ping from workstation A to workstation B.<br />

3. Do a trace route from workstation A to workstation B.<br />

4. On each router view and record its routing table.<br />

5. Turn on all debug on Robert and Worm.<br />

6. Test ping from workstation A to workstation B and view the ICMP messages on<br />

Robert and Worm.<br />

7. Change the serial lines to a 30-bit mask. (hint: the IP numbers will also need to be<br />

changed).<br />

8. Repeat steps 2-6. About 60% of the time you will not be able to ping from<br />

workstation A to workstation B. A known quirk with RIP. Don’t sweat it if it works.<br />

9. Switch to using RIP version 2 on all routers.<br />

10. Repeat steps 2-6. So why do you think it works with RIPv2 and not RIP? Why or<br />

when would you use RIPv2 instead of RIP? Why or when would you use RIP instead<br />

of RIPv2?<br />

Guest Router Name Derivation<br />

In 1991 Robert Morris became the first individual convicted for violating the 1986<br />

Federal Computer Fraud and Abuse Act. He created an internet worm as part of a<br />

graduate school project whose sole purpose was to expose security vulnerabilities in<br />

networks so that network administrators could pro-actively fix any security holes.<br />

Unfortunately the project went amiss and computer networks crashed left and right when<br />

it was released errantly on the Internet. In hind-sight he should have kept it a little better<br />

under control. It just goes to show you that good intentions also get punished…<br />

“ignorance of the law is no excuse.”<br />

283

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!