mẹo hay

Fix lỗi you appear to be behind a nat route năm 2024

The workstation is behind NAT [different subnet entirely to that used by the teleport server], but is otherwise unrestricted. Note that attempting to connect from an ssh session running on the teleport server itself also fails in the same way, so I think that eliminates any issue with connectivity between the client session [as in the machine being used by human running tsh db connect db] and the teleport server.

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. Before packets are forwarded onto another network, NAT translates the private [not globally unique] addresses in the internal network into legal addresses. NAT can be configured to advertise to the outside world only one address for the entire network. This ability provides more 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. It allows Internet access to internal devices such as mail servers.

Prerequisites for Configuring NAT for IP Address Conservation

Access Lists

All access lists that are required for use with the configuration tasks that are described in this module must be configured before initiating 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. This command is commonly used in an access list.

NAT Requirements

Before configuring NAT in your network, ensure that you know the interfaces on which NAT is configured and for what purposes. The following requirements 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 networks with different address schemes to communicate.
- 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 the BDI interface.

Restrictions for Configuring NAT for IP Address Conservation

It is not practical to use Network Address Translation [NAT] if a large number 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 not work at all through a NAT device.
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 the outside. However, routing information that NAT receives from the outside can be advertised in the stub domain as usual.
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 the access list.
NAT configuration is not supported on the access side of the Intelligent Services Gateway [ISG].
On Cisco Catalyst 6500 Series Switches, if you have a NAT overload configuration, we recommend that you limit the number of NAT translations to less than 64512, by using the ip nat translation max-entries command. If the number of NAT translations is 64512 or more, a limited number of ports are available for use by local applications, which, in turn can cause security issues such as denial-of-service [DoS] attacks. The port numbers used by local applications can easily be identified by DoS attacks, leading to security threats. This restriction is specific to all NAT overload configurations [for example, interface overload or pool overload configurations] that use a logical, loopback, or physical address for NAT configurations.
Configuring zone-based policy firewall high availability with NAT and NAT high availability with zone-based policy firewalls is not recommended.
If the NAT outside local address matches with any logical interface address, interface IP address, or a tunnel-configured address; then packets are software-switched.
NAT outside interface is not supported on a VRF. However, NAT outside interface is supported in iWAN and is part of the Cisco Validated Design.
The acl-log keyword will not work with an ACL used in NAT. The permit or deny functions for NAT ACL are used to filter the traffic according to the NAT rule. A rule like permit tcp any any log in the ACL used for NAT configuration is similar to permit tcp any any . Native ACL logging does not work in this ACL.
BFD sessions may fail if you configure them to operate using an address that is also used for dynamic NAT. One common scenario is when you configure BFD on the same interface that you use to carry out interface-based dynamic NAT overload. To avoid this, you can instead employ a pool-based dynamic NAT overload configuration. However, even in this scenario, ensure that you do not use the chosen NAT pool address for BFD. When you configure BFD, we recommend you to use an address that does not overlap with NAT in order to avoid a conflict in case dynamic NAT is also configured on the device.

Information About Configuring NAT for IP Address Conservation

Benefits of Configuring NAT for IP Address Conservation

Network Address Translation [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 IP addresses, and if more than 254 clients are present or are planned, the scarcity of Class B addresses becomes a serious issue. 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 clients. With client addresses hidden, a degree of security is established. 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]. The expansion of Class A addresses occurs within the organization without a concern for addressing changes at the LAN or the Internet interface.

Cisco software can selectively or dynamically perform NAT. This flexibility allows 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 routers for IP address simplification and conservation. In addition, 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 any changes to hosts or routers other than to those few routers on which NAT will be configured.

Purpose of NAT

NAT is a feature that allows the IP network of an organization to appear from the outside to use a different IP address space than what it is actually using. 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.

NAT supports all H.225 and H.245 message types, including FastConnect and Alerting, as part of the H.323 Version 2 specification. Any product that makes use of these message types will be able to pass through a Cisco NAT configuration without any static configuration. Full support for NetMeeting Directory [Internet Locator Service] is also provided through NAT.

How NAT Works

A device that is configured with NAT has 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 exits 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. Then, NAT sends an Internet Control Message Protocol [ICMP] host unreachable packet to the destination.

Uses of NAT

NAT can be used for the following scenarios:

Connect to the internet when all your hosts do not have globally unique IP addresses. Network Address Translation [NAT] enables private IP networks that use nonregistered IP addresses to connect to the Internet. NAT is configured on a device at the border of a stub domain [mentioned as the inside network ] and a public network such as the Internet [mentioned 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 simultaneously outside the domain. When outside communication is necessary, only a small subset of the IP addresses in the domain must be translated into globally unique IP addresses. Also, 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 with many local IP addresses by using the TCP Load Distribution feature.

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 have addresses in one space [known as the local address space]. These hosts appear to those users 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 not under the control of an organization. Also, hosts in outside networks can be subject to translation, and can thus have local and global addresses. NAT uses the following definitions:

Inside local address—An IP address that is assigned to a host on the inside network. The address that the Network Information Center [NIC] or service provider assigns is probably not a legitimate IP address.
Inside global address—A 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 address—The 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 address—The IP address that is 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.

NAT supports the following VRFs:

Table 1. VRF NAT Support

NAT Inside Interface

NAT Outside Interface

Condition

Global VRF [also referred to as a non-VRF interface]

Normal

VRF X

Global VRF [also referred to as a non-VRF interface]

When NAT is not configured for Match-in-VRF support. For more details, see the Match-in-VRF Support for NAT chapter.

VRF X

When both inside and outside interfaces are in the same VRF, and NAT is configured with Match-in-VRF support.

This section describes the following topics:

Inside Source Address Translation

You can translate IP addresses into globally unique IP addresses when communicating outside of your network. You can configure inside source address translation of static or dynamic NAT 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 following figure 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

The following process describes the inside source address translation, as shown in the preceding figure:

The user at host 10.1.1.1 opens a connection to Host B in the outside network.
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. The device selects a legal, global address from the dynamic address pool, and creates a translation entry in the NAT table. This kind of translation entry is called a simple entry .
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.
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.
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. 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]. This action translates 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.

The following figure 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 preceding figure. Both Host B and Host C believe that they are communicating with a single host at address 203.0.113.2. Whereas, 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.

The user at host 10.1.1.1 opens a connection to Host B.
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. This saved information 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 .
The device replaces inside local source address 10.1.1.1 with the selected global address and forwards the packet.
Host B receives the packet and responds to host 10.1.1.1 by using the inside global IP address 203.0.113.2.
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. It 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.

Types of NAT

NAT operates on a router—generally connecting only two networks. Before any packets are forwarded to another network, NAT translates the private [inside local] addresses within the internal network into public [inside global] addresses. This functionality gives you the option to configure NAT so that it advertises only a single address for your entire network to the outside world. Doing this translation, NAT 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.
Overloading—Maps multiple unregistered IP addresses to a single registered IP address [many to one] by using different ports. This method is also known as Port Address Translation [PAT]. Thousands of users can be connected to the Internet by using only one real global IP address through overloading.

Address Translation of Overlapping Networks

Use Network Address Translation [NAT] to translate IP addresses if the IP addresses that you use are not legal or officially assigned. Overlapping networks result when you assign an IP address to a device on your network. This device is already legally owned and assigned to a different device on the Internet or outside the network.

The following figure shows how NAT translates overlapping networks.

Figure 3. NAT Translating Overlapping Addresses

The following steps describe how a device translates overlapping addresses:

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.
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. This entry maps the overlapping address, 10.1.1.3 to an address from a separately configured, outside the 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 in the following steps:

Host 10.1.1.1 opens a connection to 172.16.0.3.
The device sets up the translation mapping of the inside local and global addresses to each other. It also sets up the translation mapping of the outside global and local addresses to each other.
The device replaces the SA with the inside global address and replaces the DA with the outside global address.
Host C receives the packet and continues the conversation.
The device does a lookup, replaces the DA with the inside local address, and replaces the SA with the outside local address.
Host 10.1.1.1 receives the packet and the conversation continues using this translation process.

NAT Virtual Interface

The NAT Virtual Interface feature allows NAT traffic flows on the virtual interface, eliminating the need to specify inside and outside domains. When a domain is specified, translation rules are applied either before or after route decisions are applied, depending on the traffic flow from inside to outside or outside to inside. Translation rules are applied to a domain only after the route decision for a NAT Virtual Interface [NVI] is applied.

When a NAT pool is shared for translating packets from multiple networks connected to a NAT router, an NVI is created and a static route is configured that forwards all packets addressed to the NAT pool to the NVI. Standard interfaces connected to various networks are configured to determine if the traffic originating from and received on the interfaces needs to be translated.

The figure below shows a typical NVI configuration.

Figure 4. NAT Virtual Interface Typical Configuration

An NVI has the following benefits:

A NAT table is maintained per interface for better performance and scalability.
Domain-specific NAT configurations can be eliminated.

The following restrictions apply to an NVI configuration:

Route maps are not supported.
NVI is not supported in a NAT on-a-stick scenario. The term NAT on-a-stick implies the use of a single physical interface of a router for translation. NVI is designed for traffic from one VPN routing and forwarding [VRF] instance to another and not for routing between subnets in a global routing table. For more information, see the Network Address Translation on a Stick document.
Note

Use access-control list [ACL] to prevent inside hosts trying to establish an IPSec session to the same IPsec headend as the router.

Note

NAT Virtual Interface gets dynamically created as part of NAT feature initialization and this interface is required for enabling the support for specific NAT usage scenarios. When a crypto module avails specific NAT services [APIs] to reserve transport ports that are of interest, the NAT feature is initialized creating a NAT Virtual interface.

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 following figure illustrates how TCP load distribution works.

Figure 5. NAT TCP Load Distribution

A device performs the following process when translating rotary addresses:

Host B [192.0.2.223] opens a connection to a virtual host at 10.1.1.127.
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.
The device replaces the destination address with the selected real host address and forwards the packet.
Host 10.1.1.1 receives the packet and responds.
The device receives the packet and performs a NAT table lookup by using the inside local address and port number. It also does a NAT table lookup by using 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.
The device will allocate IP address 10.1.1.2 as the inside local address for the next connection request.

Route Map Overview

For NAT, a route map must be processed instead of an access list. A route map allows you to match any combination of access lists, next-hop IP addresses, and output interfaces to determine which pool to use. The ability to use route maps with static translations enables the NAT multihoming capability with static address translations. Multihomed internal networks can host common services such as the Internet and DNS, which are accessed from different outside networks. NAT processes route map-based mappings in lexicographical order. When static NAT and dynamic NAT are configured with route maps that share the same name, static NAT is given precedence over dynamic NAT. To ensure the precedence of static NAT over dynamic NAT, you can either configure the route map associated with static NAT and dynamic NAT to share the same name or configure the static NAT route map name so that it is lexicographically lower than the dynamic NAT route map name.

Benefits of using route maps for address translation are as follows:

The ability to configure route map statements provides the option of using IPsec with NAT.
Translation decisions can be made based on the destination IP address when static translation entries are used.

NAT Route Maps Outside-to-Inside Support Feature

The NAT Route Maps Outside-to-Inside Support feature enables the deployment of a NAT route map configuration that allows IP sessions to be initiated from the outside to the inside.

An initial session from inside to outside is required to trigger a NAT. New translation sessions can then be initiated from the outside to the inside host that triggered the initial translation. When route maps are used to allocate global addresses, the global address can allow return traffic, and the return traffic is allowed only if it matches the defined route map in the reverse direction. The outside-to-inside functionality remains unchanged [by not creating additional entries to allow the return traffic for a route-map-based dynamic entries] unless you configure the ip nat inside source reversible command.

The following restrictions apply to the NAT Route Maps Outside-to-Inside Support feature:

Access lists with reversible route maps must be configured to match the inside-to-outside traffic.
In Cisco IOS Release 12.2[33]SXI5, the NAT Route Maps Outside-to-Inside Support feature is supported only on Cisco ME 6500 series Ethernet switches.
Only IP hosts that are part of the route-map configuration will allow outside sessions.
Outside-to-inside support is not available with PAT.
Outside sessions must use an access list.
The match interface and match ip next-hop commands are not supported for reversible route maps.

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.

To support users who are configured with a static IP address, the NAT Static IP Address Support feature extends the capabilities of public wireless LAN providers. 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. RADIUS-enabled devices handle issues that are related to a server availability, retransmission, and timeouts 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. To deliver service to the user, RADIUS servers receive a user connection request, authenticate the user, and then return the configuration information necessary for the client. 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 misuse of standard protocols or connection processes. The intent of DoS attack is 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 that is infected with a virus or worm. Distributed DoS attack is an attack that comes from many different sources at once. This attack can be when a virus or worm has infected many computers. Such distributed DoS attacks can spread rapidly and involve thousands of systems.

Viruses and Worms That Target NAT

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

How to Configure NAT for IP Address Conservation

The tasks that are described in this section configure NAT for IP address conservation. Ensure that you configure at least one of the tasks that are 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 the 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

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

enable
configure terminal
ip nat inside source static local-ip global-ip
interface type number
ip address ip-address mask [secondary]
ip nat inside
exit
interface type number
ip address ip-address mask [secondary]
ip nat outside
end

DETAILED STEPS

Command or Action Purpose Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 3

ip nat inside source static local-ip global-ip

Example:

Device[config]# ip nat inside source static 10.10.10.1 172.16.131.1

Establishes static translation between an inside local address and an inside global address.

Step 4

interface type number

Example:

Device[config]# interface ethernet 1

Specifies an interface and enters the interface configuration mode.

Step 5

ip address ip-address mask [secondary]

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

Sets a primary IP address for an interface.

Step 6

ip nat inside

Example:

Device[config-if]# ip nat inside

Connects the interface to the inside network, which is subject to NAT.

Step 7

exit

Example:

Device[config-if]# exit

Exits interface configuration mode and returns to global configuration mode.

Step 8

interface type number

Example:

Device[config]# interface gigabitethernet 0/0/0

Specifies a different interface and enters the interface configuration mode.

Step 9

ip address ip-address mask [secondary]

Example:

Device[config-if]# ip address 172.31.232.182 255.255.255.240

Sets a primary IP address for an interface.

Step 10

ip nat outside

Example:

Device[config-if]# ip nat outside

Connects the interface to the outside network.

Step 11

end

Example:

Device# configure terminal

Exits interface configuration mode and returns to privileged EXEC mode.

Note

Conditional translation is not supported with ip nat outside source route-map configuration.

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 must access the Internet. The dynamically configured pool IP address may be used as needed. It 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 NAT device, the device adds IP aliases for them. This action enables it to 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 security issue can happen when an incoming Internet Control Message Protocol [ICMP] packet or a UDP packet that is destined for one of the aliased addresses does not have a corresponding NAT translation in the NAT table. Also, the device itself runs a corresponding service, for example, Network Time Protocol [NTP]. Such a situation can cause minor security risks.

SUMMARY STEPS

enable
configure terminal
ip nat pool name start-ip end-ip {netmask netmask | prefix-length prefix-length }
access-list access-list-number permit source [source-wildcard ]
ip nat inside source list access-list-number pool name
interface type number
ip address ip-address mask
ip nat inside
exit
interface type number
ip address ip-address mask
ip nat outside
end

DETAILED STEPS

Command or Action Purpose Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 3

ip nat pool name start-ip end-ip {netmask netmask | prefix-length prefix-length }

Example:

Device# configure terminal

Defines a pool of global addresses to be allocated as needed.

Step 4

access-list access-list-number permit source [source-wildcard ]

Example:

Device# configure terminal

Defines a standard access list permitting those addresses that are to be translated.

Step 5

ip nat inside source list access-list-number pool name

Example:

Device# configure terminal

Establishes dynamic source translation, specifying the access list defined in Step 4.

Step 6

interface type number

Example:

Device[config]# interface ethernet 1

Specifies an interface and enters an interface configuration mode.

Step 7

ip address ip-address mask

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

Sets a primary IP address for the interface.

Step 8

ip nat inside

Example:

Device[config-if]# ip nat inside

Connects the interface to the inside network, which is subject to NAT.

Step 9

exit

Example:

Device[config-if]# exit

Exits interface configuration mode and returns to global configuration mode.

Step 10

interface type number

Example:

Device[config]# ip nat inside source static 10.10.10.1 172.16.131.1

Specifies an interface and enters an interface configuration mode.

Step 11

ip address ip-address mask

Example:

Device[config]# ip nat inside source static 10.10.10.1 172.16.131.1

Sets a primary IP address for the interface.

Step 12

ip nat outside

Example:

Device[config-if]# ip nat outside

Connects the interface to the outside network.

Step 13

end

Example:

Device# configure terminal

Exits interface configuration mode and returns to privileged EXEC mode.

Using NAT to Allow Internal Users Access to the Internet

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.

SUMMARY STEPS

enable
configure terminal
ip nat pool name start-ip end-ip {netmask netmask | prefix-length prefix-length }
access-list access-list-number permit source [source-wildcard ]
ip nat inside source list access-list-number pool name overload
interface type number
ip address ip-address mask
ip nat inside
exit
interface type number
ip address ip-address mask
ip nat outside
end

DETAILED STEPS

Command or Action Purpose Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 3

ip nat pool name start-ip end-ip {netmask netmask | prefix-length prefix-length }

Example:

Device[config]# ip nat inside source static 10.10.10.1 172.16.131.1

Defines a pool of global addresses to be allocated as needed.

Step 4

access-list access-list-number permit source [source-wildcard ]

Example:

Device[config]# ip nat inside source static 10.10.10.1 172.16.131.1

Defines a standard access list permitting those addresses that are to be translated.

The access list must permit only those addresses that are to be translated. [Remember that there is an implicit “deny all” at the end of each access list.] Use of an access list that is too permissive can lead to unpredictable results.

Step 5

ip nat inside source list access-list-number pool name overload

Example:

Device[config]# ip nat inside source static 10.10.10.1 172.16.131.1

Establishes dynamic source translation with overloading, specifying the access list defined in Step 4.

Step 6

interface type number

Example:

Device[config]# interface ethernet 1

Specifies an interface and enters the interface configuration mode.

Step 7

ip address ip-address mask

Example:

Device[config]# interface ethernet 1

Sets a primary IP address for the interface.

Step 8

ip nat inside

Example:

Device[config-if]# ip nat inside

Connects the interface to the inside network, which is subject to NAT.

Step 9

exit

Example:

Device[config-if]# exit

Exits interface configuration mode and returns to global configuration mode.

Step 10

interface type number

Example:

Device[config]# ip nat inside source static 10.10.10.1 172.16.131.1

Specifies an interface and enters the interface configuration mode.

Step 11

ip address ip-address mask

Example:

Device[config]# interface ethernet 1

Sets a primary IP address for the interface.

Step 12

ip nat outside

Example:

Device[config-if]# ip nat outside

Connects the interface to the outside network.

Step 13

end

Example:

Device# configure terminal

Exits interface configuration mode and returns to privileged EXEC mode.

Configuring Address Translation Timeouts

You can configure address translation timeouts that is based on your NAT configuration.

By default, dynamic address translations time out after a period of remaining idle. 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.

Note

On Catalyst 6500 Series Switches, when the NAT translation is done in the hardware, timers are reset every 100 seconds or once the set timeout value is reached.

Changing the Translation Timeout

By default, dynamic address translations time out after some period of remaining idle. 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 that are described in this section. If you must quickly free your global IP address for a dynamic configuration, configure a shorter timeout than the default timeout. You can do it by using the ip nat translation timeout command. However, the configured timeout is longer than the other timeouts configured using commands specified in the following task. If a finish [FIN] packet does not close a TCP session properly from both sides or during a reset, change the default TCP timeout. You can do it by using the ip nat translation tcp-timeout command.

When you change the default timeout using the ip nat translation timeout command, the timeout that you configure overrides the default TCP and UDP timeout values, unless you explicitly configure the TCP timeout value [using the ip nat translation tcp-timeout seconds command] or the UDP timeout value [using the ip nat translation udp-timeout seconds command].

SUMMARY STEPS

enable
configure terminal
ip nat translation seconds
ip nat translation udp-timeout seconds
ip nat translation dns-timeout seconds
ip nat translation tcp-timeout seconds
ip nat translation finrst-timeout seconds
ip nat translation icmp-timeout seconds
ip nat translation syn-timeout seconds
end

DETAILED STEPS

Command or Action Purpose Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 3

ip nat translation seconds

Example:

Device[config]# interface ethernet 1

[Optional] Changes the amount of time after which NAT translations time out.

The default timeout is 24 hours, and it applies to the aging time for half-entries.
The timeout configured using this command overrides the default TCP and UDP timeout values, unless explicitly configured.

Step 4

ip nat translation udp-timeout seconds

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

[Optional] Changes the UDP timeout value.

The default is 300 seconds. This default value only applies if the general IP NAT translation timeout value [using the ip nat translation seconds command] is not configured.

Step 5

ip nat translation dns-timeout seconds

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

[Optional] Changes the Domain Name System [DNS] timeout value.

Step 6

ip nat translation tcp-timeout seconds

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

[Optional] Changes the TCP timeout value.

The default is 7440 seconds. This default value only applies if the general IP NAT translation timeout value [using the ip nat translation seconds command] is not configured.

Step 7

ip nat translation finrst-timeout seconds

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

[Optional] Changes the finish and reset timeout value.

finrst-timeout —The aging time after a TCP session receives both finish-in [FIN-IN] and finish-out [FIN-OUT] requests or after the reset of a TCP session.

Step 8

ip nat translation icmp-timeout seconds

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

[Optional] Changes the ICMP timeout value.

Step 9

ip nat translation syn-timeout seconds

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

[Optional] Changes the synchronous [SYN] timeout value.

The synchronous timeout or the aging time is used only when a SYN request is received on a TCP session. When a synchronous acknowledgment [SYNACK] request is received, the timeout changes to TCP timeout.

Step 10

end

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

[Optional] Exits global configuration mode and returns to privileged EXEC mode.

Allowing Overlapping Networks to Communicate Using NAT

Tasks in this section are grouped because they perform the same action. However, the tasks are executed differently depending on the type of translation that is implemented—static 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 that are based on the following requirements:

If your IP addresses in the stub network are legitimate IP addresses belonging to another network.
If you want to communicate with those hosts or routers by using static translation.

SUMMARY STEPS

enable
configure terminal
ip nat inside source static local-ip global-ip
interface type number
ip address ip-address mask
ip nat inside
exit
interface type number
ip address ip-address mask
ip nat outside
end

DETAILED STEPS

Command or Action Purpose Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 3

ip nat inside source static local-ip global-ip

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

Establishes static translation between an inside local address and an inside global address.

Step 4

interface type number

Example:

Device[config]# interface ethernet 1

Specifies an interface and enters the interface configuration mode.

Step 5

ip address ip-address mask

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

Sets a primary IP address for the interface.

Step 6

ip nat inside

Example:

Device[config-if]# ip nat inside

Marks the interface as connected to the inside.

Step 7

exit

Example:

Device[config-if]# exit

Exits interface configuration mode and returns to global configuration mode.

Step 8

interface type number

Example:

Device[config]# ip nat inside source static 10.10.10.1 172.16.131.1

Specifies an interface and enters the interface configuration mode.

Step 9

ip address ip-address mask

Example:

Device[config]# ip nat inside source static 10.10.10.1 172.16.131.1

Sets a primary IP address for the interface.

Step 10

ip nat outside

Example:

Device[config-if]# ip nat outside

Marks the interface as connected to the outside.

Step 11

end

Example:

Device# configure terminal

[Optional] Exits interface configuration mode and returns to privileged EXEC mode.

What to Do Next

When you have completed the required configuration, go to the “Monitoring and Maintaining NAT” module.

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.
You want to communicate with those hosts or routers by using dynamic translation.

SUMMARY STEPS

enable
configure terminal
ip nat pool name start-ip end-ip {netmask netmask | prefix-length prefix-length }
access-list access-list-number permit source [source-wildcard ]
ip nat outside source list access-list-number pool name
interface type number
ip address ip-address mask
ip nat inside
exit
interface type number
ip address ip-address mask
ip nat outside
end

DETAILED STEPS

Command or Action Purpose Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 3

ip nat pool name start-ip end-ip {netmask netmask | prefix-length prefix-length }

Example:

Device[config-if]# exit

Defines a pool of global addresses to be allocated as needed.

Step 4

access-list access-list-number permit source [source-wildcard ]

Example:

Device[config-if]# exit

Defines a standard access list permitting those addresses that are to be translated.

The access list must permit only those addresses that are to be translated. [Remember that there is an implicit “deny all” at the end of each access list.] Use of an access list that is too permissive can lead to unpredictable results.

Step 5

ip nat outside source list access-list-number pool name

Example:

Device[config-if]# exit

Establishes dynamic outside source translation, specifying the access list defined in Step 4.

Step 6

interface type number

Example:

Device[config]# interface ethernet 1

Specifies an interface and enters the interface configuration mode.

Step 7

ip address ip-address mask

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

Sets a primary IP address for the interface.

Step 8

ip nat inside

Example:

Device[config-if]# ip nat inside

Marks the interface as connected to the inside.

Step 9

exit

Example:

Device[config-if]# exit

Exits interface configuration mode and returns to global configuration mode.

Step 10

interface type number

Example:

Device[config]# ip nat inside source static 10.10.10.1 172.16.131.1

Specifies an interface and enters the interface configuration mode.

Step 11

ip address ip-address mask

Example:

Device[config]# ip nat inside source static 10.10.10.1 172.16.131.1

Sets a primary IP address for the interface.

Step 12

ip nat outside

Example:

Device[config-if]# ip nat outside

Marks the interface as connected to the outside.

Step 13

end

Example:

Device# configure terminal

[Optional] Exits interface configuration mode and returns to privileged EXEC mode.

Configuring the NAT Virtual Interface

The NAT Virtual Interface feature removes the requirement to configure an interface as either NAT inside or NAT outside. An interface can be configured to use or not use NAT.

Restrictions for NAT Virtual Interface

Route maps are not supported.
NVI is not supported in a NAT on-a-stick scenario. The term NAT on-a-stick implies the use of a single physical interface of a router for translation. NVI is designed for traffic from one VPN routing and forwarding [VRF] instance to another and not for routing between subnets in a global routing table. For more information on NAT on-a-stick, see //www.cisco.com/en/US/tech/tk648/tk361/technologies_tech_note09186a0080094430.shtml.

Enabling a Dynamic NAT Virtual Interface

SUMMARY STEPS

enable
configure terminal
interface type number
ip nat enable
exit
ip nat pool name start-ip end-ipnetmask netmask add-route
ip nat source list access-list-number pool name vrf name
ip nat source list access-list-number pool name overload
end

DETAILED STEPS

Command or Action Purpose Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 3

interface type number

Example:

Device[config]# interface gigabitethernet 0/0/0

Configures an interface and enters interface configuration mode.

Step 4

ip nat enable

Example:

Device[config]# interface gigabitethernet 0/0/0

Configures an interface that connects VPNs and the Internet for NAT.

Step 5

exit

Example:

Device[config-if]# exit

Exits interface configuration mode and returns to global configuration mode.

Step 6

ip nat pool name start-ip end-ipnetmask netmask add-route

Example:

Device[config]# interface gigabitethernet 0/0/0

Configures a NAT pool and the associated mappings.

Step 7

ip nat source list access-list-number pool name vrf name

Example:

Device[config]# interface gigabitethernet 0/0/0

Configures a dynamic NVI without an inside or outside specification.

Step 8

ip nat source list access-list-number pool name overload

Example:

Device[config]# interface gigabitethernet 0/0/0

Configures an overloading NVI without an inside or outside specification.

Step 9

end

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

Exits global configuration mode and returns to privileged EXEC mode.

Enabling a Static NAT Virtual Interface

SUMMARY STEPS

enable
configure terminal
interface type number
ip nat enable
exit
ip nat source static local-ip global-ip vrf name
end

DETAILED STEPS

Command or Action Purpose Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 3

interface type number

Example:

Device[config]# interface gigabitethernet 0/0/0

Configures an interface type and enters interface configuration mode.

Step 4

ip nat enable

Example:

Device[config]# interface gigabitethernet 0/0/0

Configures an interface that connects VPNs and the Internet for NAT.

Step 5

exit

Example:

Device[config-if]# exit

Exits interface configuration mode and enters global configuration mode.

Step 6

ip nat source static local-ip global-ip vrf name

Example:

Device[config-if]# ip address 172.31.232.182 255.255.255.240

Configures a static NVI.

Step 7

end

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

[Optional] Exits global configuration mode and returns to privileged EXEC mode.

Configuring Server TCP Load Balancing

Perform this task to configure a server TCP load balancing by way of destination address rotary translation. The commands that are specified in the task allow you to map one virtual host with many real hosts. Each new TCP session opened with the virtual host is translated into a session with a different real host.

SUMMARY STEPS

enable
configure terminal
ip nat pool name start-ip end-ip {netmask netmask | prefix-length prefix-length } type rotary
access-list access-list-number permit source [source-wildcard ]
ip nat inside destination-list access-list-number pool name
interface type number
ip address ip-address mask
ip nat inside
exit
interface type number
ip address ip-address mask
ip nat outside
end

DETAILED STEPS

Command or Action Purpose Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 3

ip nat pool name start-ip end-ip {netmask netmask | prefix-length prefix-length } type rotary

Example:

Device[config-if]# ip address 172.31.232.182 255.255.255.240

Defines a pool of addresses containing the addresses of the real hosts.

Step 4

access-list access-list-number permit source [source-wildcard ]

Example:

Device[config]# ip nat inside source static 10.10.10.1 172.16.131.1

Defines an access list permitting the address of the virtual host.

Step 5

ip nat inside destination-list access-list-number pool name

Example:

Device[config-if]# ip nat outside

Establishes dynamic inside destination translation, specifying the access list defined in the prior step.

Step 6

interface type number

Example:

Device[config]# ip nat inside source static 10.10.10.1 172.16.131.1

Specifies an interface and enters the interface configuration mode.

Step 7

ip address ip-address mask

Example:

Device[config]# interface ethernet 1

Sets a primary IP address for the interface.

Step 8

ip nat inside

Example:

Device[config-if]# ip nat inside

Marks the interface as connected to the inside.

Step 9

exit

Example:

Device[config-if]# exit

Exits interface configuration mode and returns to global configuration mode.

Step 10

interface type number

Example:

Device[config-if]# ip nat outside

Specifies a different interface and enters the interface configuration mode.

Step 11

ip address ip-address mask

Example:

Device[config-if]# ip nat outside

Sets a primary IP address for the interface.

Step 12

ip nat outside

Example:

Device[config-if]# ip nat outside

Marks the interface as connected to the outside.

Step 13

end

Example:

Device# configure terminal

[Optional] Exits interface configuration mode and returns to privileged EXEC mode.

Enabling Route Maps on Inside Interfaces

Before you begin

All route maps required for use with this task must be configured before you begin the configuration task.

SUMMARY STEPS

enable
configure terminal
ip nat inside source {list {access-list-number | access-list-name } pool pool-name [overload ]| static local-ip global-ip [route-map map-name ]}
exit
show ip nat translations [verbose ]

DETAILED STEPS

Command or Action Purpose Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 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 ]}

Example:

Device# configure terminal

Enables route mapping with static NAT configured on the NAT inside interface.

Step 4

exit

Example:

Device# configure terminal

Exits global configuration mode and returns to privileged EXEC mode.

Step 5

show ip nat translations [verbose ]

Example:

Device# configure terminal

[Optional] Displays active NAT.

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. It allows 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

enable
configure terminal
ip nat pool name start-ip end-ip netmask netmask
ip nat pool name start-ip end-ip netmask netmask
ip nat inside source route-map name pool name [reversible ]
ip nat inside source route-map name pool name [reversible ]
end

DETAILED STEPS

Command or Action Purpose Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 3

ip nat pool name start-ip end-ip netmask netmask

Example:

Device# configure terminal

Defines a pool of network addresses for NAT.

Step 4

ip nat pool name start-ip end-ip netmask netmask

Example:

Device# configure terminal

Defines a pool of network addresses for NAT.

Step 5

ip nat inside source route-map name pool name [reversible ]

Example:

Device# configure terminal

Enables outside-to-inside initiated sessions to use route maps for destination-based NAT.

Step 6

ip nat inside source route-map name pool name [reversible ]

Example:

Device# configure terminal

Enables outside-to-inside initiated sessions to use route maps for destination-based NAT.

Step 7

end

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

[Optional] Exits global configuration mode and returns to privileged EXEC mode.

Configuring NAT of External IP Addresses Only

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 enterprise’s network flows through the internal network. A device that is configured for NAT translates the packet to an address that can be routed inside the internal network. If the intended destination is outside an enterprise’s network, the packet gets translated back to an external address and is sent out.

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 that is used for IPsec connections and for traffic flows.
Supports public and private network architecture with no specific route updates.

SUMMARY STEPS

enable
configure terminal
ip nat inside source {list {access-list-number | access-list-name } pool pool-name [overload ] | static network local-ip global-ip [no-payload ]}
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 ]}
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 ]}
ip nat outside source {list {access-list-number | access-list-name } pool pool-name | static local-ip global-ip [no-payload ]}
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 ]}
ip nat outside source {list {access-list-number | access-list-name } pool pool-name | static [network ] local-network-mask global-network-mask [no-payload ]}
exit
show ip nat translations [verbose ]

DETAILED STEPS

Command or Action Purpose Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 3

ip nat inside source {list {access-list-number | access-list-name } pool pool-name [overload ] | static network local-ip global-ip [no-payload ]}

Example:

Device# configure terminal

Disables the network packet translation on the inside host device.

Step 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 ]}

Example:

Device# configure terminal

Disables port packet translation on the inside host device.

Step 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 ]}

Example:

Device# configure terminal

Disables packet translation on the inside host device.

Step 6

ip nat outside source {list {access-list-number | access-list-name } pool pool-name | static local-ip global-ip [no-payload ]}

Example:

Device# configure terminal

Disables packet translation on the outside host device.

Step 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 ]}

Example:

Device# configure terminal

Disables port packet translation on the outside host device.

Step 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 ]}

Example:

Device# configure terminal

Disables network packet translation on the outside host device.

Step 9

exit

Example:

Device# configure terminal

Exits global configuration mode and returns to privileged EXEC mode.

Step 10

show ip nat translations [verbose ]

Example:

Device# configure terminal

Displays active NAT.

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 are 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 enterprise’s network, and there is no match in the NAT table for fully extended entry or 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 different from the IP address 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

enable
configure terminal
ip nat inside source static local-ip interface type number
ip nat inside source static tcp local-ip local-port interface global-port
exit
show ip nat translations [verbose ]

DETAILED STEPS

Command or Action Purpose Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 3

ip nat inside source static local-ip interface type number

Example:

Device# configure terminal

Enables static NAT on the interface.

Step 4

ip nat inside source static tcp local-ip local-port interface global-port

Example:

Device# configure terminal

[Optional] Enables the use of telnet to the device from the outside.

Step 5

exit

Example:

Device# configure terminal

Exits global configuration mode and returns to privileged EXEC mode.

Step 6

show ip nat translations [verbose ]

Example:

Device# configure terminal

[Optional] Displays active NAT.

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.

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

enable
configure terminal
interface type number
ip nat inside
exit
ip nat allow-static-host
ip nat pool name start-ip end-ip netmask netmask accounting list-name
ip nat inside source list access-list-number pool name
access-list access-list-number deny ip source
end
show ip nat translations verbose

DETAILED STEPS

Command or Action Purpose Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 3

interface type number

Example:

Device[config]# interface ethernet 1

Configures an interface and enters an interface configuration mode.

Step 4

ip nat inside

Example:

Device[config-if]# ip nat inside

Marks the interface as connected to the inside.

Step 5

exit

Example:

Device[config-if]# exit

Exits interface configuration mode and returns to global configuration mode.

Step 6

ip nat allow-static-host

Example:

Device# configure terminal

Enables static IP address support.

Dynamic Address Resolution Protocol [ARP] learning will be disabled on this interface, and NAT will control the creation and deletion of ARP entries for the static IP host.

Step 7

ip nat pool name start-ip end-ip netmask netmask accounting list-name

Example:

Device# configure terminal

Specifies an existing RADIUS profile name to be used for authentication of the static IP host.

Step 8

ip nat inside source list access-list-number pool name

Example:

Device# configure terminal

Specifies the access list and pool to be used for static IP support.

The specified access list must permit all traffic.

Step 9

access-list access-list-number deny ip source

Example:

Device# configure terminal

Removes the traffic of the device from NAT.

The source argument is the IP address of the device that supports the NAT Static IP Support feature.

Step 10

end

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

[Optional] Exits global configuration mode and returns to privileged EXEC mode.

Step 11

show ip nat translations verbose

Example:

Device# configure terminal

[Optional] Displays active NAT translations and additional information for each translation table entry, including how long ago the entry was created and used.

Examples

The following is sample output from the show ip nat translations verbose command:

Device# configure terminal

Configuring Support for ARP Ping

When the NAT entry of the static IP client times out, the NAT entry and the secure ARP entry associations are deleted for the client. The ARP Ping feature enables the NAT entry and the secure ARP entry to not be deleted when the static IP client exists in the network where the IP address is unchanged after authentication.

An ARP ping is necessary to determine static IP client existence and to restart the NAT entry timer.

SUMMARY STEPS

enable
configure terminal
ip nat pool name start-ip end-ip prefix-length prefix-length [accounting method-list-name ] [arp-ping ]
ip nat translation arp -ping -timeout [seconds ]
end

DETAILED STEPS

Command or Action Purpose Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 3

ip nat pool name start-ip end-ip prefix-length prefix-length [accounting method-list-name ] [arp-ping ]

Example:

Device# configure terminal

Defines a pool of IP addresses for NAT.

Step 4

ip nat translation arp -ping -timeout [seconds ]

Example:

Device# configure terminal

Changes the amount of time after each network address translation.

Step 5

end

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

[Optional] Exits global configuration mode and returns to privileged EXEC mode.

Configuring the Rate Limiting NAT Translation Feature

SUMMARY STEPS

enable
show ip nat translations
configure terminal
ip nat translation max-entries {number | all-vrf number | host ip-address number | list listname number | vrf name number }
end
show ip nat statistics

DETAILED STEPS

Command or Action Purpose Step 1

enable

Example:

Device# configure terminal

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

show ip nat translations

Example:

Device# configure terminal

[Optional] Displays active NAT.

A specific host, access control list, or VRF instance generating an unexpectedly high number of NAT requests may be the source of a malicious virus or worm attack.

Step 3

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 4

ip nat translation max-entries {number | all-vrf number | host ip-address number | list listname number | vrf name number }

Example:

Device# configure terminal

Configures the maximum number of NAT entries that are allowed from the specified source.

The maximum number of allowed NAT entries is 2147483647, although a typical range for a NAT rate limit is 100 to 300 entries.
When you configure a NAT rate limit for all VRF instances, each 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.

Step 5

end

Example:

Device[config-if]# ip address 10.114.11.39 255.255.255.0

Exits global configuration mode and returns to privileged EXEC mode.

Step 6

show ip nat statistics

Example:

Device# configure terminal

[Optional] Displays current NAT usage information, including NAT rate limit settings.

After setting a NAT rate limit, use the show ip nat statistics command to verify the current NAT rate limit settings. Note

The CEF counters associated with the output of the show ip nat statistics command signify the number of packets that are translated and forwarded in the SW plane. Packets that require translation are punted to the SW plane in the absence of the corresponding NF shortcuts in the HW plane. This enables SW plane to carry out the translation and program the corresponding NF shortcuts in the HW in order to facilitate the HW translation for subsequent packets that match the given flow.

A route-map based NAT rule does not maintain Half Entry mappings and this implies that every new packet flow that matches the given rule is directed to the SW plane for translation and forwarding. Such packets undergo translation in the SW plane. This in turn results in the increment of the afore mentioned CEF counters. This is an expected behavior when you employ a route-map-based NAT configuration. However, note that these packets that undergo translation in the SW result in the corresponding full flow NF shortcuts to be programmed in the HW. This is to facilitate the HW translation of subsequent packets that match the given flow.

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 that are addressed from the 10.114.11.0 network [the true 10.114.11.0 network] are translated to appear from the 10.0.1.0/24 network.

Device# configure terminal

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.

Device# configure terminal

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:

Device# configure terminal

The following example shows how only traffic local to the provider edge [PE] device running NAT is translated:

Device# configure terminal

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 is 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.

Device# configure terminal

Example: Allowing Overlapping Networks to Communicate Using NAT

Example: Configuring the NAT Virtual Interface

Example: Enabling a Static NAT Virtual Interface

Device# configure terminal

Example: Enabling a Dynamic NAT Virtual Interface

Device# configure terminal

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 exist, TCP packets from serial interface 0 [the outside interface], whose destination matches the access list, are translated to an address from the pool.

Device# configure terminal

Example: Enabling Route Maps on Inside Interfaces

Device# configure terminal

Example: Enabling NAT Route Maps Outside-to-Inside Support

The following example shows how to configure a route map A and route map B to allow outside-to-inside translation for a destination-based Network Address Translation [NAT]:

Device# configure terminal

Example: Configuring NAT of External IP Addresses Only

Device# configure terminal

Example: Configuring Support for Users with Static IP Addresses

Device# configure terminal

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:

Device# configure terminal

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:

Device# configure terminal

Example: Configuring the Rate Limiting NAT Translation Feature

The following example shows how to limit the maximum number of allowed NAT entries to 300:

Device# configure terminal

The following example shows how to limit the VRF instance named “vrf1” to 150 NAT entries:

Device# configure terminal

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

Device# configure terminal

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

Device# configure terminal

The following example shows how to limit the access control list named “vrf3” to 100 NAT entries:

Device# configure terminal

The following example shows how to limit the host at IP address 10.0.0.1 to 300 NAT entries:

Device# configure terminal

Example: Setting a Global NAT Rate Limit

The following example shows how to limit the maximum number of allowed NAT entries to 300:

Device# configure terminal

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:

Device# configure terminal

Example: Setting NAT Rate Limits for All VRF Instances

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

Device# configure terminal

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

Device# configure terminal

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:

Device# configure terminal

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:

Device# configure terminal

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.
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

Standards and RFCs

Standard/RFC

Title

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]

Technical Assistance

Description

Link

The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.

//www.cisco.com/cisco/web/support/index.html

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 2. Feature Information for Configuring NAT for IP Address Conservation

Feature Name

Releases

Feature Information

NAT Ability to Use Route Maps with Static Translation

12.2.[4]T

The NAT Ability to Use Route Maps with Static Translation feature provides a dynamic translation command that can specify a route map to be processed instead of an access list. A route map allows you to match any combination of the access list, next-hop IP address, and output interface to determine which pool to use. The ability to use route maps with static translations enables NAT multihoming capability with static address translations.

NAT Default Inside Server

12.3[13]T

The NAT Default Inside Server feature enables forwarding of packets from outside to a specified inside local address.

NAT Route Maps Outside-to-Inside Support

12.2[33]SXI5

12.3[14]T

The NAT Route Maps Outside-to-Inside Support feature enables the deployment of a NAT route map configuration that allows IP sessions to be initiated from the outside to the inside.

NAT RTSP Support Using NBAR

12.3[7]T

The NAT RTSP Support Using NBAR feature is a client/server multimedia presentation control protocol that supports multimedia application delivery. Applications that use RTSP include WMS by Microsoft, QuickTime by Apple Computer, and RealSystem G2 by RealNetworks.

NAT Static and Dynamic Route Map Name-Sharing

15.0[1]M

The NAT Static and Dynamic Route Map Name-Sharing feature provides the ability to configure static and dynamic NAT to share the same route map name, while enforcing precedence of static NAT over dynamic NAT.

NAT Static IP Support

12.3[7]T

The NAT Static IP Support feature provides support for users with static IP addresses, enabling those users to establish an IP session in a public wireless LAN environment.

NAT Translation of External IP Addresses Only

12.2[4]T

12.2[4]T2

15.0[1]S

Use the NAT Translation of External IP Addresses Only feature to configure NAT to ignore all embedded IP addresses for any application and traffic type.

NAT Virtual Interface

12.3[14]T

The NAT Virtual Interface feature removes the requirement to configure an interface as either Network Address Translation [NAT] inside or NAT outside. An interface can be configured to use or not use NAT.

Rate Limiting NAT Translation

12.3[4]T

15.0[1]S

The Rate Limiting NAT Translation feature 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.

Support for ARP Ping in a Public Wireless LAN

12.4[6]T

The Support for ARP Ping in a Public Wireless LAN feature ensures that the NAT entry and the secure ARP entry from removal when the static IP client exists in the network, where the IP address is unchanged after authentication.