Routing Help!

Hi
First post on this forum so hopefully someone can help me out? I'm studying for the CCENT at the moment and I've set up a small home lab. Ive attached the configuration on here.
Ive got one problem I'm encountering. I know its something really simple, but maybe Ive just been at it too long. Everythings set up fine and all devices can ping each other fine...except router 3.

On router 3 I can ping router 2 fine, but nothing else, it cant see past router 2. Ive set up RIP 2 on both routers. Think Ive got some kind of mental block! Not sure what to do from here!!

Thanks in advance

Rob

home_lab(1).jpg

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

xbuzz

Hey, without seeing the running-config or some show commands the best guess I could make would be that maybe you haven't entered 192.168.0.0 subnet to be advertised with RIP. When you configure RIP, you need to specify which networks you want to advertise on the router they are connected to. To do this, when you are setting up rip you would entered the address with the network 192.168.0.0 command from the rip configuration interface i.e.

configure terminal
router rip
version 2
network 192.168.0.0
network 192.168.1.0

Hope that helps.

oli356

The 'broadband router' has thrown me..

If that router was just a normal router like the other 2 (I'm calling it R1), once you've configured RIP v2 with network 192.168.0.0 if you do a show ip route

C    192.168.0.0/24 is directly connected, FastEthernet0/0
R    192.168.1.0/24 [120/1] via 192.168.0.8, 00:00:13, FastEthernet0/0

From R2

C    192.168.0.0/24 is directly connected, FastEthernet0/0
C    192.168.1.0/24 is directly connected, Serial0/0/0

From R3

R    192.168.0.0/24 [120/1] via 192.168.1.100, 00:00:08, Serial0/0/0
C    192.168.1.0/24 is directly connected, Serial0/0/0

Without the routing protocol being on R1 there is nothing more R3 could get to.. It can get to R2 as its directly connected. R2 can get to the PC as its connected, though the PCs default gateway is R1. Unless R1 is advertising its network and therefore learning about the 192.168.1.0 network (R3), the PC can't access anything apart from R1 and R2 (192.168.0.8 )

robsellars

Thanks a lot. Router 1 is just my router I got from my ISP A Sagemcomm one. So thatll probably be why. No ability to set up routing on it? The rest are all cisco gear.

mella060

Have you set up routing on R3 ? Routing is a two-way street so it needs to be set up on both R2 and R3. Each router needs to advertise its directly connected networks, so R2 would advertise networks 192.168.0.0 and 192.168.1.0

Since R3 is only directly connected to the network 192.168.1.0 it only needs to advertise that network.

The configs for R2 and R3 might look like the following

R2

configure terminal
router rip
version 2
network 192.168.0.0
network 192.168.1.0

R3

configure terminal
router rip
version 2
network 192.168.1.0

Zartanasaurus

R3 can see past R2 just fine I'm guessing (assuming you are running RIP or something between them). It's the things past R2 that likely don't have a return path to R3. R3 knows how to get to the PC's IP, but the PC doesn't know how to get to R3 because it's default is pointing towards your internet router.

Zartanasaurus

Go to a command line and add this to your Windows box:

route add 192.168.1.0 mask 255.255.255.0 192.168.0.8 metric 1 -p

robsellars

Getting further i think. I used the route add line and got the below response.

C:\Windows\system32>route add 192.168.1.0 mask 255.255.255.0 192.168.0.8 metric
1 -p
OK!

C:\Windows\system32>ping 192.168.1.2

Pinging 192.168.1.2 with 32 bytes of data:
Reply from 192.168.1.101: TTL expired in transit.
Reply from 192.168.1.101: TTL expired in transit.
Reply from 192.168.1.101: TTL expired in transit.
Reply from 192.168.1.101: TTL expired in transit.

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Windows\system32>

robsellars

Seems to go in a bit of a loop actually, when I use tracert

C:\Windows\system32>tracert 192.168.1.2

Tracing route to 192.168.1.2 over a maximum of 30 hops

1 1 ms 1 ms 1 ms (null) [192.168.0.8]
2 1 ms 1 ms 1 ms 192.168.1.101
3 1 ms 1 ms 1 ms 192.168.1.1
4 2 ms 2 ms 2 ms 192.168.1.101
5 2 ms 2 ms 2 ms 192.168.1.1
6 3 ms 3 ms 3 ms 192.168.1.101
7 3 ms 3 ms 3 ms ^C

robsellars

Heres a few results of show commands too.

Router 3 IP ROUTE

Gateway of last resort is not set

R 192.168.0.0/24 [120/1] via 192.168.1.1, 00:00:21, Serial0/0
C 192.168.1.0/24 is directly connected, Serial0/0
router3#

Router 2 IP ROUTE

Gateway of last resort is not set

C 192.168.0.0/24 is directly connected, Ethernet0/0
C 192.168.1.0/24 is directly connected, Serial0/1

Zartanasaurus

What's 192.168.1.2? I don't see it on your diagram.

robsellars

sorry! I was playing about with it yesterday and changed the IP on the serial link. on R2 serial 0/1 = 192.168.1.1 on R3 serial 0/0= 192.168.1.2