Static Routing issue

phillip · ‎12-09-2007

Ok kind of lost here and been staring at it too long.

Router A:

FA0 ip address 192.168.2.1

ser0 ip address 10.10.10.2

ip route 0.0.0.0 0.0.0.0 10.10.10.1

Router B

FA0 ip address 192.168.1.3

ser0 ip address 10.10.10.1

ip route 0.0.0.0 0.0.0.0 192.168.1.2

ip route 192.168.2.0 10.10.10.2

Router c

FA0 ip address 192.168.1.2

ip route 0.0.0.0 0.0.0.0 192.168.1.1

ip route 192.168.2.0 192.168.1.3

pix

fa0 ip address 192.168.1.1

Router B C and Pix all connected at office via switch

Router B C and Pix all work fine see each other and route everything just fine

Router A connects via serial to Router B just fine, ethernet interfaces on A B see each other just fine.

Router A can not see Router C or Pix.

Any ideas, routes all look good..

Edison Ortiz · ‎12-09-2007

In order to get to the 192.168.2.x/24 network in RouterA, you need to traverse the serial IP subnet 10.10.10.x/30

You need a route in routerC and the PIX

ip route 10.10.10.0/30 192.168.1.3

Much easier when you let dynamic routing do it for you :)

Richard Burts · ‎12-10-2007

I believe that we need some clarification from Phillip about what the problem is. If the problem is attempting to access routerC and PIX from routerA itself, then the packets will be sourced from its serial interface by default and the solution to the problem is the route to 10.10.10.0/30 as Edison suggests (or the solution is to use extended ping, or traceroute, or specify the source interface for telnet, tftp, etc to be the Ethernet interface).

If the problem is attempting to access routerC or PIX from end stations on the Ethernet of routerA then the static route to 10.10.10.0/30 may or may not be required. If the static routes on routerC and the PIX for network 192.168.2.0 specify the serial interface on routerC as the next hop, then the static route is necessary. But if the static routes on routerC and the PIX specify the Ethernet of routerB as the next hop then routerC and the PIX do not need to know about the serial link or its address to access the 192.168.2.0 network. They only need to know that routerB can get to it.

I do note that the syntax given on routerC and the PIX for static routes is incorrect:

ip route 192.168.2.0 10.10.10.2

I assume that this is a typo for the forum posting rather than a cut and paste from the config. But if it were cut and paste from the config then the lack of a mask in the static route would be a syntax error.

HTH

Rick

HTH

Rick