Need some network help....

[jmcoreymv]

Well Ive been playing with this router simulator software and this is one thing I cant figure out and Im probably making a stupid mistake. Anyways, heres the visualization window of the network.
http://www.crosswinds.net/~jmcoreymv/labsetup.htm
As you can see, ive set the ip addresses on the relevant network interfaces, and Ive configured igrp routing on all of them using the same AS number. Anyways, if im at host A, i can ping all interfaces up to s0 of routerB. I can ping s0 of routerB but anything past that like, e0 or s1 or anything else is unreachable and im not sure how to fix it. Take a look, advice appreciated.

 

[jmcoreymv]

Hears the IP routing table of RouterA

[cut]
172.16.0.0/24 is subnetted, 6 subnets
I currentip [120/2] via 172.16.20.2, 00:00:12, Serial0
I 172.16.40.0 [120/2] via 172.16.20.2, 00:00:12, Serial0
I 172.16.30.0 [120/2] via 172.16.20.2, 00:00:12, Serial0
I 172.16.40.0 [120/2] via 172.16.20.2, 00:00:12, Serial0
C 172.16.20.0 is directly connected, Serial0
C 172.16.10.0 is directly connected, Ethernet0
[cut]
And yes I did set the clock rate on the two serial links, im sure because I can ping s0 of RouterB

 

[jmcoreymv]

Also if Im on host B, i can ping every interface on the network, including host a.

 

[bhuie]

What does the routing table on router B look like?

 

[jmcoreymv]

Heres Router B's table
[cut]
172.16.0.0/24 is subnetted, 7 subnets
I currentip [120/1] via 172.16.40.2, 00:00:14, Serial1
I currentip [120/1] via 172.16.40.2, 00:00:14, Serial1
I 172.16.10.0 [120/1] via 172.16.20.1, 00:00:01, Serial0
C 172.16.40.0 is directly connected, Serial1
C 172.16.30.0 is directly connected, Ethernet0
C 172.16.20.0 is directly connected, Serial0
I 172.16.20.0 [120/1] via 172.16.20.1, 00:00:01, Serial0

 

[bhuie]

Well, whatever it is, I don't see it either. I can't imagine why you wouldn't even be able to ping the s1 interface of router B if you could ping s0. What kind of routers are they supposed to be? If they're Cisco routers and this program has a simulated CLI for each one, I might be able to spot something in the configs.

 

[jmcoreymv]

They are cisco routers with a CLI. What do you want me to copy off them?

 

[bhuie]

Can you copy a "show running-config" from each of them. I can't promise anything, but maybe I can spot something.

 

[jmcoreymv]

Heres RouterA:

RouterA#sh run
Building configuration...
Current configuration:
!
version 11.3
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname RouterA
!
enable secret tQVrYunKsPoL
!
!
interface Ethernet0
ip address 172.16.10.1 255.255.255.0
!
interface Serial0
ip address 172.16.20.1 255.255.255.0
!
!
interface Serial1
ip address 172.16.40.1 255.255.255.0
shutdown
!
interfac e TokenRing0
no ip address
!
shutdown
router igrp 10
network 172.16.0.0
!
no ip classless
ip route 172.16.20.0 255.255.255.0 172.16.10.1
banner login ^C
Dont Mess wit mah router foo.
^C
!
line con 0
password xxxxx
line aux 0
line vty 0 4
password xxxxx
login
!
end



Heres RouterB:

RouterB#sh run
Building configuration...
Current configuration:
!
version 11.3
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname RouterB
!
!
!
!
interface Ethernet0
ip address 172.16.30.1 255.255.255.0
!
interface Serial0
ip address 172.16.20.2 255.255.255.0
!
clockrate 56000
!
!
interface Serial1
ip address 172.16.40.1 255.255.255.0
clockrat e 56000
!
router igrp 10
network 172.16.0.0
!
no ip classless
!
line con 0
line aux 0
line vty 0 4
end



Hope that tells something.

 

[bhuie]

The only thing that looks out of place is the static route you have configured on router A. It's trying to send all traffic destined to 172.16.20.* to the interfece that contains 172.16.10.1 (eth0). I'm not sure what effect that would have when it conflicts with what IGRP says. Did you try taking that line out?

 

[CTR]

Are you still having trouble? Like bhuie said, take out that static route on router A.

The reason you can ping ser0 on routerB but not past is that ser0 on routerB falls under the trivial connected route from routerA. Connected route is always preferred over static.

Hope that helps.