Table Of Contents
Prerequisites for NAT - Static IP Support
Information About NAT - Static IP Support
Benefits of NAT - Static IP Support
How to Configure NAT - Static IP Support
Configuration Examples for NAT - Static IP Support
Configuring NAT - Static IP Support: Example
Creating a RADIUS Profile for NAT - Static IP Support: Example
NAT - Static IP Support
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.
Release Modification12.3(2)XE
This feature was introduced.
12.3(7)T
This feature was integrated into Cisco IOS Software Release 12.3(7)T.
Feature History for NAT - Static IP Support
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Prerequisites for NAT - Static IP Support
•
Information About NAT - Static IP Support
•
How to Configure NAT - Static IP Support
•
Configuration Examples for NAT - Static IP Support
Prerequisites for NAT - Static IP Support
Before enabling static IP support for Network Address Translation (NAT), you must first enable NAT on your router and configure a RADUIS server host. For additional information on NAT and RADUIS configuration, see the "Related Documents" section.
Information About NAT - Static IP Support
To configure the NAT - Static IP Support feature, you should understand the following concepts:
•
Benefits of NAT - Static IP Support
Benefits of NAT - Static IP Support
The NAT - Static IP Support feature extends the capabilities of Public Wireless LAN providers to support users configured with a static IP address. By configuring a router to support users with a static IP address, Public Wireless LAN providers extend their services to a greater number of potential users, which can lead to greater user satisfaction and additional revenue.
Public Wireless LAN
A Public Wireless LAN provides users of mobile computing devices with wireless connections to a public network, such as the Internet.
RADIUS
Remote Authentication Dial-In User Service (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 User Datagram Protocol (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.
How to Configure NAT - Static IP Support
This section contains the following procedures:
•
Configuring Static IP Support (required)
•
Verifying Static IP Support (optional)
Configuring Static IP Support
To configure the NAT - Static IP Support feature, perform the following steps.
SUMMARY STEPS
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
DETAILED STEPS
Verifying Static IP Support
To verify the NAT - Static IP Support feature, perform the following steps.
SUMMARY STEPS
1.
show ip nat translations verbose
DETAILED STEPS
Step 1
show ip nat translations verbose
Use this command to verify that NAT is configured to support static IP addresses, for example:
Router# show ip nat translations verbose--- 171.1.1.11 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
Configuration Examples for NAT - Static IP Support
This section provides the following configuration examples:
•
Configuring NAT - Static IP Support: Example
•
Creating a RADIUS Profile for NAT - Static IP Support: Example
Configuring NAT - Static IP Support: Example
The following example enables static IP address support for the router at 192.168.196.51:
interface ethernet 1ip nat insideip nat allow-static-hostip nat pool xyz 171.1.1.1 171.1.1.10 netmask 255.255.255.0 accounting WLAN-ACCTip nat inside source list 1 pool net-208access-list 1 deny ip 192.168.196.51Creating a RADIUS Profile for NAT - Static IP Support: Example
The following example shows how create a RADIUS profile for use with the NAT - Static IP Support feature.
aaa new-model
!
!
aaa group server radius WLAN-RADIUS
server 168.58.88.1 auth-port 1645 acct-port 1645
server 168.58.88.1 auth-port 1645 acct-port 1646
!
aaa accounting network WLAN-ACCT start-stop group WLAN-RADIUS
aaa session-id common
ip radius source-interface Ethernet3/0
radius-server host 168.58.88.1 auth-port 1645 acct-port 1646
radius-server key cisco
Additional References
The following sections provide references related to the NAT - Static IP Support feature.
Related Documents
Related Topic Document TitleConfiguring Network Address Translation (NAT)
IP NAT translation
Cisco IOS IP Command Reference, Volume 1 of 4: Addressing and Services, Release 12.3(4)T
Public Wireless LAN access routers
RADIUS
Cisco IOS Security Command Reference, Release 12.3(4)T
SSG
Service Selection Gateway, Release 12.3(4)T
Standards
Standards TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
RFCs TitleRFC 2663
IP Network Address Translator (NAT) Terminology and Considerations
RFC 3022
Traditional IP Network Address Translator (Traditional NAT)
Technical Assistance
Command Reference
This section documents only modified commands.
Modified Commands
debug ip nat
To display information about IP packets translated by the IP Network Address Translation (NAT) feature, use the debug ip nat command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip nat [access-list | detailed | h323 | ipsec | port | pptp | route | sip | skinny | vrf | wlan-nat]
no debug ip nat [access-list | detailed | h323 | ipsec | port | pptp | route | sip | skinny | vrf | wlan-nat]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The NAT feature reduces the need for unique, registered IP addresses. It can also save private network administrators from needing to renumber hosts and routers that do not conform to global IP addressing.
Use the debug ip nat command to verify the operation of the NAT feature by displaying information about every packet that is translated by the router. The debug ip nat detailed command generates a description of each packet considered for translation. This command also displays information about certain errors or exceptional conditions, such as the failure to allocate a global address. To display messages related to the processing of H.225 signaling and H.245 messages, use the debug ip nat h323 command. To display messages related to the processing of SIP messages, use the debug ip nat sip command. To display messages related to the processing of VRF messages, use the debug ip nat vrf command.
CautionBecause the debug ip nat command generates a substantial amount of output, use it only when traffic on the IP network is low, so that other activity on the system is not adversely affected.
Examples
The following is sample output from the debug ip nat command. In this example, the first two lines show the debugging output produced by a Domain Name System (DNS) request and reply. The remaining lines show the debugging output from a Telnet connection from a host on the inside of the network to a host on the outside of the network. All Telnet packets, except for the first packet, were translated in the fast path, as indicated by the asterisk (*).
Router# debug ip natNAT: s=192.168.1.95->172.31.233.209, d=172.31.2.132 [6825]NAT: s=172.31.2.132, d=172.31.233.209->192.168.1.95 [21852]NAT: s=192.168.1.95->172.31.233.209, d=172.31.1.161 [6826]NAT*: s=172.31.1.161, d=172.31.233.209->192.168.1.95 [23311]NAT*: s=192.168.1.95->172.31.233.209, d=172.31.1.161 [6827]NAT*: s=192.168.1.95->172.31.233.209, d=172.31.1.161 [6828]NAT*: s=172.31.1.161, d=172.31.233.209->192.168.1.95 [23313]NAT*: s=172.31.1.161, d=172.31.233.209->192.168.1.95 [23325]Table 1 describes the significant fields shown in the display.
The following is sample output from the debug ip nat detailed command. In this example, the first two lines show the debugging output produced by a DNS request and reply. The remaining lines show the debugging output from a Telnet connection from a host on the inside of the network to a host on the outside of the network. In this example, the inside host 192.168.1.95 was assigned the global address 172.31.233.193.
Router# debug ip nat detailedNAT: i: udp (192.168.1.95, 1493) -> (172.31.2.132, 53) [22399]NAT: o: udp (172.31.2.132, 53) -> (172.31.233.193, 1493) [63671]NAT*: i: tcp (192.168.1.95, 1135) -> (172.31.2.75, 23) [22400]NAT*: o: tcp (172.31.2.75, 23) -> (172.31.233.193, 1135) [22002]NAT*: i: tcp (192.168.1.95, 1135) -> (172.31.2.75, 23) [22401]NAT*: i: tcp (192.168.1.95, 1135) -> (172.31.2.75, 23) [22402]NAT*: o: tcp (172.31.2.75, 23) -> (172.31.233.193, 1135) [22060]NAT*: o: tcp (172.31.2.75, 23) -> (172.31.233.193, 1135) [22071]The following is sample output from the debug ip nat h323 command. In this example, an H.323 call is established between two hosts, one host on the inside and the other host on the outside. The debug displays the H.323 messages names that NAT recognizes and the embedded IP addresses contained in those messages.
Router# debug ip nat h323NAT:H225:[0] processing a Setup messageNAT:H225:[0] found Setup sourceCallSignallingNAT:H225:[0] fix TransportAddress addr=192.168.122.50 port=11140NAT:H225:[0] found Setup fastStartNAT:H225:[0] Setup fastStart PDU length:18NAT:H245:[0] processing OpenLogicalChannel message, forward channelnumber 1NAT:H245:[0] found OLC forward mediaControlChannelNAT:H245:[0] fix TransportAddress addr=192.168.122.50 port=16517NAT:H225:[0] Setup fastStart PDU length:29NAT:H245:[0] processing OpenLogicalChannel message, forward channelnumber 1NAT:H245:[0] found OLC reverse mediaChannelNAT:H245:[0] fix TransportAddress addr=192.168.122.50 port=16516NAT:H245:[0] found OLC reverse mediaControlChannelNAT:H245:[0] fix TransportAddress addr=192.168.122.50 port=16517NAT:H225:[1] processing an Alerting messageNAT:H225:[1] found Alerting fastStartNAT:H225:[1] Alerting fastStart PDU length:25NAT:H245:[1] processing OpenLogicalChannel message, forward channelTable 2 describes the significant fields shown in the display.
The following is sample output from the debug ip nat ipsec command:
Router# debug ip nat ipsec5d21h:NAT:new IKE going In->Out, source addr 192.168.122.35, destination addr 192.168.22.20, initiator cookie0x9C42065D5d21h:NAT:IPSec:created In->Out ESP translation IL=192.168.122.35 SPI=0xAAE32A0A, IG=192.168.22.40, OL=192.168.22.20,OG=192.168.22.205d21h:NAT:IPSec:created Out->In ESP translation OG=192.168.22.20 SPI=0xA64B5BB6, OL=192.168.22.20, IG=192.168.22.40,IL=192.168.122.355d21h:NAT:new IKE going In->Out, source addr 192.168.122.20, destination addr 192.168.22.20, initiator cookie0xC91738FF5d21h:NAT:IPSec:created In->Out ESP translation IL=192.168.122.20 SPI=0x3E2E1B92, IG=192.168.22.40, OL=192.168.22.20,OG=192.168.22.205d21h:NAT:IPSec:Inside host (IL=192.168.122.20) trying to open an ESP connection to Outside host (OG=192.168.22.20),wait for Out->In reply5d21h:NAT:IPSec:created Out->In ESP translation OG=192.168.22.20 SPI=0x1B201366, OL=192.168.22.20, IG=192.168.22.40,IL=192.168.122.20The following is sample output from the debug ip nat sip command. In this example, one IP phone registers with a Cisco SIP proxy and then calls another IP phone. The debug output displays the SIP messages that NAT recognizes and the embedded IP addresses contained in those messages.
Router# debug ip nat sipNAT:SIP:[0] processing REGISTER messageNAT:SIP:[0] translated embedded address192.168.122.3->2.2.2.2NAT:SIP:[0] translated embedded address192.168.122.3->2.2.2.2NAT:SIP:[0] message body foundNAT:SIP:[0] found address/port in SDP body:192.168.122.2020332NAT:SIP:[1] processing SIP/2.0 100 Trying reply messageNAT:SIP:[1] translated embedded address2.2.2.2->192.168.122.3NAT:SIP:[1] processing SIP/2.0 200 OK reply messageNAT:SIP:[1] translated embedded address2.2.2.2->192.168.122.3NAT:SIP:[1] translated embedded address2.2.2.2->192.168.122.3NAT:SIP:[1] processing INVITE messageNAT:SIP:[1] translated embedded address2.2.2.2->192.168.122.3NAT:SIP:[1] message body foundNAT:SIP:[1] found address/port in SDP body:192.168.22.20Table 3 describes the significant fields shown in the display.
The following is sample output from the debug ip nat vrf command:
Router# debug ip nat vrf6d00h:NAT:address not stolen for 192.168.121.113, proto 1 port 72246d00h:NAT:creating portlist proto 1 globaladdr 2.2.2.106d00h:NAT:Allocated Port for 192.168.121.113 -> 2.2.2.10:wanted 7224 got 72246d00h:NAT:i:icmp (192.168.121.113, 7224) -> (168.58.88.2, 7224) [2460]6d00h:NAT:s=192.168.121.113->2.2.2.10, d=168.58.88.2 [2460] vrf=> shop6d00h:NAT*:o:icmp (168.58.88.2, 7224) -> (2.2.2.10, 7224) [2460] vrf=> shop6d00h:NAT*:s=168.58.88.2, d=2.2.2.10->192.168.121.113 [2460] vrf=> shop6d00h:NAT:Allocated Port for 192.168.121.113 -> 2.2.2.10:wanted 7225 got 72256d00h:NAT:i:icmp (192.168.121.113, 7225) -> (168.58.88.2, 7225) [2461]6d00h:NAT:s=192.168.121.113->2.2.2.10, d=168.58.88.2 [2461] vrf=> shop6d00h:NAT*:o:icmp (168.58.88.2, 7225) -> (2.2.2.10, 7225) [2461] vrf=> shop6d00h:NAT*:s=168.58.88.2, d=2.2.2.10->192.168.121.113 [2461] vrf=> shop6d00h:NAT:Allocated Port for 192.168.121.113 -> 2.2.2.10:wanted 7226 got 72266d00h:NAT:i:icmp (192.168.121.113, 7226) -> (168.58.88.2, 7226) [2462]6d00h:NAT:s=192.168.121.113->2.2.2.10, d=168.58.88.2 [2462] vrf=> shopTable 4 describes the significant fields shown in the display.
Table 4 debug ip nat vrf Field Descriptions
Field Descriptionvrf=>
Indicates that NAT is applied to a particular VPN.
The following is sample output from the debug ip nat wlan-nat command:
Router# debug ip nat wlan-natWLAN-NAT: Creating secure ARP entry (10.1.1.1,0010.7bc2.9ff6)WLAN-NAT: Triggered Acct Start for (171.1.1.10,0010.7bc2.9ff6)WLAN-NAT: Extracting addr:171.1.1.10,input_idb:Ethernet1/2 from pakWLAN-NAT: Saving address:171.1.1.10,input_idb:Ethernet1/2 in pakAfter the WLAN-entry times out, the following debugs will be seen:
Router# debug ip nat wlan-natWLAN-NAT: Removing secure arp entry (10.1.1.1,0010.7bc2.9ff6)WLAN-NAT: triggered Acct Stop for (171.1.1.10,0010.7bc2.9ff6)Table 5 describes the significant fields shown in the display.
Related Commands
ip nat
To designate that traffic originating from or destined for the interface is subject to Network Address Translation (NAT), to enable NAT logging, or to enable static IP address support, use the ip nat command in interface configuration mode. To prevent the interface from being able to translate or log, use the no form of this command.
ip nat [{inside | outside} | log | translations | syslog | allow-static-host]
no ip nat [{inside | outside} | log | translations | syslog | allow-static-host]
Syntax Description
Defaults
Traffic leaving or arriving at this interface is not subject to NAT.
Command Modes
Interface configuration
Command History
Release Modification11.2
This command was introduced.
12.3(2)XE
The allow-static-host keyword was added.
12.3(7)T
This command was implemented in Cisco IOS Release 12.3(7)T.
Usage Guidelines
Only packets moving between inside and outside interfaces can be translated. You must specify at least one inside interface and outside interface for each border router where you intend to use NAT.
When static IP address support is enabled with the ip nat allow-static-host command, Cisco IOS software will provide a working IP address within the Public Wireless LAN to users configured with a static IP address.
Examples
The following example translates between inside hosts addressed from either the 192.168.1.0 or 192.168.2.0 network to the globally unique 171.69.233.208/28 network:
ip nat pool net-208 171.69.233.208 171.69.233.223 prefix-length 28ip nat inside source list 1 pool net-208!interface ethernet 0ip address 171.69.232.182 255.255.255.240ip nat outside!interface ethernet 1ip address 192.168.1.94 255.255.255.0ip nat inside!access-list 1 permit 192.168.1.0 0.0.0.255access-list 1 permit 192.168.2.0 0.0.0.255The following example enables static IP address support for the router at 192.168.196.51:
interface ethernet 1ip nat insideip nat allow-static-hostip nat pool xyz 171.1.1.1 171.1.1.10 netmask 255.255.255.0 accounting WLAN-ACCTip nat inside source list 1 pool net-208access-list 1 deny ip 192.168.196.51Related Commands
ip nat pool
To define a pool of IP addresses for Network Address Translation (NAT), use the ip nat pool command in global configuration mode. To remove one or more addresses from the pool, use the no form of this command.
ip nat pool name start-ip end-ip {netmask netmask | prefix-length prefix-length} [type rotary] | [accounting list-name]
no ip nat pool name start-ip end-ip {netmask netmask | prefix-length prefix-length} [type rotary] | [accounting list-name]
Syntax Description
Defaults
No pool of addresses is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
This command defines a pool of addresses using start address, end address, and either netmask or prefix length. The pool could define an inside global pool, an outside local pool, or a rotary pool.
Examples
The following example translates between inside hosts addressed from either the 192.168.1.0 or 192.168.2.0 network to the globally unique 171.69.233.208/28 network:
ip nat pool net-208 171.69.233.208 171.69.233.223 prefix-length 28ip nat inside source list 1 pool net-208!interface ethernet 0ip address 171.69.232.182 255.255.255.240ip nat outside!interface ethernet 1ip address 192.168.1.94 255.255.255.0ip nat inside!access-list 1 permit 192.168.1.0 0.0.0.255access-list 1 permit 192.168.2.0 0.0.0.255Related Commands
Copyright © 2003 Cisco Systems, Inc. All rights reserved.


