cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
981
Views
5
Helpful
3
Replies

RIP, static routes, and frustration

artheyman
Level 1
Level 1

Two old routers (a 2500 and a 1600) , back to back with a serial cable (Dte Dce, & clocking all properly set)  with two Dlink VPN routers on either side of the routers and PC’s hung off those,

1) RIP did nothing ; should it have with just 2 routers ? I had to set static routes for any Pinging to work across the “network”

2) I noticed I could ping from a PC across the serial connection to the far router , and I could ping from a router into a far PC, but could not ping from a PC into a far PC; in other words the ping would work , but to make a physical analogy, in a kind of “overlapping” way.

3 Replies 3

Mahesh Gohil
Level 7
Level 7

Hi

Did you mean pc1-subnet1-dlink1-subnet2-cisco1--subnet3-cisco2-subnet4-dlink2-subnet5-pc2

Please verify at:

dlink1--for routes of subnet3,subnet4,subnet5
cisco1--for routes of subnet4,subnet5
cisco2--for routes of subnet2,subnet1,subnet5
dlink2- for routes of subnet1,subnet2,subnet3

you are not able to ping from pc-to-pc that means you are not having routes of subnet1 at pc2 and vice versa.

Either you put static routes at dlink1 or dlink2 for subnet1 and subnet5 or you can add that network in RIP.

Please remember If you put static routes you need to redistribute same in RIP (remember RIPv1 is classful protocol)

Hope this is helpful...you can share config for more clarity

Regards

Mahesh

Ganesh Hariharan
VIP Alumni
VIP Alumni

Two old routers (a 2500 and a 1600) , back to back with a serial cable (Dte Dce, & clocking all properly set)  with two Dlink VPN routers on either side of the routers and PC’s hung off those,

1) RIP did nothing ; should it have with just 2 routers ? I had to set static routes for any Pinging to work across the “network”

2) I noticed I could ping from a PC across the serial connection to the far router , and I could ping from a router into a far PC, but could not ping from a PC into a far PC; in other words the ping would work , but to make a physical analogy, in a kind of “overlapping” way.

Hi,

If i understand ur topology is something like this

PC1 -- R1 ---- R2 ---PC2 and your rip is not working, If yes then check it out the following thing PC1 and PC2 are in different subnets which are advertise in rip by both the routers.

R1 is R2 is connected interface is also particpating rip with both the routers are running same version of rip and disable auto summary in both the routers.

http://www.cisco.com/en/US/docs/ios/12_0/np1/configuration/guide/1crip.html#wp4549

Hope to Help !!

Ganesh.H

Remember to rate the helpful post

edwardhenry
Level 1
Level 1

To build on what was said previously, make sure you're running RIPv2.

Once using RIPv2, make sure ip classless is enabled and advertise the routes in RIP.

Example:

10.1.1.1

10.1.10.1

10.1.20.1

10.1.30.1

10.1.40.1

If you have these 5 subnets setup on two routers using RIPv2 and the ip classless enabled, RIP will avertise these routes over the serial interface as 10.0.0.0 - kind of makes for an easy and, for future use, scalable setup while using RIP. The sh ip route command will the show all learned routes and the router will still route according to the subnetting schema used.

Example output from router :

!
router rip
version 2
network 10.0.0.0
!

     10.0.0.0/24 is subnetted, 13 subnets
C       10.1.1.0 is directly connected, FastEthernet0/1.1
C       10.1.10.0 is directly connected, FastEthernet0/1.10
C       10.1.20.0 is directly connected, FastEthernet0/1.20
C       10.1.30.0 is directly connected, FastEthernet0/1.30
C       10.1.40.0 is directly connected, FastEthernet0/1.40
C       10.2.1.0 is directly connected, FastEthernet0/0
R       10.3.1.0 [120/1] via 10.2.1.2, 00:00:19, FastEthernet0/0
R       10.4.1.0 [120/2] via 10.2.1.2, 00:00:19, FastEthernet0/0
R       10.5.1.0 [120/3] via 10.2.1.2, 00:00:19, FastEthernet0/0
R       10.5.10.0 [120/3] via 10.2.1.2, 00:00:19, FastEthernet0/0
R       10.5.20.0 [120/3] via 10.2.1.2, 00:00:19, FastEthernet0/0
R       10.5.30.0 [120/3] via 10.2.1.2, 00:00:19, FastEthernet0/0
R       10.5.40.0 [120/3] via 10.2.1.2, 00:00:19, FastEthernet0/0

As you can see, RIP is operating as a classless address of 10.0.0.0 but populating it's routing table as the proper subnets.

I, also, am still relatively new to the cisco world of routing, I've been studying for my CCNA for a few weeks, but that should answer the general question you're asking.

Please if anyone else wants to jump in and correct me, I would appreciate it!

Thanks,
Ed

Review Cisco Networking products for a $25 gift card