SOHO RIPv2 redistribution to OSPF on Cisco 2900

Unanswered Question
Jul 28th, 2012
User Badges:

Hi,


I am having a problem reaching a soho linksys e1000 router through a second hop cisco 2900 router.


Here is a brief topology of the network: I am using OSPF area 100 for all networks except for 192.168.2.0 on R1 to E1000 which is RIPv2

R1 directly connects to R2 with a point-to-point serial on network 192.168.12.0 /30 with ip 192.168.1.13

R1 directly connects to a a switchport using network 192.168.2.0 /24 with ip 192.168.1.75

R3 directly connects to a switchport using network 192.168.1.128.0 /25 with ip 192.168.1.129

R3 directly connects to a different cisco router using ethernet on network 192.168.1.0 with ip 192.168.1.1

E1000 directly connects to a switchport using network 192.168.2.0 /24 with ip 192.168.2.1

The switch has a vlan ip on 192.168.1.128 /25


I can ping from R1 to E1000

I can ping from R3 to R1 192.168.2.75


I can't ping from R3 to E1000 192.168.2.1


show ip route on R2 indicates that network 192.168.2.0 is reachable via the serial connection on 192.168.1.12


I have redistributed rip to ospf area 100 and OSPF to RIP on R1


I am wondering why R1 can reach E1000 on network 192.168.2.0, and why R3 can reach R1s 192.168.2.0 newtork, but R3 can't reach the E1000.



There is an R2 router than can reach R1 and also cannot reach E1000, but I assume it's for the same reasons R3 can't, so I've ommitted the remainder of that topology for this question.


Thanks for any insight!

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
John Blakley Sat, 07/28/2012 - 09:04
User Badges:
  • Purple, 4500 points or more

When you're redistributing from ospf to rip, you need to make sure that you have a metric specified. Under the rip process, make sure that you have:


router rip

redistribute ospf 100 metric 2


HTH,

John

orthostaticindi... Sat, 07/28/2012 - 12:59
User Badges:

here are the processes I have setup:


router ospf 100

redistribute rip metric 2

network 10.1.1.1 0.0.0.0 area 0

network 192.168.1.8 0.0.0.3 area 0

network 192.168.1.12 0.0.0.3 area 0

!

router rip

version 2

redistribute ospf 100 metric 2

network 192.168.2.0


I am still able to reach the E1000 on router 1, but not through router 3.


Also, here is the routing table for router 3



10.0.0.0/32 is subnetted, 3 subnets

O       10.1.1.2 [110/2] via 192.168.1.2, 00:03:12, FastEthernet0/1

C       10.1.1.3 is directly connected, Loopback0

O       10.1.1.1 [110/65] via 192.168.1.9, 00:03:12, Serial0/0

192.168.1.0/24 is variably subnetted, 4 subnets, 2 masks

C       192.168.1.8/30 is directly connected, Serial0/0

O       192.168.1.12/30 [110/128] via 192.168.1.9, 00:03:12, Serial0/0

C       192.168.1.0/30 is directly connected, FastEthernet0/1

C       192.168.1.128/25 is directly connected, FastEthernet0/0

O    192.168.2.0/24 [110/74] via 192.168.1.9, 00:03:12, Serial0/0

John Blakley Sun, 07/29/2012 - 06:06
User Badges:
  • Purple, 4500 points or more

What does the other routing table say? The bigger issue I think that may be going on is that you've set version 2 on this router. This will restrict to send/receive only version 2 whereas if your other router (E1000) only supports, or is hard set to version 1, it won't see the other routes. You could try to set this to version 1 to see if that resolves the issue for you. (or the better option would be to enable version 2 on the E1000 if it supports it.)



router rip

version 1


HTH,

John

orthostaticindi... Sun, 07/29/2012 - 17:19
User Badges:

Well, after running debug ip rip, I discovered that no rip updates are being sent over the ethernet link between the e1000 and R1. After reading up further on dd-wrt, I've found that it needs to be set to gateway if that router manages my wan. I setup a couple of static routes and now all the routers can ping each other, but I'll have to statically mange anything off of the e1000 or set it to RIPv2.


I'm not too thrilled with the limited support and documentation with the dd-wrt firmware. It's a fantastic project, and I am sure with more experience and in-depth knowledge of linux, I could navigate the CLI and figure out what my e1000 capabilities are.


Thanks for the suggestions, I should have been running the debug a long time ago.

Actions

This Discussion