I configured EIGRP in R1 and R2 , but for some reason I cannot ping from R1 to 192.168.23.3, even though there is an EIGRP route in R1 for 192.168.23.0
1#sh run | sec eigrprouter eigrp 1 network 192.168.12.0R1#
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.23.3, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
R1#
FRom R2 I can ping:
R2#ping 192.168.23.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.23.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/19/24 ms
R2# Screen-Shot-2017-11-09-at-8.38.50-PM.png
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
Unlimited question asking, solutions, articles and more.
jskfan
ASKER
without the NAT:
on R1:
ip route 0.0.0.0 0.0.0.0 192.168.12.2
on R2 I configured:
ip route 0.0.0.0 0.0.0.0 192.168.23.3
on ISP:
ip route 192.168.12.0 255.255.255.0 192.168.23.2
I believe NAT is used just in case you want some Networks on R1 and R2 to access ISP and not all Networks
in my case I used the command below to route everything
ip route 0.0.0.0 0.0.0.0 192.168.12.2
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
R1#sh ip route eigrp
D* 0.0.0.0/0 [90/30720] via 192.168.12.2, 00:06:03, FastEthernet0/0
D 192.168.23.0/24 [90/30720] via 192.168.12.2, 00:06:03, FastEthernet0/0
R1#