Tring to figure out static routing any help!!

longhorn79

I was able to configure everything right but I seem I cannot ping R2 from PC1 also can’t ping R1 from PC2.
I have been reading in the book and came up with static routing. The question I have I’m getting confused with the figuring out the ip route.
My Guess would be adding this line to the R1 routing table
ip route 192.168.2.2 255.255.255.0 serial 0/0
Would this allow me to ping R2 from PC1 and possibly to PC2.
I’m just getting my ears wet be kind, lol
Thanks

jamesleecoleman

Did you configure the default gateways of the computers?

dredlord

That is incorrect the static route should point towards the destination subnet in this case from R1 the destination subnet of pc2 would be 192.168.3.0 /24, there is no need for a static route for the 192.168.2.0 / 24 network since it is directly connected and hence already in the routing table. Also please note that one must configure a static route from R2 also in order to allow return traffic.

Correct config is as follows:

R1 - ip route 192.168.3.0 255.255.255.0 serial0/0/0
R2 - ip route 192.168.1.0 255.255.255.0 serial0/0/0

The above config would result in a ARP request for each packet sent on the WAN since the router would assume that the subnet is directly connected so for a performance stand point it is best to use the next hop IP address

R1 - ip route 192.168.3.0 255.255.255.0 192.168.2.2
R2 - ip route 192.168.1.0 255.255.255.0 192.168.2.1

dustinmurphy

Without seeing your running config, I would say the static routing statement(s) you will need are...

in R1
ip route 192.168.3.0 255.255.255.0 192.168.2.2


in R2
ip route 192.168.1.0 255.255.255.0 192.168.2.1

Both routers have to be aware of the outside network, or else it can't return the traffic.

The ip route statement is as follows: ip route <destination network> <netmask> <next hop interface address>

Edit: looks like I was too slow. LOL

angel.oa

R2 does not have a route to 192.168.1.0 so it discards the packet (PC2-->PC1) the same goes for R1 and route 192.168.3.0
The solution is create a static route in R1 to the subnet 192.168.3.0 and another one for R2 to the subnet 192.168.1.0

longhorn79

Thank very much to everyone. I was getting confused on the "next hop interface". Talk about fast responses great site!

dredlord

this document should explain the theory for static routing

Specifying a Next Hop IP Address for Static Routes - Cisco Systems

alxx

Section 6 – Configuring Static Routing
Free CCNA Workbook » Section 6 – Configuring Static Routing

drkat

Just by the discussion just remember we always route on destination (more on pbr later) however... if you remember we're always concerned on "how to get there" you should be able to figure it out.


Your first step in troubleshooting this would be to ping R1 from R2 and so forth and make sure your dhcp or static assignment includes the correct gateways.

show ip route 192.168.x.x will give you an idea on where packets "destined" for that subnet will be going also your traceroute will SHOW you where the last completed hop was so you can narrow that down.

for instance if our last completed hop was R2 then I'd go right to R2 and do a show ip route / show arp etc

NEXT HOP INTERFACE = WHERE WE'RE SENDING TRAFFIC DESTINED FOR THAT NETWORK - just remember it's all about where you're going.. not where you've been


best of luck