I have two routers set up as below: https://imgur.com/USLlHAQ The 10.0.0.1 and 10.0.1.2 networks are configured as loopback interfaces. Se0/1/0 on RouterA is configured with IP address 192.168.0.1 and Se0/2/0 on RouterB is configured with IP address 192.168.0.2. I have the current nat configuration (no default routes set): access-list 10 permit 10.0.0.0 0.0.255.255
ip nat pool mypool 192.168.0.1 192.168.0.254 netmask 255.255.0.0
ip nat inside source list 10 pool mypool I can issue a ping to destination 192.168.0.2 from source 10.0.1.2 successfully. I get "....." when issuing a ping to destination 192.168.0.1 from source 10.0.1.2: Sending 5, 100-byte ICMP Echos to 192.168.0.1, timeout is 2 seconds: Packet sent with a source address of 10.0.1.2 NAT: s=10.0.1.2->192.168.0.2, d=192.168.0.1  . NAT: s=10.0.1.2->192.168.0.2, d=192.168.0.1  . NAT: s=10.0.1.2->192.168.0.2, d=192.168.0.1  . NAT: s=10.0.1.2->192.168.0.2, d=192.168.0.1  . NAT: s=10.0.1.2->192.168.0.2, d=192.168.0.1  . Success rate is 0 percent (0/5) Can someone clarify what the series of steps are that is preventing a successful ping?
... View more
I set up Router0 with an extended ACL to permit telnet into loopback0 (172.20.0.1) on interface s0/1/0. I was originally able to telnet from Router1, then I tried to make some funky additions to my network and when I tried to telnet from Router1 afterwards I got "remote host not responding" message. Any ideas what the cause might be? I've tried: - shutting and no shutting the serial interfaces - removing the ACL from int s0/1/0 on Router0 - still did not allow telnet in (which would make sense if the ACL entry was correct) - severing the other two connections - verified the default route from Router1 is exiting int s0/1/0 Not sure what might be causing it?
... View more