All access lists required for use with the tasks in this module should be configured prior to beginning the configuration task. For information about how to configure an access list, refer to the IP Access List Sequence Numbering document.

Note	If you specify an access list with a NAT command, NAT will not support the commonly used permit ip any any command in the access list.

Before configuring NAT in your network, it is important to understand on which interfaces NAT will be configured and for what purposes. The requirements listed below would help you to decide on how to configure and use NAT:

1. Define the NAT inside and outside interfaces if:
   • Users exist off multiple interfaces.
   • There are multiple interfaces connecting to the Internet.
2. 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.
   • Redirect TCP traffic to another TCP port or address.
   • To use NAT during a network transition.
   • Allow overlapping networks to communicate.
   • Allow networks with different address schemes to communicate.
   • Allow the use of an application level gateway.

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 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 are hidden, a degree of security is established. Cisco IOS 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 the concern for addressing changes at the LAN or Internet interface.

Cisco IOS 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 routers for IP address simplification and conservation. In addition, Cisco IOS 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 those few routers on which NAT will be configured.

Two key problems facing the Internet are the depletion of IP address space and the scaling in routing. 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.

Beginning with Cisco IOS Release 12.1(5)T, 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 IOS NAT configuration without any static configuration. Full support for NetMeeting Directory (Internet Locator Service) is also provided through Cisco IOS NAT.

A router 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 router between a stub domain and the backbone. When a packet is leaving the domain, NAT translates the locally significant source address into a globally unique address. When a packet is entering 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 the software 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.

NAT can be used in the following scenarios:

• When you want to connect to the Internet, but not all of your hosts have globally unique IP addresses. NAT enables private IP internetworks that use nonregistered IP addresses to connect to the Internet. NAT is configured on the router 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 the 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. 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 no longer in use.
• When you must change your internal addresses. Instead of changing them, which can be a considerable amount of work, you can translate them by using NAT.
• When you want to do 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.

The term inside in a 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 (knows 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, outside refers to those networks to which the stub network connects, and which are generally not under the control of the organization. Hosts in outside networks can also be subject to translation, and thus have local and global addresses.

NAT uses the following definitions:

• Inside local address--The IP address that is assigned to a host on the inside network. The address is probably not a legitimate IP address assigned by the NIC or service provider.
• 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 routable on the inside.
• Outside global address--The 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.

• Inside Source Address Translation
  
• Inside Global Addresses Overloading
  

NAT operates on a router--generally connecting only two networks--and 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.

NAT types 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--a form of dynamic NAT--maps 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 PAT (NAT overload), thousands of users can be connected to the Internet using only one real global IP address.

NAT is used to translate your IP addresses, if your IP addresses are not legal or officially assigned IP addresses. Perhaps you chose IP addresses that officially belong to another network. When an IP address is used both illegally and legally, it is called index overlapping. You can use NAT to translate inside addresses that overlap with outside addresses.

The figure below shows how NAT translates overlapping networks.

Figure 3

NAT Translating Overlapping Addresses

The router performs the following tasks when translating overlapping addresses:

1. The user at host 10.1.1.1 opens a connection to host C by name, requesting a name-to-address lookup from a DNS server.
2. The router 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 router creates a simple translation entry mapping the overlapping address 10.1.1.3 to an address from a separately configured, outside local address pool.

The router examines every DNS reply from everywhere, ensuring that the IP address is not in the stub network. If it is, the router translates the address.

1. Host 10.1.1.1 opens a connection to 172.16.0.3.
2. The router sets up a translations mapping of the inside local and global addresses to each other and the outside global and local addresses to each other.
3. The router 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 router 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.

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

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. The standard interfaces connected to the various networks will be configured to identify that 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

NAT Virtual Interface has the following benefits:

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

• TCP Load Distribution for NAT
  

For NAT, a route map must be processed instead of an access list. A route map allows you to match any combination of 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 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. In order 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 that of the dynamic NAT route map name.

Benefits of Using Route Maps for Address Translation are the following:

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

A public wireless LAN provides users of mobile computing devices with wireless connections to a public network, such as the Internet.

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 the UDP. Generally, the RADIUS protocol is considered a connectionless service. Issues related to server availability, retransmission, and timeouts are handled by the RADIUS-enabled devices rather than the transmission protocol.

RADIUS is a client/server 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 service to the user. A RADIUS server can act as a proxy client to other RADIUS servers or other kinds of authentication servers.

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 router or web server. DoS attacks can come from a malicious user or from a computer infected with a virus or worm. When the attack comes from many different sources at once, such as when a virus or worm has infected many computers, it is known as a distributed denial-of-service (DDoS) attack. Such DDoS attacks can spread rapidly and involve thousands of systems.

Viruses and worms are 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 VRF instances.

Inside source address can be configured for static or dynamic translations. Perform one of the following tasks depending on your requirements:

• Configuring Static Translation of Inside Source Addresses
  
• Configuring Dynamic Translation of Inside Source Addresses
  

1.    enable

2.    configure terminal

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 overload

6.    interface type number

7.    ip address ip-address mask

8.    ip nat inside

9.    exit

10.    interface type number

11.    ip address ip-address mask

12.    ip nat outside

13.    end

This section describes how to change the default translation timeout when overloading is configured and not configured. You can use the configuration that is applicable to your specific NAT configuration.

• Changing the Translation Timeout
  
• Changing the Timeouts When Overloading Is Configured
  

The tasks in this section are grouped because they perform the same action but 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 is implemented.

• Configuring Static Translation of Overlapping Networks
  
• What to Do Next
  
• Configuring Dynamic Translation of Overlapping Networks
  

The NAT Virtual Interface (NVI) 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.

This section contains the following procedure:

• Restrictions for NAT Virtual Interface
  
• Enabling a Dynamic NAT Virtual Interface
  
• Enabling a Static NAT Virtual Interface
  

1.    enable

2.    configure terminal

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

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

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

6.    interface type number

7.    ip address ip-address mask

8.    ip nat inside

9.    exit

10.    interface type number

11.    ip address ip-address mask

12.    ip nat outside

13.    end

1.    enable

2.    configure terminal

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]

The NAT Route Maps Outside-to-Inside 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. Perform this task to enable the NAT Route Maps Outside-to-Inside Support feature.

An initial session from inside-to-outside is required to trigger a NAT. New translation sessions can then be initiated from 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. No additional entries are created to allow the return traffic for a route-map-based dynamic entry unless the reversible keyword is used with the ip nat inside source command.

Note

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. Match-interface or Match Next-hop is not supported for reversible route maps. 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. >

1.    enable

2.    configure terminal

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

1.    enable

2.    configure terminal

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 | upd} 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 [overload] | static local-ip global-ip [no-payload]}

7.    ip nat outside source {list {access-list-number | access-list-name} pool pool-name [overload] | static {tcp | upd} 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 [overload] | static [network] local-network-mask global-network-mask [no-payload]}

9.    exit

10.    show ip nat translations [verbose]

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 the packets are not dropped. For online games, outside traffic comes on a different UDP.

Dynamic mapping and interface overload can be configured for the PC traffic and also for the gaming device. If a packet is destined for the 806 interface from outside an enterprise’s network and there 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 the feature to configure gaming devices with an IP address that is different from that of the PC. To avoid unwanted traffic or attacks, use access lists. For traffic going from the PC to the outside world, it is better to use a route map so that extended entries are created. >

1.    enable

2.    configure terminal

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

6.    show ip nat translations [verbose]

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 in order 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 re-enable RTSP on a NAT router if this configuration has been disabled.

1.    enable

2.    configure terminal

3.    interface type number

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

Router# show
 ip
 nat
 translations
 verbose
--- 172.16.0.0 10.1.1.1           ---                ---
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

1.    enable

2.    configure terminal

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

4.    ip nat translation arp -ping-timeout [seconds]

5.    end

1.    enable

2.    show ip nat translations

3.    configure terminal

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

• Example Configuring NAT Static IP Support
  
• Example Creating a RADIUS Profile for NAT Static IP Support
  

• Example Setting a Global NAT Rate Limit
  
• Example Setting NAT Rate Limits for a Specific VRF Instance
  
• Example Setting NAT Rate Limits for All VRF Instances
  
• Example Setting NAT Rate Limits for Access Control Lists
  
• Example Setting NAT Rate Limits for an IP Address