problem setting up rip

What is the output for show ip prot? Looks like a bug.

here is what i get from sh ip prot

router2#sh ip prot

Routing Protocol is "rip"
  Sending updates every 30 seconds, next due in 25 seconds
  Invalid after 180 seconds, hold down 180, flushed after 240
  Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Redistributing: rip
  Default version control: send version 1, receive any version
    Interface        Send  Recv   Key-chain
    Ethernet0        1     1 2
    Serial0          1     1 2
  Routing for Networks:
 172.16.20.0
Routing Information Sources:
Gateway        Distance         Last Update
172.16.20.2      120            00:00:03
Distance: (default is 120)

After "router rip" you also need "version 2", it's version 1 by default, and it will not send subnet mask information.

haven't gone that far yet, i believe thats part of the next lesson. but could that be related to whats going on here?

Yes, because you are using 172.16.x.x IP addresses, RIPv1 will use the default subnet mask of 255.255.0.0 for the two subnets, but in fact, your two subnets are 172.16.11.0 and 172.16.20.0 with mask of 255.255.255.0, in RIPv1, it will simply advertise the subnets in the network 172.16.0.0.

Do a 'no router rip' to clear your RIP settings, do a 'router rip' again, and then type 'version 2' and then type your network 172.16.11.0 and 172.16.20.0, actually, I think if you just type network 172.16.0.0, it will find your two subnets automatically.

Good luck.

when i do this i get the following:

router2(config)#router rip
router2(config-router)#version 2
                       ^

% Invalid input detected at '^' marker.

router2(config-router)#

That's really weird, I've never seen that before....let's try something else, in your interface configuration (both interfaces), try
"ip rip send version 1 2"

when i do this i get:

router2#copy run start
Building configuration...

[OK]
router2#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
router2(config)#int e0
router2(config-if)#ip rip send version 1 2
                      ^

% Invalid input detected at '^' marker.

wonder if its because the sim is messed up

oh my....I totally missed out the whole thing about "sybex virtual lab".....there should be a chart of features with your simulator, check to see if RIPv2 is there, if not, you will have to change your IP addresses to something else. 172.16.0.0 and 172.17.0.0 for example.

Unfortunately, that's the sad truth with simulators, they just don't cut it sometimes...geez, it's just RIPv2 we're talking about...I'm glad I spent the extra dough on real hardware.

i plan on scoping ebay shortly when i have some money, its amazing how much 9 month old kids cost these days lol...

bighornsheep wrote:

Yes, because you are using 172.16.x.x IP addresses, RIPv1 will use the default subnet mask of 255.255.0.0 for the two subnets, but in fact, your two subnets are 172.16.11.0 and 172.16.20.0 with mask of 255.255.255.0, in RIPv1, it will simply advertise the subnets in the network 172.16.0.0.

Do a 'no router rip' to clear your RIP settings, do a 'router rip' again, and then type 'version 2' and then type your network 172.16.11.0 and 172.16.20.0, actually, I think if you just type network 172.16.0.0, it will find your two subnets automatically.

Good luck.

RIPv1 will only auto summarize at another major classful network boundry. Meaning he can use 255.255.255.0 for his networks and they will not be auto summarized as long as he continues to use 172.16.0.0 as the major classful network. When he begins to implement another network like 172.15.0.0, then 172.16.20.0 will summarize to 172.16.0.0. So i do not think RIPv1 is the problem. The recieving router that recieves the routing update will assume that each major network has the same subnet mask in the update as it's local interface. This "assuming behavior" is caused from not sending a subnet mask. as long as he uses /24 across the entire network of 172.16.0.0, he should be fine.

So having said that, I still think it is a bug because you should be routing for the other network and it should be in your running-config.

dtlokee

Netstudent wrote:

bighornsheep wrote:

Yes, because you are using 172.16.x.x IP addresses, RIPv1 will use the default subnet mask of 255.255.0.0 for the two subnets, but in fact, your two subnets are 172.16.11.0 and 172.16.20.0 with mask of 255.255.255.0, in RIPv1, it will simply advertise the subnets in the network 172.16.0.0.

Do a 'no router rip' to clear your RIP settings, do a 'router rip' again, and then type 'version 2' and then type your network 172.16.11.0 and 172.16.20.0, actually, I think if you just type network 172.16.0.0, it will find your two subnets automatically.

Good luck.

RIPv1 will only auto summarize at another major classful network boundry. Meaning he can use 255.255.255.0 for his networks and they will not be auto summarized as long as he continues to use 172.16.0.0 as the major classful network. When he begins to implement another network like 172.15.0.0, then 172.16.20.0 will summarize to 172.16.0.0. So i do not think RIPv1 is the problem. The recieving router that recieves the routing update will assume that each major network has the same subnet mask in the update as it's local interface. This "assuming behavior" is caused from not sending a subnet mask. as long as he uses /24 across the entire network of 172.16.0.0, he should be fine.

So having said that, I still think it is a bug because you should be routing for the other network and it should be in your running-config.

Bah, bad Netstudent

The network command for RIP is always classful, if you type in "network 172.16.10.0" it will become "network 172.16.0.0" in the running config. If you did "network 172.16.10.0" and "network 172.16.20.0" in since they are both subents of the same classful network they bouth truncate to "network 172.16.0.0" hence the output in you see.

Well maybe I'm thinking of the actual routing updates then. So truncation and auto-summarization are two different things. I was referring to auto-summarization behavior on the network. Maybe I'm just flat out wrong.

hopefully not!

I realize he should have done network 172.16.0.0, but I still do not see the truncated classful network in the running-config.

dtlokee

Auto summary is only done when the router is going to advertise a subnet of one classful network out an interface that has an address in a different classful network, like 172.16.20.0/24 advertised out an interface with the IP 192.168.100.1 would result in the router advertising 172.16.0.0/16 instead of the 172.16.20.0/24 subnet

Well thats kinda what I was trying to get across.

ok, can i get a cisco newbie explanation on what yall are talkin about... lol.

What i'm getting out of this is that i should be using a /16 (default for class b) mask instead of the /24 mask that the sybex book has me doin?

GregD

sprinkl3s wrote:

ok, can i get a cisco newbie explanation on what yall are talkin about... lol.

What i'm getting out of this is that i should be using a /16 (default for class b) mask instead of the /24 mask that the sybex book has me doin?

It looks like the simulator is bugged. It should show network 172.16.0.0 in the running config - not 172.16.20.0

As dtlokee said, the network command in rip is classful - meaning if you type in network 172.16.whatever.whatever, it should truncate it to 172.16.0.0 - and would, on a real router. For some reason, according to the sh run you posted, it has 172.16.20.0 as the network.

Try typing in network 172.16.0.0 in the rip config and see what happens.