Can't see LAN

[tenover]

2 Routers, A and B.
From Router A, I can ping all interfaces AND remote network on the inside of Router B, and the internal (10.0.0.0)network inside router A.

From Router B, I can ping all interfaces on both routers, but NOT the internal network inside of RouterA.

Config:
Router A
eth0/0: 10.0.0.7/255.0.0.0
ser0/0: 192.168.5.1/255.255.255.252
ip route 0.0.0.0 0.0.0.0 10.0.0.1(our main router)
ip route 192.168.4.0 0.0.0.0 192.168.5.2

Router B
eth0/0: 192.168.4.1/255.255.255.0
ser0/0: 192.168.5.2/255.255.255.252
ip route 0.0.0.0 0.0.0.0 192.168.5.1

See anything wrong? Could it be a firewall issue??

 

[fynx]

The ip route statements for the opposing LAN contains incorrect mask.
In your example it should read...
RouterA:-
ip route 192.168.4.0 255.255.255.0 192.168.5.2

Good luck.
Phil.

 

[tenover]

Phil,
Thanks, that's actually what I have in the routing table, I just mis-typed it. I still can't ping any 10.0.0.0 address from router B except the 10.0.0.7 interface IP.....Any ideas? I'm banging my head against a wall here, because if I telnet into router A, I can ping ALL the 10.0.0.0 addresses. It seems to be getting stuck between Router A's ethernet interface and the rest of the LAN when trying from Router B only. ANY help is MUCH appreciated!

 

[wybnormal]

Lets see here.. you can ping from A to b and see 192.168.4.1? So the packet goes to A, sees the static route which directs it to the next hop of 192.168.5.2 which in turn gets the packets and sees that the .1 address is directly connected.. so far so good..

Going the other way, you ping 10.0.0.x? and the packet goes to out B since the route says any packet I dont know about goes to 192.168.5.1... 192.168.5.1 gets the packet and looks to see where for it go.. 10.0.0.7 directly connected so you should be able to ping .7 BUT everything else is routed to 10.0.0.1 as the next hop? If .7 doesnt have a route for it where does it go?

I dont like the idea of having a default route pointing to itself in a sense. You have packets hitting E0/0 and then being re-routed right back out to get to a different router on the same segment. I'm not sure off hand if that is your problem, but that is where I would start to look. I would also run a traceroute from B and see what the packet thinks is happing once it hits router A

Let us know any more info like the results from a traceroute

Mike S
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin

 

[tenover]

Thanks for all the help. It turns out that the routers were all configured properly, but there were no routes to the 192.168.4.0 and 192.168.5.0 networks in my firewall, so the packets were getting sent straight to the firewall(10.0.0.1), and from there didn't have any idea where to go....You learn something new everyday.