Considering the below network, I am trying to accomplish the communication in green arrows for the request (telnet on port 80) and orange for the reply from the server. Router R1 should NAT communication as indicated by the source (S) and destination (D) labels below the green arrow. I've posted relevant parts of R1's config that should NAT the source and destination of the packet. Yet, when packet exits R1 toward the web server packet is still sourced from 192.168.0.1 although it should be "NATted" and sourced by Ge0's address IP (10.0.0.1). Problem is that as the server sees packet from 192.168.0.1 instead of 10.0.0.1 it does not send it back to R1.
I've posted an output of a debug ip nat on R1 which shows that source isn't translated and also a show ip accces-list which shows that ACL 1 never matches.
Main constraint is that configurations of R2 and WS1 cannot be changed.
Note : routers are running IOS 150-1
I am wondering what I am missing in R1's config that will translate packet's source IP address. Any help would be appreciated.
Listen: https://smarturl.it/CCRS9E25 Follow us: twitter.com/ciscochampions
With applications and users everywhere, the networks are now, more than ever, being tasked with delivering consistent protection while providing an exceptional user exper...
Listen: https://smarturl.it/CCRS9E24 Follow us: https://twitter.com/CiscoChampion
Cisco Radio Aware Routing addresses several of the challenges faced when merging IP routing and radio communications in mobile networks, especially those exhibiti...
Listen: https://smarturl.it/CCRS9E23 Follow us: https://twitter.com/CiscoChampion The Wi-Fi 6E Catalyst 9136 access point takes advantage of the 6-GHz band to produce a network that is more reliable and secure, with higher throughput, more ...
When moving from OSPFv2 to OSPFv3, there are many changes in the format of the LSAs Type, but the most known changes are: IP prefix informations are no longer carried in Type-1 LSA and Type-2 LSA, new LSAs Type 8 and 9 are added to carry these prefixes.