Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Static routes - why can I not ping??
Hi there,
I am trying to set up some static routes on three Cisco 3640 routers. I simply cannot get a working route which will allow me to ping remote interfaces.
Refer to the attached PNG file for a network diagram (just a basic three router setup at the moment)
Router configs :
R1
[output cut]
interface Ethernet0/0
ip address 172.100.20.1 255.255.0.0
half-duplex
!
interface Ethernet1/0
ip address 192.168.20.254 255.255.255.0
half-duplex
!
R2
[output cut]
interface Ethernet0/0
ip address 172.0.10.2 255.255.0.0
half-duplex
!
interface Ethernet1/0
ip address 172.100.20.2 255.255.0.0
half-duplex
!
R3
[output cut]
interface Ethernet0/0
ip address 192.168.10.254 255.255.255.0
half-duplex
!
interface Ethernet1/0
ip address 172.0.10.1 255.255.0.0
half-duplex
!
I want to put in static routes so R1 can ping every interface up to and including R3e0/0, and R3 can ping every interface up to and including R1e1/0.
Whenever I try, from say R1, I can get as far as pinging R2e0/0 but not e1/0 which is surely on the same network??
Many thanks - Cisco newbie :-)
STATIC2.png
I am trying to set up some static routes on three Cisco 3640 routers. I simply cannot get a working route which will allow me to ping remote interfaces.
Refer to the attached PNG file for a network diagram (just a basic three router setup at the moment)
Router configs :
R1
[output cut]
interface Ethernet0/0
ip address 172.100.20.1 255.255.0.0
half-duplex
!
interface Ethernet1/0
ip address 192.168.20.254 255.255.255.0
half-duplex
!
R2
[output cut]
interface Ethernet0/0
ip address 172.0.10.2 255.255.0.0
half-duplex
!
interface Ethernet1/0
ip address 172.100.20.2 255.255.0.0
half-duplex
!
R3
[output cut]
interface Ethernet0/0
ip address 192.168.10.254 255.255.255.0
half-duplex
!
interface Ethernet1/0
ip address 172.0.10.1 255.255.0.0
half-duplex
!
I want to put in static routes so R1 can ping every interface up to and including R3e0/0, and R3 can ping every interface up to and including R1e1/0.
Whenever I try, from say R1, I can get as far as pinging R2e0/0 but not e1/0 which is surely on the same network??
Many thanks - Cisco newbie :-)
STATIC2.png
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
you cant have two different interfaces on a router with IP address in the same range.
every interface needs to be in a different network, or routing will not work.
the only reason you can ping R2 from R1 is because a route is automatically created when you add the IP address.
What you need to do now, is add static routes for the remaining networks.
On R1, add static routes for all your networks and point them to the interface on R2 that you can ping.
On R2, add static routes for all the networks on R1 and point them to the interface you can ping on R1. Then add the remaining static routes, and point them to R3
every interface needs to be in a different network, or routing will not work.
the only reason you can ping R2 from R1 is because a route is automatically created when you add the IP address.
What you need to do now, is add static routes for the remaining networks.
On R1, add static routes for all your networks and point them to the interface on R2 that you can ping.
On R2, add static routes for all the networks on R1 and point them to the interface you can ping on R1. Then add the remaining static routes, and point them to R3
you cant have two different interfaces on a router with IP address in the same range.
every interface needs to be in a different network, or routing will not work.
except for directly connected interfaces. my bad.
every interface needs to be in a different network, or routing will not work.
except for directly connected interfaces. my bad.
Hey thanks for replying.
My understanding is that the 172.100.0.0/16 and the 172.0.0.0/16 are different networks on R2? Therefore shouldn't the routing work here? Ignoring the /24 stub networks, only R2 will do any routing if i ping a remote network from R1 and R3?
Could you demonstrate the commands with respect to the network here, or at least the routes needed for one of the routers?
Thanks again!
My understanding is that the 172.100.0.0/16 and the 172.0.0.0/16 are different networks on R2? Therefore shouldn't the routing work here? Ignoring the /24 stub networks, only R2 will do any routing if i ping a remote network from R1 and R3?
Could you demonstrate the commands with respect to the network here, or at least the routes needed for one of the routers?
Thanks again!
so, on R1, you need the following static routes
ip route 172.0.10.2 255.255.0.0 172.100.20.2
ip route 192.168.10.254 255.255.255.0 172.100.20.2
ip route 172.0.10.1 255.255.0.0 172.100.20.2
On R2, put in these static routes:
ip route 192.168.20.254 255.255.255.0 172.100.20.1
ip route 192.168.10.254 255.255.255.0 172.0.10.1
on R3, put in these static rotues:
ip route 172.100.20.2 255.255.0.0 172.0.10.2
ip route 192.168.20.254 255.255.255.0 172.0.10.2
ip route 172.100.20.1 255.255.0.0 172.0.10.2
ip route 172.0.10.2 255.255.0.0 172.100.20.2
ip route 192.168.10.254 255.255.255.0 172.100.20.2
ip route 172.0.10.1 255.255.0.0 172.100.20.2
On R2, put in these static routes:
ip route 192.168.20.254 255.255.255.0 172.100.20.1
ip route 192.168.10.254 255.255.255.0 172.0.10.1
on R3, put in these static rotues:
ip route 172.100.20.2 255.255.0.0 172.0.10.2
ip route 192.168.20.254 255.255.255.0 172.0.10.2
ip route 172.100.20.1 255.255.0.0 172.0.10.2
I am getting the same '%Inconsistent address and mask' error when i try and apply the 172.100.20.2 255.255.0.0 172.0.10.2 route on R3 and the 172.0.10.2 255.255.0.0 172.100.20.2 route on R1...
I have double-checked the config and all the ip's are as described. I am using GNS3 and a cisco 3640 image (c3640-io3-mz.123-26.image
I have double-checked the config and all the ip's are as described. I am using GNS3 and a cisco 3640 image (c3640-io3-mz.123-26.image
opps my bad. i forgot to change the the numbers to zeros when i copy/paste
try this:
ip route 172.0.0.0 255.255.0.0 172.100.20.2
ip route 192.168.10.0 255.255.255.0 172.100.20.2
ip route 172.0.0.0 255.255.0.0 172.100.20.2
On R2, put in these static routes:
ip route 192.168.20.0 255.255.255.0 172.100.20.1
ip route 192.168.10.0 255.255.255.0 172.0.10.1
on R3, put in these static rotues:
ip route 172.100.0.0 255.255.0.0 172.0.10.2
ip route 192.168.20.0 255.255.255.0 172.0.10.2
ip route 172.100.0.0 255.255.0.0 172.0.10.2
try this:
ip route 172.0.0.0 255.255.0.0 172.100.20.2
ip route 192.168.10.0 255.255.255.0 172.100.20.2
ip route 172.0.0.0 255.255.0.0 172.100.20.2
On R2, put in these static routes:
ip route 192.168.20.0 255.255.255.0 172.100.20.1
ip route 192.168.10.0 255.255.255.0 172.0.10.1
on R3, put in these static rotues:
ip route 172.100.0.0 255.255.0.0 172.0.10.2
ip route 192.168.20.0 255.255.255.0 172.0.10.2
ip route 172.100.0.0 255.255.0.0 172.0.10.2
Great stuff! Finally i can see the light.. I can use this to apply to other networks and hopefully it won't take me quite so long! Many thanks for your assistance with this :-)
Add the following routes to the indicated routers.
R1
ip route 172.0.0.0 255.255.0.0 172.100.20.2
ip route 192.168.10.0 255.255.255.0 172.100.20.2
R2
ip route 192.168.20.0 255.255.255.0 172.100.20.1
ip route 192.168.10.0 255.255.255.0 172.0.10.1
R3
ip route 172.100.0.0 255.255.0.0 172.0.10.2
ip route 192.168.20.0 255.255.255.0 172.0.10.2
Premium Content
You need an Expert Office subscription to comment.Start Free Trial