Everyone can access the server 192.168.1.3 from outside using the PUblic IP address but when people VPN in and try to access 192.168.1.3 using the private IP address, it doesn't work. Here's the NAT ACL
ip access-list extended NATACL
deny ip 192.168.1.0 0.0.0.255 192.168.2.0 0.0.0.255
One question from the above configuration. The address of the LO interface .253 But when we set next-hop 10.254.254.254. Where does this .254 come from
Good question :) , i will try to answer. when we set next hop as 10.254.254.254 (it does not exist anywhere) but this makes the traffic to exit out of Loopback interface where there is no "ip nat outside " configured. Another good argument can be why we did not configure " set interface loopback0" why next-hop ? when you configure set interface , the traffic does not exit out of loopback interface .
I am sure somebody here can explain it better than me.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...