Within this article we will look at the two ways in which to NAT traffic.
Source NAT Pool
This examples provides the commands required to configure source NAT via the use of a pool and ACL. This allows you to source NAT a number of internal hosts behind the ADX to a single IP address.
Here we will NAT the servers 10.1.1.1 and 10.1.1.2 to the source IP address 192.168.1.100 (when traffic from these servers is sent out through the load-balancer on port tcp/80).
access-list 150 permit tcp host 10.1.1.1 any eq 80
access-list 150 permit tcp host 10.1.1.2 any eq 80
ip nat pool SNAT 192.168.1.100 192.168.1.100 netmask 255.255.255.255
ip nat inside source list 150 pool SNAT overload
ip nat outside
ip nat inside
Another common scenario that is required (to ensure that traffic is routed back through the ADX) when either configuring remote servers or internal load-balancing is to configure server source NAT.
This ensures that any traffic from the ADX to the real server is source NAT`d behind the egress interface of the ADX.
server real RS-10.1.1.1 10.1.1.1
- How to Configure a BIND Server on Ubuntu - March 15, 2018
- What is a BGP Confederation? - March 6, 2018
- Cisco – What is BGP ORF (Outbound Route Filtering)? - March 5, 2018
Want to become a networking expert?
Here is our hand-picked selection of the best courses you can find online:
Cisco CCNA 200-301 Certification Gold Bootcamp
Complete Cyber Security Course – Network Security
Internet Security Deep Dive course
Python Pro Bootcamp
and our recommended certification practice exams:
AlphaPrep Practice Tests - Free Trial