NAT Types

Configuring NAT for IP Address Conservation
This module describes how to configure Network Address Translation (NAT) for IP address conservation
and how to configure inside and outside source addresses. This module also provides information about the
benefits of configuring NAT for IP address conservation.
NAT enables private IP internetworks that use nonregistered IP addresses to connect to the Internet. NAT
operates on a device, usually connecting two networks, and translates the private (not globally unique)
addresses in the internal network into legal addresses before packets are forwarded onto another network.
NAT can be configured to advertise to the outside world only one address for the entire network. This ability
provides additional security by effectively hiding the entire internal network behind that one address.
NAT is also used at the enterprise edge to allow internal users access to the Internet and to allow Internet
access to internal devices such as mail servers.
Finding Feature Information, page 1

Prerequisites for Configuring NAT for IP Address Conservation, page 2
Restrictions for Configuring NAT for IP Address Conservation, page 2
Information About Configuring NAT for IP Address Conservation, page 4
How to Configure NAT for IP Address Conservation, page 12
Configuration Examples for Configuring NAT for IP Address Conservation, page 39
Where to Go Next, page 43
Additional References for Configuring NAT for IP Address Conservation, page 44
Feature Information for Configuring NAT for IP Address Conservation, page 45
Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and
feature information, see Bug Search Tool and the release notes for your platform and software release. To
find information about the features documented in this module, and to see a list of the releases in which each
feature is supported, see the feature information table.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

1
Prerequisites for Configuring NAT for IP Address Conservation
Prerequisites for Configuring NAT for IP Address Conservation
Access Lists
All access lists that are required for use with the configuration tasks described in this module should be
configured before beginning a configuration task. For information about how to configure an access list, see
the IP Access List EntrySequence Numbering document.
Note If you specify an access list with a NAT command, NAT will not support the permit ip any any command
that is commonly used in an access list.
NAT Requirements
Before configuring NAT in your network, you should know the interfaces on which NAT will be configured
and for what purposes. The following requirements will help you decide how to configure and use NAT:
Define the NAT inside and outside interfaces if:
Users exist off multiple interfaces.
Multiple interfaces connect to the Internet.
Define what you need NAT to accomplish:

Allow internal users to access the Internet.
Allow the Internet to access internal devices such as a mail server.
Allow overlapping networks to communicate.
Allow networks with different address schemes to communicate.
Allow the use of an application level gateway.
Redirect TCP traffic to another TCP port or address.
Use NAT during a network transition.
From Cisco IOS XE Denali 16.3 release, NAT support is introduced on Bridge Domain Interface (BDI) for
enabling NAT configuration on BDI interface.
Restrictions for Configuring NAT for IP Address Conservation

When you configure Network Address Translation (NAT) on an interface, that interface becomes
optimized for NAT packet flow. Any nontranslated packet that flows through the NAT interface goes
through a series of checks to determine whether the packet needs to be translated or not. These checks
result in increased latency for nontranslated packet flows and thus negatively impact the packet processing

2
Restrictions for Configuring NAT for IP Address Conservation
latency of all packet flows through the NAT interface. We highly recommend that a NAT interface must
be used only for NAT-only traffic. Any non-NAT packets must be separated and these packets should
go through an interface that does not have NAT configured on it. You can use Policy-Based Routing
(PBR) for separating non-NAT traffic.
NAT Virtual Interfaces (NVIs) are not supported in the Cisco IOS XE software.
NAT is not practical if large numbers of hosts in the stub domain communicate outside of the domain.
Some applications use embedded IP addresses in such a way that translation by a NAT device is
impractical. These applications may not work transparently or at all through a NAT device.
In a NAT configuration, addresses configured for any inside mapping should not be configured for any
outside mapping.
Do not configure the interface IP address as part of the IP address NAT pool.
By default, support for the Session Initiation Protocol (SIP) is enabled on port 5060. Therefore,
NAT-enabled devices interpret all packets on this port as SIP call messages. If other applications in the
system use port 5060 to send packets, the NAT service may corrupt the packet as it attempts to interpret
the packet as a SIP call message.
NAT hides the identity of hosts, which may be an advantage or a disadvantage depending on the desired
result.
A device configured with NAT must not advertise the local networks to outside the network. However,
routing information that NAT receives from the outside can be advertised in the stub domain as usual.
If you specify an access list to use with a NAT command, NAT does not support the permit ip any any
command that is commonly used in the access list.
An access list with a port range is not supported on the Cisco ASR 1000 Series Aggregation Services
Routers.
NAT configuration is not supported on the access side of the Intelligent Services Gateway (ISG).
Using any IP address configured of a device as an address pool or in a NAT static rule is not supported.
NAT can share the physical interface address (not any other IP address) of a device only by using the
NAT interface overload configuration. A device uses the ports of its physical interface and NAT must
receive communication about the ports that it can safely use for translation. This communication happens
only when the NAT interface overload is configured.
The output of the show ip nat statistics command displays information about all IP address pools and
NAT mappings that you have configured. If your NAT configuration has a high number of IP address
pools and NAT mappings (for example 1000 to 4000), the update rate of the pool and mapping statistics
in the show ip nat statistics is very slow.
Static and dynamic NAT with generic generic routing encapsulation (generic GRE) and dynamic NAT
with Layer 2 do not work when used along with hardware-based Cisco AppNav appliances (for example,
Wide Area Application Services [WAAS]). In the context of WAAS, generic GRE is an out-of-path
deployment mechanism that helps to return packets from the WAAS Wide-Area Application Engine
(WAE) through the GRE tunnel to the same device from which they were originally redirected, after
completing optimization.
Port Address Translation (also called NAT overload) only supports protocols whose port numbers are
known; these protocols are Internet Control Message Protocol (ICMP), TCP, and UDP. Other protocols
do not work with PAT because they consume the entire address in an address pool. Configure your

3
Information About Configuring NAT for IP Address Conservation
access control list to only permit ICMP, TCP, and UDP protocols, so that all other protocol traffic is
prevented from entering the network.
NAT, Zone-Based Policy Firewall, and Web Cache Communication Protocol (WCCP) cannot coexist
in a network.
Information About Configuring NAT for IP Address Conservation
Benefits of Configuring NAT for IP Address Conservation

NAT allows organizations to resolve the problem of IP address depletion when they have existing networks
and need to access the Internet. Sites that do not yet possess Network Information Center (NIC)-registered
IP addresses must acquire them, and if more than 254 clients are present or planned, the scarcity of Class B
addresses becomes a serious issue. Cisco IOS XE NAT addresses these issues by mapping thousands of hidden
internal addresses to a range of easy-to-get Class C addresses.
Sites that already have registered IP addresses for clients on an internal network may want to hide those
addresses from the Internet so that hackers cannot directly attack the clients. With client addresses hidden, a
degree of security is established. Cisco IOS XE NAT gives LAN administrators complete freedom to expand
Class A addressing, which is drawn from the reserve pool of the Internet Assigned Numbers Authority (RFC
1597). This expansion occurs within the organization without concern for addressing changes at the
LAN/Internet interface.
The Cisco IOS XE software can selectively or dynamically perform NAT. This flexibility allows the network
administrator to use a mix of RFC 1597 and RFC 1918 addresses or registered addresses. NAT is designed
for use on a variety of devices for IP address simplification and conservation. In addition, Cisco IOS XE NAT
allows the selection of internal hosts that are available for NAT.
A significant advantage of NAT is that it can be configured without requiring changes to hosts or devices
other than those few devices on which NAT is configured.
In Cisco IOS XE Denali 16.3 release, Multi-Tenant support for NAT feature was introduced. With Multi-Tenant
support for NAT feature, the configuration changes of a Virtual Routing and Forwarding (VRF) instance does
not interrupt the traffic flow of other VRFs in the network.
NAT is a feature that allows the IP network of an organization to appear from the outside to a use different
IP address space than what it actually uses. Thus, NAT allows an organization with nonglobally routable
addresses to connect to the Internet by translating those addresses into a globally routable address space. NAT
also allows a graceful renumbering strategy for organizations that are changing service providers or voluntarily
renumbering into classless interdomain routing (CIDR) blocks. NAT is described in RFC 1631.
How NAT Works

A device that is configured with NAT will have at least one interface to the inside network and one to the
outside network. In a typical environment, NAT is configured at the exit device between a stub domain and
the backbone. When a packet leaves the domain, NAT translates the locally significant source address into a
globally unique address. When a packet enters the domain, NAT translates the globally unique destination
address into a local address. If more than one exit point exists, each NAT must have the same translation table.
If NAT cannot allocate an address because it has run out of addresses, it drops the packet and sends an Internet
Control Message Protocol (ICMP) host unreachable packet to the destination.

4
Uses of NAT
Uses of NAT
NAT can be used for the following scenarios:
To connect to the Internet, but not all of your hosts have globally unique IP addresses. Network Address
Translation (NAT) enables private IP internetworks that use nonregistered IP addresses to connect to
the Internet. NAT is configured on a device at the border of a stub domain (referred to as the inside
network) and a public network such as the Internet (referred to as the outside network). NAT translates
internal local addresses to globally unique IP addresses before sending packets to the outside network.
As a solution to the connectivity problem, NAT is practical only when relatively few hosts in a stub
domain communicate outside of the domain at the same time. When this is the case, only a small subset
of the IP addresses in the domain must be translated into globally unique IP addresses when outside
communication is necessary, and these addresses can be reused when they are no longer in use.
Change your internal addresses. Instead of changing the internal addresses, which can be a considerable
amount of work, you can translate them by using NAT.
For basic load-sharing of TCP traffic. You can map a single global IP address to many local IP addresses
by using the TCP Load Distribution feature.
Types of NAT
NAT operates on a routergenerally connecting only two networksand translates the private (inside local)
addresses within the internal network into public (inside global) addresses before any packets are forwarded
to another network. This functionality gives you the option to configure NAT so that it will advertise only a
single address for your entire network to the outside world. Doing this effectively hides the internal network
from the world, giving you some additional security.
The types of NAT include:
Static address translation (static NAT)Allows one-to-one mapping between local and global addresses.
Dynamic address translation (dynamic NAT)Maps unregistered IP addresses to registered IP addresses
from a pool of registered IP addresses.
OverloadingMaps multiple unregistered IP addresses to a single registered IP address (many to one)
using different ports. This method is also known as Port Address Translation (PAT). By using overloading,
thousands of users can be connected to the Internet by using only one real global IP address.
NAT Inside and Outside Addresses

The term inside in a Network Address Translation (NAT) context refers to networks owned by an organization
that must be translated. When NAT is configured, hosts within this network will have addresses in one space
(known as the local address space) that will appear to those outside the network as being in another space
(known as the global address space).
Similarly, the term outside refers to those networks to which the stub network connects, and which are generally
not under the control of an organization. Hosts in outside networks can also be subject to translation, and can
thus have local and global addresses.
NAT uses the following definitions:

5
Inside local addressAn IP address that is assigned to a host on the inside network. The address is
probably not a legitimate IP address assigned by the Network Information Center (NIC) or service
provider.
Inside global addressA legitimate IP address (assigned by the NIC or service provider) that represents
one or more inside local IP addresses to the outside world.
Outside local addressThe IP address of an outside host as it appears to the inside network. Not
necessarily a legitimate address, it is allocated from the address space that is routable on the inside.
Outside global addressThe IP address assigned to a host on the outside network by the owner of the
host. The address is allocated from a globally routable address or network space.
This section describes the following topics:

Inside Source Address Translation, on page 6
Overloading of Inside Global Addresses, on page 7
Inside Source Address Translation

You can translate IP addresses into globally unique IP addresses when communicating outside of your network.
You can configure static or dynamic inside source address translation as follows:
Static translation establishes a one-to-one mapping between the inside local address and an inside global
address. Static translation is useful when a host on the inside must be accessible by a fixed address from
the outside.
Dynamic translation establishes a mapping between an inside local address and a pool of global addresses.
The figure below illustrates a device that is translating a source address inside a network to a source address
outside the network.
Figure 1: NAT Inside Source Translation

6
The following process describes the inside source address translation, as shown in the figure above:
1 The user at host 10.1.1.1 opens a connection to Host B in the outside network.
2 The first packet that the device receives from host 10.1.1.1 causes the device to check its Network Address
Translation (NAT) table. Based on the NAT configuration, the following scenarios are possible:
If a static translation entry is configured, the device goes to Step 3.
If no translation entry exists, the device determines that the source address (SA) 10.1.1.1 must be
translated dynamically, selects a legal, global address from the dynamic address pool, and creates a
translation entry in the NAT table. This type of translation entry is called a simple entry.
3 The device replaces the inside local source address of host 10.1.1.1 with the global address of the translation
entry and forwards the packet.
4 Host B receives the packet and responds to host 10.1.1.1 by using the inside global IP destination address
(DA) 203.0.113.2.
5 When the device receives the packet with the inside global IP address, it performs a NAT table lookup by
using the inside global address as a key. It then translates the address to the inside local address of host
10.1.1.1 and forwards the packet to host 10.1.1.1.
Host 10.1.1.1 receives the packet and continues the conversation. The device performs Steps 2 to 5 for each
packet that it receives.
Overloading of Inside Global Addresses

You can conserve addresses in the inside global address pool by allowing a device to use one global address
for many local addresses and this type of Network Address Translation (NAT) configuration is called
overloading. When overloading is configured, the device maintains enough information from higher-level
protocols (for example, TCP or UDP port numbers) to translate the global address back to the correct local
address. When multiple local addresses map to one global address, the TCP or UDP port numbers of each
inside host distinguish between local addresses.

7
The figure below illustrates a NAT operation when an inside global address represents multiple inside local
addresses. The TCP port numbers act as differentiators.
Figure 2: NAT Overloading Inside Global Addresses
The device performs the following process in the overloading of inside global addresses, as shown in the
figure above. Both Host B and Host C believe that they are communicating with a single host at address
203.0.113.2. Where as, they are actually communicating with different hosts; the port number is the
differentiator. In fact, many inside hosts can share the inside global IP address by using many port numbers.
1 The user at host 10.1.1.1 opens a connection to Host B.
2 The first packet that the device receives from host 10.1.1.1 causes the device to check its NAT table. Based
on your NAT configuration the following scenarios are possible:
If no translation entry exists, the device determines that IP address 10.1.1.1 must be translated, and
translates inside local address 10.1.1.1 to a legal global address.
If overloading is enabled and another translation is active, the device reuses the global address from
that translation and saves enough information that can be used to translate the global address back,
as an entry in the NAT table. This type of translation entry is called an extended entry.
3 The device replaces inside local source address 10.1.1.1 with the selected global address and forwards the
packet.
4 Host B receives the packet and responds to host 10.1.1.1 by using the inside global IP address 203.0.113.2.
5 When the device receives the packet with the inside global IP address, it performs a NAT table lookup by
using a protocol, the inside global address and port, and the outside address and port as keys; translates
the address to the inside local address 10.1.1.1 and forwards the packet to host 10.1.1.1.
Host 10.1.1.1 receives the packet and continues the conversation. The device performs Steps 2 to 5 for each
packet it receives.

8
Address Translation of Overlapping Networks
Address Translation of Overlapping Networks

Use Network Address Translation (NAT) to translate IP addresses if the IP addresses that you use are neither
legal nor officially assigned. Overlapping networks result when you assign an IP address to a device on your
network that is already legally owned and assigned to a different device on the Internet or outside the network.
The figure below shows how NAT translates overlapping networks.
Figure 3: NAT Translating Overlapping Addresses
The following steps describes how a device translates overlapping addresses:

1 Host 10.1.1.1 opens a connection to Host C using a name, requesting a name-to-address lookup from a
Domain Name System (DNS) server.
2 The device intercepts the DNS reply, and translates the returned address if there is an overlap (that is, the
resulting legal address resides illegally in the inside network). To translate the return address, the device
creates a simple translation entry to map the overlapping address 10.1.1.3 to an address from a separately
configured, outside local address pool.
The device examines every DNS reply to ensure that the IP address is not in a stub network. If it is, the device
translates the address as described below:
1 Host 10.1.1.1 opens a connection to 172.16.0.3.
2 The device sets up the translation mapping of the inside local and global addresses to each other and the
outside global and local addresses to each other.

9
TCP Load Distribution for NAT
3 The device replaces the SA with the inside global address and replaces the DA with the outside global
address.
4 Host C receives the packet and continues the conversation.
5 The device does a lookup, replaces the DA with the inside local address, and replaces the SA with the
outside local address.
6 Host 10.1.1.1 receives the packet and the conversation continues using this translation process.
TCP Load Distribution for NAT

Your organization may have multiple hosts that must communicate with a heavily-used host. By using Network
Address Translation (NAT), you can establish a virtual host on the inside network that coordinates load sharing
among real hosts. Destination addresses that match an access list are replaced with addresses from a rotary
pool. Allocation is done on a round-robin basis and only when a new connection is opened from the outside
to inside the network. Non-TCP traffic is passed untranslated (unless other translations are configured). The
figure below illustrates this how TCP load distribution works.
Figure 4: NAT TCP Load Distribution
A device performs the following process when translating rotary addresses:

1 Host B (192.0.2.223) opens a connection to a virtual host at 10.1.1.127.

10
Static IP Address Support
2 The device receives the connection request and creates a new translation, allocating the next real host
(10.1.1.1) for the inside local IP address.
3 The device replaces the destination address with the selected real host address and forwards the packet.
4 Host 10.1.1.1 receives the packet and responds.
5 The device receives the packet and performs a NAT table lookup by using the inside local address and
port number, and the outside address and port number as keys. The device then translates the source address
to the address of the virtual host and forwards the packet.
6 The device will allocate IP address 10.1.1.2 as the inside local address for the next connection request.
Static IP Address Support

A public wireless LAN provides users of mobile computing devices with wireless connections to a public
network, such as the Internet.
The Network Address Translation (NAT) Static IP Address Support feature extends the capabilities of public
wireless LAN providers to support users configured with a static IP address. By configuring a device to support
users with a static IP address, public wireless LAN providers extend their services to a greater number of
users.
Users with static IP addresses can use services of the public wireless LAN provider without changing their
IP address. NAT entries are created for static IP clients and a routable address is provided.
RADIUS
RADIUS is a distributed client/server system that secures networks against unauthorized access. Communication
between a network access server (NAS) and a RADIUS server is based on UDP. Generally, the RADIUS
protocol is considered a connectionless service. Issues related to server availability, retransmission, and
timeouts are handled by RADIUS-enabled devices rather than the transmission protocol.
The RADIUS client is typically a NAS, and the RADIUS server is usually a daemon process running on a
UNIX or Windows NT machine. The client passes user information to designated RADIUS servers and acts
on the response that is returned. RADIUS servers receive user connection requests, authenticate the user, and
then return the configuration information necessary for the client to deliver the service to the user. A RADIUS
server can act as a proxy client to other RADIUS servers or other kinds of authentication servers.
Denial-of-Service Attacks
A denial-of-service (DoS) attack typically involves the misuse of standard protocols or connection processes
with the intent to overload and disable a target, such as a device or web server. DoS attacks can come from a
malicious user or from a computer infected with a virus or worm. An attack that comes from many different
sources at once, such as when a virus or worm has infected many computers, is known as a distributed DoS
attack. Such distributed DoS attacks can spread rapidly and involve thousands of systems.

11
Viruses and Worms That Target NAT
Viruses and Worms That Target NAT

Viruses and worms are malicious programs designed to attack computer and networking equipment. Although
viruses are typically embedded in discrete applications and run only when executed, worms self-propagate
and can quickly spread on their own. Although a specific virus or worm may not expressly target NAT, it
might use NAT resources to propagate itself. The Rate Limiting NAT Translation feature can be used to limit
the impact of viruses and worms that originate from specific hosts, access control lists, and VPN routing and
forwarding (VRF) instances.
How to Configure NAT for IP Address Conservation

The tasks described in this section configure NAT for IP address conservation. You must configure at least
one of the tasks described in this section. Based on your configuration, you may need to configure more than
one task.
Configuring Inside Source Addresses

Inside source addresses can be configured for static or dynamic translations. Based on your requirements, you
can configure either static or dynamic translations.
Configuring Static Translation of Inside Source Addresses

Configure static translation of inside source addresses to allow one-to-one mapping between an inside local
address and an inside global address. Static translation is useful when a host on the inside must be accessible
by a fixed address from the outside.
Note You must configure different IP addresses for an interface on which NAT is configured and for inside
addresses that are configured by using the ip nat inside source static command.
SUMMARY STEPS
1. enable
2. configure terminal
3. ip nat inside source static local-ip global-ip
4. interface type number
5. ip address ip-address mask [secondary]
6. ip nat inside
7. exit
9. ip address ip-address mask [secondary]
10. ip nat outside
11. end

12
DETAILED STEPS
Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Enter your password if prompted.
Example:
Device> enable
Step 2 configure terminal Enters global configuration mode.
Example:
Device# configure terminal
Step 3 ip nat inside source static local-ip global-ip Establishes static translation between an inside local
address and an inside global address.
Example:
Device(config)# ip nat inside source static
10.10.10.1 172.16.131.1
Step 4 interface type number Specifies an interface and enters interface configuration
mode.
Example:
Device(config)# interface ethernet 1
Step 5 ip address ip-address mask [secondary] Sets a primary IP address for an interface.
Example:
Device(config-if)# ip address 10.114.11.39
255.255.255.0
Step 6 ip nat inside Connects the interface to the inside network, which is
subject to NAT.
Example:
Device(config-if)# ip nat inside
Step 7 exit Exits interface configuration mode and returns to global

configuration mode.
Example:
Device(config-if)# exit
Step 8 interface type number Specifies a different interface and enters interface
configuration mode.
Example:
Device(config)# interface gigabitethernet 0/0/0
Step 9 ip address ip-address mask [secondary] Sets a primary IP address for an interface.
Example:
255.255.255.240

13

Step 10 ip nat outside Connects the interface to the outside network.
Example:
Device(config-if)# ip nat outside
Step 11 end Exits interface configuration mode and returns to

privileged EXEC mode.
Example:
Device(config-if)# end
Configuring Dynamic Translation of Inside Source Addresses

Dynamic translation establishes a mapping between an inside local address and a pool of global addresses.
Dynamic translation is useful when multiple users on a private network need to access the Internet. The
dynamically configured pool IP address may be used as needed and is released for use by other users when
access to the Internet is no longer required.
Note When inside global or outside local addresses belong to a directly connected subnet on a Network Address
Translation (NAT) device, the device adds IP aliases for them so that it can answer Address Resolution
Protocol (ARP) requests. However, a situation can arise where the device answers packets that are not
destined for it, possibly causing a security issue. This can happen when an incoming Internet Control
Message Protocol (ICMP) packet or an UDP packet that is destined for one of the aliased addresses does
not have a corresponding NAT translation in the NAT table, and the device itself runs a corresponding
service, for example, Network Time Protocol (NTP). Such a situation might cause minor security risks.
SUMMARY STEPS
1. enable
3. ip nat pool name start-ip end-ip {netmask netmask | prefix-length prefix-length}
4. access-list access-list-number permit source [source-wildcard]
5. ip nat inside source list access-list-number pool name
7. ip address ip-address mask
8. ip nat inside
9. exit
12. ip nat outside
13. end

14
DETAILED STEPS

Example:
Device> enable
Example:
Step 3 ip nat pool name start-ip end-ip {netmask netmask | Defines a pool of global addresses to be allocated as
prefix-length prefix-length} needed.
Example:
Device(config)# ip nat pool net-208 172.16.233.208
172.16.233.223 prefix-length 28
Step 4 access-list access-list-number permit source Defines a standard access list permitting those
[source-wildcard] addresses that are to be translated.
Example:
Device(config)# access-list 1 permit 192.168.34.0
0.0.0.255
Step 5 ip nat inside source list access-list-number pool name Establishes dynamic source translation, specifying the
access list defined in Step 4.
Example:
Device(config)# ip nat inside source list 1 pool
net-208
mode.
Example:
Step 7 ip address ip-address mask Sets a primary IP address for the interface.
Example:
255.255.255.0
subject to NAT.
Example:

15
Using NAT to Allow Internal Users Access to the Internet

configuration mode.
Example:
mode.
Example:
Example:
255.255.255.240
Example:
Step 13 end Exits interface configuration mode and returns to

Example:

Perform this task to allow your internal users access to the Internet and conserve addresses in the inside global
address pool using overloading of global addresses.

16
SUMMARY STEPS
1. enable
5. ip nat inside source list access-list-number pool name overload
8. ip nat inside
9. exit
12. ip nat outside
13. end
DETAILED STEPS

Example:
Device> enable
Example:
Example:
Device(config)# ip nat pool net-208
192.168.202.129 192.168.202.158 netmask
255.255.255.224
Step 4 access-list access-list-number permit source Defines a standard access list permitting those addresses
[source-wildcard] that are to be translated.
The access list must permit only those addresses that
Example: are to be translated. (Remember that there is an
Device(config)# access-list 1 permit
192.168.201.30 0.0.0.255 implicit deny all at the end of each access list.) Use
of an access list that is too permissive can lead to
unpredictable results.

17

Step 5 ip nat inside source list access-list-number pool name Establishes dynamic source translation with overloading,
overload specifying the access list defined in Step 4.
Example:
Device(config)# ip nat inside source list 1 pool
net-208 overload
mode.
Example:
Example:
255.255.255.240
subject to NAT.
Example:

configuration mode.
Example:
mode.
Example:
Example:
255.255.255.240
Example:
Step 13 end Exits interface configuration mode and returns to privileged

EXEC mode.
Example:

18
Configuring Address Translation Timeouts

You can configure address translation timeouts based on your NAT configuration.
By default, dynamic address translations time out after a period of nonuse. You can change the default values
on timeouts, if necessary. When overloading is not configured, simple translation entries time out after 24
hours. Use the ip nat translation timeout command to change the timeout value for dynamic address
translations.
You can use the ip nat translation max-entries command to change the default global NAT translation limit.
Changing the Translation Timeout

By default, dynamic address translations time out after some period of nonuse. You can change the default
values on timeouts, if necessary. When overloading is not configured, simple translation entries time out after
24 hours. Configure the ip nat translation timeout seconds command to change the timeout value for dynamic
address translations that do not use overloading.
Changing the Timeouts When Overloading Is Configured

If you have configured overloading, you can control the translation entry timeout, because each translation
entry contains more context about the traffic using it.
Based on your configuration, you can change the timeouts described in this section. If you need to quickly
free your global IP address for a dynamic configuration, you should configure a shorter timeout than the
default timeout, by using the ip nat translation timeout command. However, the configured timeout should
be longer than the other timeouts configured using commands specified in the following task. If a TCP session
is not properly closed by a finish (FIN) packet from both sides or during a reset, you should change the default
TCP timeout by using the ip nat translation tcp-timeout command.
SUMMARY STEPS
1. enable
3. ip nat translation seconds
4. ip nat translation udp-timeout seconds
5. ip nat translation dns-timeout seconds
6. ip nat translation tcp-timeout seconds
7. ip nat translation finrst-timeout seconds
8. ip nat translation icmp-timeout seconds
9. ip nat translation syn-timeout seconds
10. end

19
DETAILED STEPS

Example:
Device> enable
Example:
Step 3 ip nat translation seconds (Optional) Changes the amount of time after which NAT
translations time out.
Example: The default timeout is 24 hours, and it applies to the aging
Device(config)# ip nat translation 300
time for half-entries.
Step 4 ip nat translation udp-timeout seconds (Optional) Changes the UDP timeout value.
Example:
Device(config)# ip nat translation
udp-timeout 300
Step 5 ip nat translation dns-timeout seconds (Optional) Changes the Domain Name System (DNS) timeout
value.
Example:
dns-timeout 45
Step 6 ip nat translation tcp-timeout seconds (Optional) Changes the TCP timeout value.
The default is 24 hours.
Example:
tcp-timeout 2500
Step 7 ip nat translation finrst-timeout seconds (Optional) Changes the finish and reset timeout value.
finrst-timeoutThe aging time after a TCP session
Example: receives both finish-in (FIN-IN) and finish-out (FIN-OUT)
finrst-timeout 45 requests or after the reset of a TCP session.
Step 8 ip nat translation icmp-timeout seconds (Optional) Changes the ICMP timeout value.
Example:
icmp-timeout 45

20
Allowing Overlapping Networks to Communicate Using NAT

Step 9 ip nat translation syn-timeout seconds (Optional) Changes the synchronous (SYN) timeout value.
The synchronous timeout or the aging time is used only
Example: when a SYN request is received on a TCP session. When
syn-timeout 45 a synchronous acknowledgment (SYNACK) request is
received, the timeout changes to TCP timeout.
Step 10 end (Optional) Exits global configuration mode and returns to

Example:
Device(config)# end

Tasks in this section are grouped because they perform the same action but are executed differently depending
on the type of translation that is implementedstatic or dynamic. Perform the task that applies to the translation
type that you have implemented.
This section contains the following tasks:
Configuring Static Translation of Overlapping Networks
Configuring Dynamic Translation of Overlapping Networks
What to Do Next
Configuring Static Translation of Overlapping Networks

Configure static translation of overlapping networks if your IP addresses in the stub network are legitimate
IP addresses belonging to another network and you want to communicate with those hosts or routers using
static translation.

21
SUMMARY STEPS
1. enable
3. ip nat inside source static local-ip global-ip
6. ip nat inside
7. exit
10. ip nat outside
11. end
DETAILED STEPS

Example:
Device> enable
Example:
Step 3 ip nat inside source static local-ip global-ip Establishes static translation between an inside local
address and an inside global address.
Example:
192.168.121.33 10.2.2.1
mode.
Example:
Example:
255.255.255.0
Step 6 ip nat inside Marks the interface as connected to the inside.
Example:

22

configuration mode.
Example:
mode.
Example:
Example:
255.255.255.240
Step 10 ip nat outside Marks the interface as connected to the outside.
Example:
Step 11 end (Optional) Exits interface configuration mode and returns

to privileged EXEC mode.
Example:
Configuring Dynamic Translation of Overlapping Networks

Configure dynamic translation of overlapping networks if your IP addresses in the stub network are legitimate
IP addresses belonging to another network and you want to communicate with those hosts or routers using
dynamic translation.

23
SUMMARY STEPS
1. enable
5. ip nat outside source list access-list-number pool name
8. ip nat inside
9. exit
12. ip nat outside
13. end
DETAILED STEPS

Example:
Device> enable
Example:
Example:
Device(config)# ip nat pool net-10 10.0.1.0
10.0.1.255 prefix-length 24
Step 4 access-list access-list-number permit source Defines a standard access list permitting those addresses
[source-wildcard] that are to be translated.
The access list must permit only those addresses that
Example: are to be translated. (Remember that there is an
0.0.0.255 implicit deny all at the end of each access list.) Use
of an access list that is too permissive can lead to
unpredictable results.

24

Step 5 ip nat outside source list access-list-number pool name Establishes dynamic outside source translation, specifying
the access list defined in Step 4.
Example:
Device(config)# ip nat outside source list 1
pool net-10
mode.
Example:
Example:
255.255.255.0
Example:

configuration mode.
Example:
mode.
Example:
Example:
255.255.255.240
Example:
Step 13 end (Optional) Exits interface configuration mode and returns

Example:

25
Configuring Server TCP Load Balancing
What to Do Next
When you have completed the required configuration, go to the Monitoring and Maintaining NAT module.

Perform this task to configure server TCP load balancing by way of destination address rotary translation.
The commands specified in the task allow you to map one virtual host to many real hosts. Each new TCP
session opened with the virtual host will be translated into a session with a different real host.
SUMMARY STEPS
1. enable
3. ip nat pool name start-ip end-ip {netmask netmask | prefix-length prefix-length} type rotary
5. ip nat inside destination-list access-list-number pool name
8. ip nat inside
9. exit
12. ip nat outside
13. end
DETAILED STEPS

Example:
Device> enable
Example:

26

Step 3 ip nat pool name start-ip end-ip {netmask netmask | Defines a pool of addresses containing the addresses
prefix-length prefix-length} type rotary of the real hosts.
Example:
Device(config)# ip nat pool real-hosts
192.168.201.2 192.168.201.5 prefix-length 28 type
rotary
Step 4 access-list access-list-number permit source Defines an access list permitting the address of the
[source-wildcard] virtual host.
Example:
0.0.0.255
Step 5 ip nat inside destination-list access-list-number pool name Establishes dynamic inside destination translation,
specifying the access list defined in the prior step.
Example:
Device(config)# ip nat inside destination-list 2
pool real-hosts
mode.
Example:
Example:
255.255.255.240
Example:
Step 9 exit Exits interface configuration mode and returns to

global configuration mode.
Example:
Step 10 interface type number Specifies a different interface and enters interface
configuration mode.
Example:
Device(config)# interface serial 0
Example:
255.255.255.240

27
Enabling Route Maps on Inside Interfaces

Example:
Step 13 end (Optional) Exits interface configuration mode and

returns to privileged EXEC mode.
Example:
Enabling Route Maps on Inside Interfaces

Before You Begin
All route maps required for use with this task should be configured before you begin the configuration task.
SUMMARY STEPS
1. enable
3. ip nat inside source {list {access-list-number | access-list-name} pool pool-name [overload]| static
local-ip global-ip [route-map map-name]}
4. exit
5. show ip nat translations [verbose]
DETAILED STEPS

Example:
Device> enable
Example:
Step 3 ip nat inside source {list {access-list-number | Enables route mapping with static NAT configured
access-list-name} pool pool-name [overload]| static local-ip on the NAT inside interface.
global-ip [route-map map-name]}

28
Enabling NAT Route Maps Outside-to-Inside Support
Example:
192.168.201.6 192.168.201.21 route-map isp2
Step 4 exit Exits global configuration mode and returns to

Example:
Device(config)# exit
Step 5 show ip nat translations [verbose] (Optional) Displays active NAT.
Example:
Device# show ip nat translations
Enabling NAT Route Maps Outside-to-Inside Support

The NAT Route Maps Outside-to-Inside Support feature enables you to configure a Network Address
Translation (NAT) route map configuration that will allow IP sessions to be initiated from the outside to the
inside. Perform this task to enable the NAT Route Maps Outside-to-Inside Support feature.
SUMMARY STEPS
1. enable
3. ip nat pool name start-ip end-ip netmask netmask
4. ip nat pool name start-ip end-ip netmask netmask
5. ip nat inside source route-map name pool name [reversible]
6. ip nat inside source route-map name pool name [reversible]
7. end
DETAILED STEPS

Example:
Device> enable

29
Configuring NAT of External IP Addresses Only

Example:
Device(config)# configure terminal
Step 3 ip nat pool name start-ip end-ip netmask netmask Defines a pool of network addresses for NAT.
Example:
Device(config)# ip nat pool POOL-A 192.168.201.4
192.168.201.6 netmask 255.255.255.128
Step 4 ip nat pool name start-ip end-ip netmask netmask Defines a pool of network addresses for NAT.
Example:
Device(config)# ip nat pool POOL-B 192.168.201.7
192.168.201.9 netmask 255.255.255.128
Step 5 ip nat inside source route-map name pool name [reversible] Enables outside-to-inside initiated sessions to use
route maps for destination-based NAT.
Example:
Device(config)# ip nat inside source route-map MAP-A
pool POOL-A reversible
Step 6 ip nat inside source route-map name pool name [reversible] Enables outside-to-inside initiated sessions to use
route maps for destination-based NAT.
Example:
Device(config)# ip nat inside source route-map MAP-B
pool POOL-B reversible
Step 7 end (Optional) Exits global configuration mode and

returns to privileged EXEC mode.
Example:
Device(config)# end

When you configure NAT of external IP addresses, NAT can be configured to ignore all embedded IP addresses
for any application and traffic type. Traffic between a host and the traffic outside an enterprises network
flows through the internal network. A device configured for NAT translates the packet to an address that can
be routed inside the internal network. If the intended destination is outside an enterprises network, the packet
gets translated back to an external address and is sent out.

30
Note When you configure the ip nat outside source static command to add static routes for outside local
addresses, there is a delay in the translation of packets and packets are dropped. Packets are dropped
because a shortcut is not created for the initial synchronization (SYN) packet when NAT is configured
for static translation. To avoid dropped packets, configure either the ip nat outside source static add-route
command or the ip route command.
Benefits of configuring NAT of external IP addresses only are:

Allows an enterprise to use the Internet as its enterprise backbone network.
Allows the use of network architecture that requires only the header translation.
Gives the end client a usable IP address at the starting point. This address is the address used for IPsec
connections and for traffic flows.
Supports public and private network architecture with no specific route updates.
SUMMARY STEPS
1. enable
3. ip nat inside source {list {access-list-number | access-list-name} pool pool-name [overload] | static
network local-ip global-ip [no-payload]}
4. ip nat inside source {list {access-list-number | access-list-name} pool pool-name [overload] | static {tcp
| udp} local-ip local-port global-ip global-port [no-payload]}
5. ip nat inside source {list {access-list-number | access-list-name} pool pool-name [overload] | static
[network] local-network-mask global-network-mask [no-payload]}
6. ip nat outside source {list {access-list-number | access-list-name} pool pool-name | static local-ip
global-ip [no-payload]}
7. ip nat outside source {list {access-list-number | access-list-name} pool pool-name | static {tcp | udp}
local-ip local-port global-ip global-port [no-payload]}
8. ip nat outside source {list {access-list-number | access-list-name} pool pool-name | static [network]
local-network-mask global-network-mask [no-payload]}
9. exit
DETAILED STEPS

Example:
Device> enable

31

Example:
Step 3 ip nat inside source {list {access-list-number | access-list-name} pool Disables the network packet translation on
pool-name [overload] | static network local-ip global-ip [no-payload]} the inside host device.
Example:
Device(config)# ip nat inside source static network 10.1.1.1
192.168.251.0/24 no-payload
Step 4 ip nat inside source {list {access-list-number | access-list-name} pool Disables port packet translation on the
pool-name [overload] | static {tcp | udp} local-ip local-port global-ip inside host device.
global-port [no-payload]}
Example:
Device(config)# ip nat inside source static tcp 10.1.1.1 2000
192.168.1.1 2000 no-payload
Step 5 ip nat inside source {list {access-list-number | access-list-name} pool Disables packet translation on the inside
pool-name [overload] | static [network] local-network-mask host device.
global-network-mask [no-payload]}
Example:
Device(config)# ip nat inside source static 10.1.1.1
192.168.1.1 no-payload
Step 6 ip nat outside source {list {access-list-number | access-list-name} pool Disables packet translation on the outside
pool-name | static local-ip global-ip [no-payload]} host device.
Example:
Device(config)# ip nat outside source static 10.1.1.1
192.168.1.1 no-payload
Step 7 ip nat outside source {list {access-list-number | access-list-name} pool Disables port packet translation on the
pool-name | static {tcp | udp} local-ip local-port global-ip global-port outside host device.
[no-payload]}
Example:
Device(config)# ip nat outside source static tcp 10.1.1.1
20000 192.168.1.1 20000 no-payload
Step 8 ip nat outside source {list {access-list-number | access-list-name} pool Disables network packet translation on the
pool-name | static [network] local-network-mask global-network-mask outside host device.
[no-payload]}
Example:
Device(config)# ip nat outside source static network 10.1.1.1
192.168.251.0/24 no-payload

32
Configuring the NAT Default Inside Server Feature

Step 9 exit Exits global configuration mode and returns
Example:
Step 10 show ip nat translations [verbose] Displays active NAT.
Example:
Configuring the NAT Default Inside Server Feature

The NAT Default Inside Server feature helps forward packets from the outside to a specified inside local
address. Traffic that does not match any existing dynamic translations or static port translations is redirected,
and packets are not dropped.
Dynamic mapping and interface overload can be configured for gaming devices. For online games, outside
traffic comes on a different UDP port. If a packet is destined for an interface from outside an enterprises
network and there is no match in the NAT table for the fully extended entry or the static port entry, the packet
is forwarded to the gaming device using a simple static entry.
Note You can use this feature to configure gaming devices with an IP address that is different from that
of the PC. To avoid unwanted traffic or DoS attacks, use access lists.
For traffic going from the PC to the outside, it is better to use a route map so that extended entries
are created.
SUMMARY STEPS
1. enable
3. ip nat inside source static local-ip interface type number
4. ip nat inside source static tcp local-ip local-port interface global-port
5. exit
DETAILED STEPS


33
Reenabling RTSP on a NAT Router

Example:
Device> enable
Example:
Step 3 ip nat inside source static local-ip interface type number Enables static NAT on the interface.
Example:
Device(config)# ip nat inside source static 10.1.1.1
interface Ethernet 1/1
Step 4 ip nat inside source static tcp local-ip local-port interface (Optional) Enables the use of telnet to the device
global-port from the outside.
Example:
Device(config)# ip nat inside source static tcp
10.1.1.1 23 interface 23
Step 5 exit Exits global configuration mode and returns to

Example:
Step 6 show ip nat translations [verbose] (Optional) Displays active NAT.
Example:
Reenabling RTSP on a NAT Router

The Real Time Streaming Protocol (RTSP) is a client/server multimedia presentation control protocol that
supports multimedia application delivery. Some of the applications that use RTSP include Windows Media
Services (WMS) by Microsoft, QuickTime by Apple Computer, and RealSystem G2 by RealNetworks.
When the RTSP protocol passes through a NAT router, the embedded address and port must be translated for
the connection to be successful. NAT uses Network Based Application Recognition (NBAR) architecture to
parse the payload and translate the embedded information in the RTSP payload.
RTSP is enabled by default. Use the ip nat service rtsp port port-number command to reenable RTSP on a
NAT router if this configuration has been disabled.

34
Configuring Support for Users with Static IP Addresses

Configuring support for users with static IP addresses enables those users to establish an IP session in a public
wireless LAN environment.
Before You Begin

Before configuring support for users with static IP addresses, you must first enable NAT on your router and
configure a RADIUS server host.
SUMMARY STEPS
1. enable
4. ip nat inside
5. exit
6. ip nat allow-static-host
7. ip nat pool name start-ip end-ip netmask netmask accounting list-name
8. ip nat inside source list access-list-number pool name
9. access-list access-list-number deny ip source
10. end
11. show ip nat translations verbose
DETAILED STEPS

Example:
Device> enable
Example:
Step 3 interface type number Configures an interface and enters interface configuration
mode.
Example:
Example:

35

configuration mode.
Example:
Step 6 ip nat allow-static-host Enables static IP address support.

Dynamic Address Resolution Protocol (ARP) learning
Example: will be disabled on this interface, and NAT will control
Device(config)# ip nat allow-static-host
the creation and deletion of ARP entries for the static IP
host.
Step 7 ip nat pool name start-ip end-ip netmask netmask Specifies an existing RADIUS profile name to be used for
accounting list-name authentication of the static IP host.
Example:
Device(config)# ip nat pool pool1 172.16.0.0
172.16.0.254 netmask 255.255.255.0
accounting WLAN-ACCT
Step 8 ip nat inside source list access-list-number pool Specifies the access list and pool to be used for static IP
name support.
The specified access list must permit all traffic.
Example:
Device(config)# ip nat inside source list 1
pool net-208
Step 9 access-list access-list-number deny ip source Removes the traffic of the device from NAT.
The source argument is the IP address of the device that
Example: supports the NAT Static IP Support feature.
Device(config)# access-list 1 deny ip
192.168.196.51
Step 10 end (Optional) Exits global configuration mode and returns to

Example:
Device(config)# end
Step 11 show ip nat translations verbose (Optional) Displays active NAT translations and additional
information for each translation table entry, including how
Example: long ago the entry was created and used.
Device# show ip nat translations verbose
Examples
The following is sample output from the show ip nat translations verbose command:
Device# show ip nat translations verbose
--- 172.16.0.0 10.1.1.1 --- ---

36
Configuring the Rate Limiting NAT Translation Feature
create 00:05:59, use 00:03:39, left 23:56:20, Map-Id(In): 1, flags: none wlan-flags: Secure
ARP added, Accounting Start sent Mac-Address:0010.7bc2.9ff6 Input-IDB:Ethernet1/2, use_count:
0, entry-id:7, lc_entries: 0
Configuring the Rate Limiting NAT Translation Feature

SUMMARY STEPS
1. enable
2. show ip nat translations
4. ip nat translation max-entries {number | all-vrf number | host ip-address number | list listname number
| vrf name number}
5. end
6. show ip nat statistics
DETAILED STEPS

Example:
Device enable
Step 2 show ip nat translations (Optional) Displays active NAT.

A specific host, access control list, or VRF instance generating an
Example: unexpectedly high number of NAT requests may be the source of a
malicious virus or worm attack.
Example:
Step 4 ip nat translation max-entries {number | Configures the maximum number of NAT entries allowed from the
all-vrf number | host ip-address number | specified source.
list listname number | vrf name number}
The maximum number of allowed NAT entries is 2147483647,
although a typical range for a NAT rate limit is 100 to 300 entries.
Example:
Device(config)# ip nat translation When you configure a NAT rate limit for all VRF instances, each
max-entries 300
VRF instance is limited to the maximum number of NAT entries
that you specify.
When you configure a NAT rate limit for a specific VRF instance,
you can specify a maximum number of NAT entries for the named
VRF instance that is greater than or less than that allowed for all
VRF instances.

37
Configuring Bypass NAT Functionality

Step 5 end Exits global configuration mode and returns to privileged EXEC mode.
Example:
Device(config)# end
Step 6 show ip nat statistics (Optional) Displays current NAT usage information, including NAT rate
limit settings.
Example: After setting a NAT rate limit, use the show ip nat statistics
Device# show ip nat statistics
command to verify the current NAT rate limit settings.
Configuring Bypass NAT Functionality

The Bypass NAT functionality feature reduces the TCAM size by resolving the deny jump issue. To enable
the Bypass NAT functionality feature you must create a NAT bypass pool using a reserved loopback address
(127.0.0.1) and a new NAT mapping containing a new ACL with all existing deny statements converted to
permit statements. You can enable the Bypass NAT functionality by creating new NAT mapping with new
ACL mapped to bypass pool.
To configure the bypass-pool with 127.0.0.1 as reserved loopback address:
enable
configure terminal
access-list 60 permit 25.33.0.0 0.0.255.255
ip nat pool bypass-pool 127.0.0.1 127.0.0.1 prefix-length 24
ip nat inside source list 60 pool bypass-pool
end
To convert existing configuration with deny statements:

enable
configure terminal
ip access list extended nat-acl
deny ip host 10.10.10.10 host 10.77.64.17
permit ip any 10.77.64.0 0.0.15.255
ip nat inside source list nat-acl pool nat-pool
end
New converted configuration using bypass pool with permit statements:

enable
configure terminal
ip nat pool bypass-pool 127.0.0.1 127.0.0.1 prefix-length 24
ip access list extended nat-bypass-acl
permit ip host 10.10.10.10 host 10.77.64.17
ip nat inside source list nat-bypass-acl pool bypass-pool
ip access list extended nat-acl
permit ip any 10.77.64.0 0.0.15.255
ip nat inside source list nat-acl pool nat-pool
end

38
Configuration Examples for Configuring NAT for IP Address Conservation
Configuration Examples for Configuring NAT for IP Address

Conservation
Example: Configuring Static Translation of Inside Source Addresses

The following example shows how inside hosts addressed from the 10.114.11.0 network are translated to the
globally unique 172.31.233.208/28 network. Further, packets from outside hosts addressed from the 10.114.11.0
network (the true 10.114.11.0 network) are translated to appear to be from the 10.0.1.0/24 network.
ip nat pool net-208 172.31.233.208 172.31.233.223 prefix-length 28

ip nat inside source list 1 pool net-208
ip nat outside source list 1 pool net-10
!
interface gigabitethernet 0/0/0
ip address 172.31.232.182 255.255.255.240
ip nat outside
!
ip address 10.114.11.39 255.255.255.0
ip nat inside
!
The following example shows NAT configured on the provider edge (PE) device with a static route to the
shared service for the vrf1 and vrf2 VPNs. NAT is configured as inside source static one-to-one translation.
ip nat pool outside 10.4.4.1 10.4.4.254 netmask 255.255.255.0

ip nat outside source list 1 pool mypool
ip nat inside source static 192.168.121.33 10.2.2.1 vrf vrf1
ip nat inside source static 192.168.121.33.10.2.2.2 vrf vrf2
Example: Configuring Dynamic Translation of Inside Source Addresses

The following example shows how inside hosts addressed from either the 192.168.1.0 or the 192.168.2.0
network are translated to the globally unique 172.31.233.208/28 network:

!
ip address 172.31.232.182 255.255.255.240
ip nat outside
!
ip address 192.168.1.94 255.255.255.0
ip nat inside
!
!

39
Example: Using NAT to Allow Internal Users Access to the Internet
The following example shows how only traffic local to the provider edge (PE) device running NAT is translated:
ip nat inside source list 1 interface gigabitethernet 0/0/0 vrf vrf1 overload
!
ip route vrf vrf1 0.0.0.0 0.0.0.0 192.168.1.1
ip route vrf vrf2 0.0.0.0 0.0.0.0 192.168.1.1
!
access-list 1 permit 10.1.1.1.0 0.0.0.255
!
!
ip route vrf vrf1 0.0.0.0 0.0.0.0 172.16.1.1 global
ip route vrf vrf2 0.0.0.0 0.0.0.0 172.16.1.1 global
!
Example: Using NAT to Allow Internal Users Access to the Internet

The following example shows how to create a pool of addresses that is named net-208. The pool contains
addresses from 172.31.233.208 to 172.31.233.233. Access list 1 allows packets with SA from 192.168.1.0 to
192.168.1.255. If no translation exists, packets matching access list 1 are translated to an address from the
pool. The router allows multiple local addresses (192.168.1.0 to 192.168.1.255) to use the same global address.
The router retains port numbers to differentiate the connections.
ip nat pool net-208 172.31.233.208 172.31.233.233 netmask 255.255.255.240

ip nat inside source list 1 pool net-208 overload
ip address 192.168.201.1 255.255.255.240
ip nat inside
!
ip address 192.168.201.29 255.255.255.240
ip nat outside
!
Example: Allowing Overlapping Networks to Communicate Using NAT
Example: Configuring Static Translation of Overlapping Networks

ip nat inside source static 192.168.121.33 10.2.2.1
!
ip address 10.114.11.39 255.255.255.0
ip nat inside
!
ip address 172.16.232.182 255.255.255.240
ip nat outside
!
Example: Configuring Dynamic Translation of Overlapping Networks

In the following example, the addresses in the local network are being used legitimately by someone else on
the Internet. An extra translation is required to access the external network. The pool net-10 is a pool of outside

40
Example: Configuring Server TCP Load Balancing
local IP addresses. The ip nat outside source list 1 pool net-10 command translates the addresses of hosts
from the outside overlapping network to addresses in that pool.
ip nat outside source list 1 pool net-10
!
ip address 10.114.11.39 255.255.255.0
ip nat inside
!
ip address 172.16.232.182 255.255.255.240
ip nat outside
!
Example: Configuring Server TCP Load Balancing

In the following example, the goal is to define a virtual address, connections to which are distributed among
a set of real hosts. The pool defines addresses of real hosts. The access list defines the virtual address. If a
translation does not already exist, TCP packets from serial interface 0 (the outside interface), whose destination
matches the access list, are translated to an address from the pool.
ip nat pool real-hosts 192.168.15.2 192.168.15.15 prefix-length 28 type rotary

access-list 2 permit 192.168.15.1
ip nat inside destination list 2 pool real-hosts
ip address 192.168.15.129 255.255.255.240
ip nat inside
!
interface serial 0
ip address 192.168.15.17 255.255.255.240
ip nat outside
!
Example: Enabling Route Maps on Inside Interfaces

ip nat inside source static 192.168.201.6 192.168.201.21
!
Example: Enabling NAT Route Maps Outside-to-Inside Support

The following example shows how to configure route map A and route map B to allow outside-to-inside
translation for a destination-based Network Address Translation (NAT):
ip nat pool POOL-A 192.168.201.4 192.168.201.6 netmask 255.255.255.128
ip nat pool POOL-B 192.168.201.7 192.168.201.9 netmask 255.255.255.128
ip nat inside source route-map MAP-A pool POOL-A reversible
ip nat inside source route-map MAP-B pool POOL-B reversible
Example: Configuring NAT of External IP Addresses Only

ip nat inside source static network 10.1.1.1 192.168.2510/24 no-payload
ip nat inside source static tcp 10.1.1.1 2000 192.168.1.1 2000 no-payload
ip nat inside source static 10.1.1.1 192.168.1.1 no-payload
ip nat outside source static 10.1.1. 192.168.1.1 no-payload

41
Example: Configuring Support for Users with Static IP Addresses
ip nat outside source static tcp 10.1.1.1 20000 192.168.1.1 20000 no-payload
ip nat outside source static network 10.1.1.1 192.168.251.0/24 no-payload
Example: Configuring Support for Users with Static IP Addresses

ip nat inside
!
ip nat allow-static-host
ip nat pool pool1 172.16.0.0 172.16.0.254 netmask 255.255.255.0 accounting WLAN-ACCT
access-list 1 deny ip 192.168.196.51
Example: Configuring NAT Static IP Support

The following example shows how to enable static IP address support for the device at 192.168.196.51:

ip nat inside
!
ip nat allow-static-host
ip nat pool net-208 172.16.1.1 172.16.1.10 netmask 255.255.255.0 accounting WLAN-ACCT
access-list 1 deny ip 192.168.196.51
Example: Creating a RADIUS Profile for NAT Static IP Support

The following example shows how to create a RADIUS profile for use with the NAT Static IP Support feature:
aaa new-model
!
aaa group server radius WLAN-RADIUS
server 172.16.88.1 auth-port 1645 acct-port 1645
server 172.16.88.1 auth-port 1645 acct-port 1646
!
aaa accounting network WLAN-ACCT start-stop group WLAN-RADIUS
aaa session-id common
ip radius source-interface gigabitethernet3/0
radius-server host 172.31.88.1 auth-port 1645 acct-port 1646
radius-server key cisco
Example: Configuring the Rate Limiting NAT Translation Feature

The following example shows how to limit the maximum number of allowed NAT entries to 300:
ip nat translation max-entries 300
The following example shows how to limit the VRF instance named vrf1 to 150 NAT entries:
ip nat translation max-entries vrf vrf1 150
The following example shows how to limit each VRF instance to 200 NAT entries:
ip nat translation max-entries all-vrf 200
The following example shows how to limit the VRF instance named vrf2 to 225 NAT entries, but limit all
other VRF instances to 100 NAT entries each:

42
Where to Go Next
The following example shows how to limit the access control list named vrf3 to 100 NAT entries:
ip nat translation max-entries list vrf3 100
The following example shows how to limit the host at IP address 10.0.0.1 to 300 NAT entries:
ip nat translation max-entries host 10.0.0.1 300
Example: Setting a Global NAT Rate Limit

The following example shows how to limit the maximum number of allowed NAT entries to 300:
ip nat translation max-entries 300
Example: Setting NAT Rate Limits for a Specific VRF Instance

The following example shows how to limit the VRF instance named vrf1 to 150 NAT entries:
Example: Setting NAT Rate Limits for All VRF Instances

The following example shows how to limit each VRF instance to 200 NAT entries:

The following example shows how to limit the VRF instance named vrf2 to 225 NAT entries, but limit all
other VRF instances to 100 NAT entries each:

Example: Setting NAT Rate Limits for Access Control Lists

The following example shows how to limit the access control list named vrf3 to 100 NAT entries:
ip nat translation max-entries list vrf3 100
Example: Setting NAT Rate Limits for an IP Address

The following example shows how to limit the host at IP address 10.0.0.1 to 300 NAT entries:
ip nat translation max-entries host 10.0.0.1 300
Where to Go Next
To configure NAT for use with application-level gateways, see the Using Application Level Gateways
with NAT module.
To verify, monitor, and maintain NAT, see the Monitoring and Maintaining NAT module.

43
Additional References for Configuring NAT for IP Address Conservation
To integrate NAT with Multiprotocol Label Switching (MPLS) VPNs, see the Integrating NAT with
MPLS VPNs module.
To configure NAT for high availability, see the Configuring NAT for High Availability module.
Additional References for Configuring NAT for IP Address

Conservation
Related Documents
Related Topic Document Title

Cisco IOS commands Cisco IOS Master Command List, All Releases
NAT commands: complete command syntax, Cisco IOS IP Addressing Services Command Reference
command mode command history, defaults,
usage guidelines, and examples
Application-level gateways Using Application Level Gateways with NAT module
IP access list sequence numbering IP Access List Entry Sequence Numbering document
RADIUS attributes overview RADIUS Attributes Overview and RADIUS IETF Attributes
module
Standards and RFCs
Standard/RFC Title
IETF Behave Draft NAT MIB Definitions of Managed Objects for Network Address
Translators (NAT) draft-ietf-behave-nat-mib-11
RFC 1597 Internet Assigned Numbers Authority
RFC 1631 The IP Network Address Translation (NAT)
RFC 1918 Address Allocation for Private Internets
RFC 2663 IP Network Address Translation (NAT) Terminology and

Considerations
RFC 3022 Traditional IP Network Address Translation (Traditional NAT)

44
Feature Information for Configuring NAT for IP Address Conservation
Technical Assistance
Description Link
The Cisco Support website provides extensive online http://www.cisco.com/support
resources, including documentation and tools for
troubleshooting and resolving technical issues with
Cisco products and technologies.
To receive security and technical information about
your products, you can subscribe to various services,
such as the Product Alert Tool (accessed from Field
Notices), the Cisco Technical Services Newsletter,
and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website
requires a Cisco.com user ID and password.
Feature Information for Configuring NAT for IP Address

Conservation
The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1: Feature Information for Configuring NAT for IP Address Conservation
Feature Name Releases Feature Information

Destination-Based NAT Using Cisco IOS XE Release The Destination-Based NAT Using Route Maps
Route Maps 2.1 feature adds support for destination-based NAT
using route maps.
NAT Duplicate Inside Global Cisco IOS XE Release The Cisco IOS XE software supports the NAT
Address 2.1 Duplicate Inside Global Addresses feature.
NAT Host Number Preservation Cisco IOS XE Release For ease of network management, some sites
2.1 prefer to translate prefixes rather than addresses.
These sites want the translated address to have
the same host number as the original address.
The two prefixes must be of the same length.
The NAT Host Number Preservation feature
can be enabled by configuring dynamic
translation with the address pool of the type,
match-host.

45

NAT MIB Support Cisco IOS XE Release The NAT MIB Support feature supports, IETF
3.15S Behave Draft, Definitions of Managed Objects
for Network Address Translators (NAT). Only
regular NAT is supported, NAT 64 is not
supported.
NAT Performance Cisco IOS XE Release The NAT Performance

EnhancementTranslation Table 2.1 EnhancementTranslation Table Optimization
Optimization feature provides greater structure for storing
translation table entries and an optimized lookup
in the table for associating table entries to IP
connections.
NAT Route Maps Outside-to- Cisco IOS XE Release The NAT Route Maps Outside-to- Inside
Inside Support 2.2 Support feature enables the deployment of a
NAT route map configuration that will allow IP
sessions to be initiated from the outside to the
inside.
NAT Static IP Support Cisco IOS XE Release The NAT Static IP Support feature provides
2.1 support for users with static IP addresses,
enabling those users to establish an IP session
in a public wireless LAN environment.
NAT Timers Cisco IOS XE Release The NAT Timers feature allows you to change
2.1 the amount of time after which NAT translations
time out.
NAT Translation of External IP Cisco IOS XE Release You can use the NAT Translation of External
Addresses Only 2.1 IP Address Only feature to configure NAT to
ignore all embedded IP addresses for any
application and traffic type.
Rate Limiting NAT Translation Cisco IOS XE Release The Rate Limiting NAT Translation feature
2.1 provides the ability to limit the maximum
number of concurrent Network Address
Translation (NAT) operations on a router. In
addition to giving users more control over how
NAT addresses are used, the Rate Limiting NAT
Translation feature can be used to limit the
effects of viruses, worms, and denial-of-service
attacks.

46

VRF Scale Increase in NAT Cisco IOS XE Release The VRF Scale Increase in NAT feature
3.10S provides the ability to increase the number of
virtual routing and forwarding (VRF) instances
that are supported on NAT to 4000. This feature
is enabled by default when NAT is configured.
You cannot disable this configuration.
No commands were introduced or modified for
this feature.
In Cisco IOS XE Release 3.10S, support was
added for Cisco CSR 1000V Series Routers.
In Cisco IOS XE Release 3.10S, support was
added for Cisco ISR 4400 Series Routers.
NAT support on BDI interface Cisco IOS XE Denali The NAT support on BDI interface feature
16.3.1 enables you to configure NAT on Bridge
Domain Interface (BDI).
No commands were introduced or modified for
this feature.
Multi-Tenant support for NAT Cisco IOS XE Denali With Multi-Tenant support for NAT feature,
16.3.1 the configuration changes of a VRF instance
does not interrupt the traffic flow of other VRFs
in the network.
This feature uses no new or modified
commands.
Bypass NAT functionality Cisco IOS XE Denali The Bypass NAT functionality feature enables
16.3.2 you to permit an ACL with deny statements
using a bypass pool. The Bypass NAT
functionality feature reduces the TCAM size by
resolving the deny jump issue.
This feature uses no new or modified
commands.

47

48

NAT Types

Uploaded by

Copyright:

Available Formats

NAT Types

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NAT Types

Uploaded by

Copyright:

Available Formats

Configuring NAT for IP Address Conservation

Finding Feature Information, page 1

Finding Feature Information

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

Prerequisites for Configuring NAT for IP Address Conservation

Define what you need NAT to accomplish:

Restrictions for Configuring NAT for IP Address Conservation

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

Information About Configuring NAT for IP Address Conservation

Benefits of Configuring NAT for IP Address Conservation

How NAT Works

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

NAT Inside and Outside Addresses

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

This section describes the following topics:

Inside Source Address Translation

Figure 1: NAT Inside Source Translation

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

Overloading of Inside Global Addresses

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

Figure 2: NAT Overloading Inside Global Addresses

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

Address Translation of Overlapping Networks

Figure 3: NAT Translating Overlapping Addresses

The following steps describes how a device translates overlapping addresses:

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

TCP Load Distribution for NAT

Figure 4: NAT TCP Load Distribution

A device performs the following process when translating rotary addresses:

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

Static IP Address Support

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

Viruses and Worms That Target NAT

How to Configure NAT for IP Address Conservation

Configuring Inside Source Addresses

Configuring Static Translation of Inside Source Addresses

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

Command or Action Purpose

Step 2 configure terminal Enters global configuration mode.

Step 7 exit Exits interface configuration mode and returns to global

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

Command or Action Purpose

Step 11 end Exits interface configuration mode and returns to

Configuring Dynamic Translation of Inside Source Addresses

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

Command or Action Purpose

Step 2 configure terminal Enters global configuration mode.

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

Command or Action Purpose

Step 12 ip nat outside Connects the interface to the outside network.

Step 13 end Exits interface configuration mode and returns to

Using NAT to Allow Internal Users Access to the Internet

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

Command or Action Purpose

Step 2 configure terminal Enters global configuration mode.

IP Addressing: NAT Configuration Guide, Cisco IOS XE Release 3S

Command or Action Purpose