Difference between revisions of "NAT Cisco IOS"

From Teknologisk videncenter
Jump to: navigation, search
m (→‎Load balancing example)
m (→‎Links)
 
(73 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
NAT Cisco IOS
 
== Network Address Translantion ==
 
== Network Address Translantion ==
−
For an explanation of NAT see Wikipedias [[Wikipedia:Network_address_translation|Network address translation]]
+
*For an explanation of NAT see Wikipedias [[Wikipedia:Network_address_translation|Network address translation]]
−
== Cisco NAT ==
+
*Cisco IOS explanation from [[Media:Cisco_IOS_nat.pdf|‎Cisco]]
−
=== Static NAT ===
+
{|
 +
|[[Image:Nat eksempel.png|600px|thumb|left|NAT eksempel med inside/outside local/global]]
 +
|}
 +
 
 +
== Order of operations ==
 +
To see in which order Cisco IOS performs operations Access-list before NAT see [[Understand_the_order_of_operations_for_Cisco_IOS]]
 +
 
 +
== Static NAT ==
 
In static NAT The Internal IP address is always translated to the same External IP address, on a one-to-one basis.<br/>
 
In static NAT The Internal IP address is always translated to the same External IP address, on a one-to-one basis.<br/>
−
==== Example of static NAT ====
+
=== Example of static NAT ===
 
In the example below, a company has acquired an Internet connection with four additional addresses 195.181.54.0/29.
 
In the example below, a company has acquired an Internet connection with four additional addresses 195.181.54.0/29.
 
*Connection Link address to internet 83.90.42.0/30
 
*Connection Link address to internet 83.90.42.0/30
−
**ISP uses 83.90.42.2/30
+
**ISP uses 83.90.42.2/32
−
**Company Router 83.90.42.1/30
+
**Company Router 83.90.42.1/32
 
*The network 195.181.54.0/29 is routed to 83.90.42.1 by the ISP
 
*The network 195.181.54.0/29 is routed to 83.90.42.1 by the ISP
 
*195.181.54.1/29 is a real IP address the company wants to use to their WEB-server
 
*195.181.54.1/29 is a real IP address the company wants to use to their WEB-server
Line 16: Line 24:
  
 
[[Image:Nat_static_cisco.png|none|600px|thumb|Cisco Static NAT example]]
 
[[Image:Nat_static_cisco.png|none|600px|thumb|Cisco Static NAT example]]
−
<pre>
+
<source lang="cli">
 
ip nat inside source static 192.168.22.110 195.181.54.1
 
ip nat inside source static 192.168.22.110 195.181.54.1
 
ip nat inside source static 192.168.22.111 195.181.54.2
 
ip nat inside source static 192.168.22.111 195.181.54.2
Line 29: Line 37:
 
  ip address 192.168.22.1 255.255.255.0
 
  ip address 192.168.22.1 255.255.255.0
 
  ip nat inside
 
  ip nat inside
−
</pre>
+
</source>
 +
=== Another example of static NAT ===
 +
Redirecting one IP address from inside to another IP address on the outside. In the example below inside uders attempt to access IP address 8.8.8.8 but are redirected to 1.1.1.1 on the outside,
 +
<source lang="cli">
 +
ip nat outside source static 1.1.1.1 8.8.8.8 extendable
 +
!
 +
interface fastethernet 0/0
 +
description Connected to ISP (Outside)
 +
ip address 83.90.42.1 255.255.255.252
 +
ip nat outside
 +
!
 +
interface fastethernet 0/1
 +
description Local private LAN (Inside)
 +
ip address 192.168.22.1 255.255.255.0
 +
ip nat inside
 +
</source>
 +
'''''Note:''''' The translation happens after Routing so there has to be a route to 8.8.8.8.
  
−
=== Dynamic NAT ===
+
== Dynamic NAT ==
−
=== Overloading ===
+
Dynamic [[NAT]] translates internal addresses to a random pool of outside addresses.
−
Overloading is often used, when you have a private internal LAN for example 192.168.1.0/24 and connect to the Internet through as ISP that lend you a Pulic IP address, through DHCP like a small [[SOHO router]].
+
=== Dynamic NAT example ===
−
==== Overloading example 1: Connection with fixed WAN IP Address ====
+
Internal addresses 192.168.1.9 to 192.168.1.14 are [[NAT|NAT'ed]] to outside 195.181.54.1 to 195.181.54.6 dynamically, not knowing which inside address are [[NAT|NAT'ed]] to which outside address.
 +
<source lang="cli">
 +
ip nat pool DYNAMIC-IP-POOL 195.181.54.1 195.181.54.6 netmask 255.255.255.248
 +
!
 +
access-list 54 permit 192.168.1.8 255.255.255.248
 +
!
 +
ip nat inside source list 54 pool DYNAMIC-IP-POOL
 +
!
 +
interface FastEthernet 0/0
 +
description Inside private network
 +
ip address 192.168.1.1
 +
ip nat inside
 +
!
 +
interface FastEthernet 0/1
 +
description Outside Connection to internet
 +
ip address dhcp
 +
ip nat outside
 +
</source>
 +
 
 +
== Overloading or PAT==
 +
Overloading or PAT - Port Address Translation - is often used, when you have a private internal LAN for example 192.168.1.0/24 and connect to the Internet through your [[ISP]] that lend you a Pulic IP address, through [[DHCP]] like a small [[SOHO router]].
 +
=== Overloading example 1: Connection with fixed WAN IP Address ===
 
*Internal private network: 192.168.1.0/24
 
*Internal private network: 192.168.1.0/24
 
*Fixed WAN IP address: 83.90.1.30/30
 
*Fixed WAN IP address: 83.90.1.30/30
−
<pre>
+
<source lang="cli">
 
interface FastEthernet0/0
 
interface FastEthernet0/0
 
  description Inside. Internal LAN
 
  description Inside. Internal LAN
Line 50: Line 95:
 
ip nat inside source list 38 interface FastEthernet0/1 overload
 
ip nat inside source list 38 interface FastEthernet0/1 overload
 
!
 
!
−
access-list 38 permit 10.0.0.0 0.0.0.255
+
access-list 38 remark Permit traffic from RFC1918 private net
−
</pre>
+
access-list 38 permit 10.0.0.0 0.255.255.255
−
==== Overloading example 2: Connection with floating WAN IP Address (DHCP) ====
+
access-list 38 permit 172.16.0.0 0.15.255.255
 +
access-list 38 permit 192.168.0.0 0.0.255.255
 +
</source>
 +
 
 +
=== Overloading example 2: Connection with floating WAN IP Address (DHCP) ===
 
*Internal private network: 192.168.1.0/24
 
*Internal private network: 192.168.1.0/24
 
*WAN Address: DHCP
 
*WAN Address: DHCP
−
<pre>
+
<source lang="cli">
 
interface FastEthernet0/0
 
interface FastEthernet0/0
 
  description Inside. Internal LAN
 
  description Inside. Internal LAN
Line 68: Line 117:
 
ip nat inside source list 38 interface FastEthernet0/1 overload
 
ip nat inside source list 38 interface FastEthernet0/1 overload
 
!
 
!
−
access-list 38 permit 10.0.0.0 0.0.0.255
+
access-list 38 remark Permit traffic from RFC1918 private net
−
</pre>
+
access-list 38 permit 10.0.0.0 0.255.255.255
−
==== Overloading example 3: Cisco Router as a SOHO Router ====
+
access-list 38 permit 172.16.0.0 0.15.255.255
 +
access-list 38 permit 192.168.0.0 0.0.255.255
 +
</source>
 +
 
 +
=== Telneting or SSH'ing to the NAT outside interface ===
 +
If you want to [[telnet]] or [[ssh]] to a routers outside interface.
 +
 
 +
<source lang="cli">
 +
interface FastEthernet 0/1
 +
ip address 83.90.47.30 255.255.255.252
 +
ip nat outside
 +
!
 +
ip nat inside source static tcp 83.90.47.30 22 interface FastEthernet0/1 22
 +
ip nat inside source static tcp 83.90.47.30 23 interface FastEthernet0/1 23
 +
</source>
 +
 
 +
If you have a floating IP Address on the outside interface, you can use a loopback IP address to connect to
 +
<source lang="cli">
 +
interface loopback 0
 +
ip address 10.10.10.1 255.255.255.255
 +
!
 +
interface FastEthernet 0/1
 +
ip address dhcp
 +
ip nat outside
 +
!
 +
ip nat inside source static tcp 10.10.10.1 22 interface FastEthernet0/1 22
 +
ip nat inside source static tcp 10.10.10.1 23 interface FastEthernet0/1 23
 +
</source>
 +
 
 +
=== Overloading example 3: Cisco Router as a SOHO Router ===
 
*Internal private network: 192.168.1.0/24 connected to fastethernet 0/0
 
*Internal private network: 192.168.1.0/24 connected to fastethernet 0/0
 
*WAN Address: DHCP client connected to fastethernet 0/1
 
*WAN Address: DHCP client connected to fastethernet 0/1
Line 76: Line 154:
 
[[image:Cisco_router_som_SOHO_router.png‎|none|600px|thumb| Principle of SOHO Router]]
 
[[image:Cisco_router_som_SOHO_router.png‎|none|600px|thumb| Principle of SOHO Router]]
  
−
NAT, PAT (overloading) and DHCP configuration  
+
NAT, PAT (overloading) and DHCP configuration. Notice firewall '''not''' configured in this example.
−
<pre>
+
<source lang="cli">
 
ip dhcp excluded-address 192.168.1.1 192.168.100.99
 
ip dhcp excluded-address 192.168.1.1 192.168.100.99
 
ip dhcp excluded-address 192.168.1.200 192.168.100.255
 
ip dhcp excluded-address 192.168.1.200 192.168.100.255
Line 100: Line 178:
 
!
 
!
 
access-list 1 permit 192.168.1.0 0.0.0.255
 
access-list 1 permit 192.168.1.0 0.0.0.255
−
</pre>
+
</source>
−
<!--  NOT YET FINISHED HeTh
 
  
 
The configration with an example of a fire-wall. Remember this config is at '''own''' risc!!
 
The configration with an example of a fire-wall. Remember this config is at '''own''' risc!!
−
<pre>
+
<source lang="cli">
−
ip dhcp excluded-address 192.168.1.1 192.168.100.99
+
ip dhcp excluded-address 192.168.1.1 192.168.1.99
−
ip dhcp excluded-address 192.168.1.200 192.168.100.255
+
ip dhcp excluded-address 192.168.1.200 192.168.1.255
 
!
 
!
 
ip dhcp pool INTERNAL-NET
 
ip dhcp pool INTERNAL-NET
Line 147: Line 224:
 
! Permit established connections
 
! Permit established connections
 
access-list 110 permit tcp any any established
 
access-list 110 permit tcp any any established
 +
</source>
 +
 +
 +
=== Having a WEB-server on the inside network ===
 +
If you want a WEB server on the internal network 192.168.1.88 to be accessed from the outside, you could issue the following nat rule.
 +
<source lang="cli">
 +
ip nat inside source static tcp 192.168.1.88 80 interface FastEthernet0/1 80
 +
</source>
 +
 +
== NAT Virtual Interface==
 +
NAT virtual interface (NVI), which removes the requirement to configure an interface as inside or outside.
 +
 +
<source lang=cli>
 +
R1(config)# <input>interface ethernet 0/0</input>
 +
R1(config-if)# <input>ip nat enable</input>
 +
R1(config-if)# <input>interface ethernet 0/1</input>
 +
R1(config-if)# <input>ip nat enable</input>
 +
R1(config-if)# <input>interface ethernet 0/2</input>
 +
R1(config-if)# <input>ip nat enable</input>
 +
 +
R1(config)# <input>access-list 10 permit 192.168.10.0 0.0.0.255</input>
 +
R1(config)# <input>ip nat pool NVI 209.165.201.5 209.165.201.10 prefix-length 27</input>
 +
R1(config)# <input>ip nat source list 10 interface Ethernet0/2 overload</input>  ! PAT
 +
R1(config)# <input>ip nat source static 172.16.10.10 209.165.201.2</input>
 +
</source>
  
−
</pre>
+
== Overlapping ==
−
-->
+
<span id="Load_Balancing"></span>
  
−
=== Overlapping ===
+
== Server load distribution - Load balancing between servers ==
−
=== Server load distribution - Load balancing between servers ===
 
 
You can load use '''nat pools''' to load balance between multiple IP addresses. Just remember a '''nat pool''' must be contiguous IP addresses.
 
You can load use '''nat pools''' to load balance between multiple IP addresses. Just remember a '''nat pool''' must be contiguous IP addresses.
−
==== Load balancing example ====
+
=== Load balancing example ===
 
Load balancing between six WEB-servers to distribute the load among them.<br/>
 
Load balancing between six WEB-servers to distribute the load among them.<br/>
 
In the real World www.tekkom.dk would for example resolve to IP Address 195.181.54.1 to which all users would connect.<br/>
 
In the real World www.tekkom.dk would for example resolve to IP Address 195.181.54.1 to which all users would connect.<br/>
Line 160: Line 261:
 
[[Image:Nat cisco load balancing.png|700px|none|thumb|Load balance heavy user access to WEB-site between six WEB-servers]]
 
[[Image:Nat cisco load balancing.png|700px|none|thumb|Load balance heavy user access to WEB-site between six WEB-servers]]
 
To load balance between several servers, you need to define a virtual IP address to which the users connect.  
 
To load balance between several servers, you need to define a virtual IP address to which the users connect.  
−
<pre>
+
<source lang="cli">
 
access-list 37 permit 195.181.54.1
 
access-list 37 permit 195.181.54.1
−
</pre>
+
</source>
 
See the full configuration below
 
See the full configuration below
−
<pre>
+
<source lang="cli">
 
ip nat pool WEB-SERVERS 192.168.22.9 192.168.22.14 netmask 255.255.255.0 type rotary
 
ip nat pool WEB-SERVERS 192.168.22.9 192.168.22.14 netmask 255.255.255.0 type rotary
 
ip nat inside destination list 37 pool WEB-SERVERS
 
ip nat inside destination list 37 pool WEB-SERVERS
Line 179: Line 280:
 
!
 
!
 
access-list 37 permit 195.181.54.1
 
access-list 37 permit 195.181.54.1
−
</pre>
+
</source>
−
== Linux IPTABLES ==
+
== NAT Sensitive protocols==
−
IPTABLES is the packet filtering and NAT solution used in many distributions of Linux for example
+
{|border=1 ;style="margin: 0 auto; text-align: center;cellpadding="5" cellspacing="0"
−
*Redhat.
+
|+ NAT Sensitive protocols and their behavior
−
*Ubunto
+
|- bgcolor=lightgrey
−
*CentOS
+
! Protocol !! Behavior
−
== FreeBSD NetFilter ==
+
|-
 +
| [[IPsec Cisco IOS|IPsec]] || NAT changes certain IP header fields  such as IP Address and the IP header checksum. This can conflict with [[IPsec Cisco IOS|IPsec]] integrity.
 +
|-
 +
| ICMP || Many ICMP packets, such as Destination Unreachable, carry embedded IP header information inside the ICMP message payload, not matching IP packet's translated address.
 +
|-
 +
| [[SIP]] || Protocols such as [[SIP]] negotiate address and port numbers at the application layer, which can become invalid through a NAT device.
 +
|}
 +
== Checking and debugging NAT ==
 +
=== current NAT translations ===
 +
To show current NAT translations use ''show ip nat translations''. See example below.
 +
<source lang="cli">
 +
Mercantec#<input>show ip nat translations</input>
 +
Pro Inside global      Inside local      Outside local      Outside global
 +
tcp 192.168.22.178:23    10.0.0.1:23          192.168.22.73:52076  192.168.22.73:52076
 +
tcp 192.168.22.178:23    10.0.0.1:23          ---                  ---
 +
udp 192.168.22.178:161    80.166.167.96:161    ---                  ---
 +
udp 192.168.22.178:162    80.166.167.96:162    ---                  ---
 +
udp 192.168.22.178:68    192.168.22.178:68    192.168.22.73:67      192.168.22.73:67
 +
icmp 192.168.22.178:512  192.168.22.178:512    58.80.117.74:512      58.80.117.74:512
 +
</source>
 +
 
 +
=== debuging NAT ===
 +
'''Be aware''' Debugging NAT on a heavily loaded Router could slow down the Router and overload the connection to the monitor terminal.<br/>
 +
'''NOTE:''' To stop the debug in flight, enter '''no debug all''' and press <ENTER>. This will stop debugging. Even if you cant see the command on the screen, because of to much debugging output. It will stop.
 +
<source lang="cli">
 +
Mercantec#<input>terminal monitor</input>
 +
Mercantec#<input>debug ip nat</input>
 +
IP NAT debugging is on
 +
TDC_SNMP#
 +
Mar 10 05:53:02.302: NAT: s=10.0.0.1->192.168.22.178, d=192.168.22.73 [34292]
 +
Mar 10 05:53:02.302: NAT*: s=192.168.22.73, d=192.168.22.178->10.0.0.1 [55215]
 +
Mar 10 05:53:03.886: NAT: s=10.0.0.1->192.168.22.178, d=192.168.22.73 [34293]
 +
Mar 10 05:53:03.986: NAT*: s=192.168.22.73, d=192.168.22.178->10.0.0.1 [55220]
 +
Mar 10 05:53:05.886: NAT: s=10.0.0.1->192.168.22.178, d=192.168.22.73 [34294]
 +
Mar 10 05:53:05.986: NAT*: s=192.168.22.73, d=192.168.22.178->10.0.0.1 [55224]
 +
Mar 10 05:53:07.886: NAT: s=10.0.0.1->192.168.22.178, d=192.168.22.73 [34295]
 +
Mar 10 05:53:07.986: NAT*: s=192.168.22.73, d=192.168.22.178->10.0.0.1 [55228]
 +
Mar 10 05:53:08.826: NAT: expiring 192.168.22.178 (10.0.0.1) tcp 23 (23)
 +
Mar 10 05:53:08.826: NAT: expiring 192.168.22.178 (192.168.22.178) tcp 17 (23)<input>no de</input>
 +
Mar 10 05:53:09.886: NAT: s=10.0.0.1->192.168.22.178, d=192.168.22.73 [34296]<input>bug all</input>
 +
Mar 10 05:53:09.986: NAT*: s=192.168.22.73, d=192.168.22.178->10.0.0.1 [55233]
 +
Mar 10 05:53:11.094: NAT*: s=192.168.22.73, d=192.168.22.178->10.0.0.1 [55235]
 +
Mar 10 05:53:11.094: NAT: s=10.0.0.1->192.168.22.178, d=192.168.22.73 [34297]
 +
Mar 10 05:53:11.194: NAT*: s=192.168.22.73, d=192.168.22.178->10.0.0.1 [55237]
 +
Mar 10 05:53:11.314: NAT*: s=192.168.22.73, d=192.168.22.178->10.0.0.1 [55238]
 +
Mar 10 05:53:11.318: NAT: s=10.0.0.1->192.168.22.178, d=192.168.22.73 [34298]
 +
</source>
 +
=== Is DHCP enabled ===
 +
Show ip sockets<ref>http://www.cisco.com/en/US/docs/ios/12_3/ipaddr/command/reference/ip1_s2g.html#wp1080801</ref>
 +
<source lang=cli>
 +
R1#<input>sh ip sockets</input>
 +
Proto    Remote      Port      Local      Port  In Out Stat TTY OutputIF
 +
R1#
 +
</source>
 +
Start DHCP service
 +
<source lang=cli>
 +
R1(config)#<input>service dhcp</input>
 +
R1(config)#<input>^Z</input>
 +
 
 +
R1#<input>sh ip sockets</input>
 +
Proto    Remote      Port      Local      Port  In Out Stat TTY OutputIF
 +
17 0.0.0.0            0 10.10.10.1        67  0  0 2211  0
 +
R1#
 +
</source>
 +
 
 +
= Order of operations in IOS =
 +
Sometimes you need to understand the order of operations when setting up complex configurations
 +
== Order of operations for the inside-to-outside ==
 +
 
 +
#If IPSec, then check input access list
 +
#Decryption—for Cisco Encryption Technology (CET) or IPSec
 +
#Check input access list
 +
#Check input rate limits
 +
#Input accounting
 +
#Policy routing
 +
#Routing
 +
#Redirect to Web cache
 +
#NAT inside to outside (local to global translation)
 +
#Crypto (check map and mark for encryption)
 +
#Check output access list
 +
#Inspect context-based access control (CBAC)
 +
#TCP intercept
 +
#Encryption
 +
 
 +
== Order of operations for the outside-to-inside ==
 +
 
 +
#If IPSec, then check input access list
 +
#Decryption—for CET or IPSec
 +
#Check input access list
 +
#Check input rate limits
 +
#Input accounting
 +
#NAT outside to inside (global to local translation)
 +
#Policy routing
 +
#Routing
 +
#Redirect to Web cache
 +
#Crypto (check map and mark for encryption)
 +
#Check output access list
 +
#Inspect CBAC
 +
#TCP intercept
 +
#Encryption
 +
=Links=
 +
*[[Media:NAT intro.pdf|NAT intro Power Point]]
 +
 
 +
=Q&A=
 +
Q. How many concurrent NAT sessions are supported in Cisco IOS NAT?<ref>http://www.cisco.com/c/en/us/support/docs/ip/network-address-translation-nat/26704-nat-faq-00.html</ref>
 +
 
 +
A. The NAT session limit is bounded by the amount of available DRAM in the router. Each NAT translation consumes about 312 bytes in DRAM. As a result, 10,000 translations (more than would generally be handled on a single router) consume about 3 MB. Therefore, typical routing hardware has more than enough memory to support thousands of NAT translations.
 +
 
 +
=Referencer=
 +
<references/>
 +
[[Category:Cisco]][[Category:CCNA]][[Category:CCNP]][[Category:IOS]][[Category:Network]]
 +
[[Category:CCNAv5]]
 +
<!--
 +
{{Source cli}}
 +
-->

Latest revision as of 08:11, 17 November 2022

NAT Cisco IOS

Network Address Translantion

NAT eksempel med inside/outside local/global

Order of operations

To see in which order Cisco IOS performs operations Access-list before NAT see Understand_the_order_of_operations_for_Cisco_IOS

Static NAT

In static NAT The Internal IP address is always translated to the same External IP address, on a one-to-one basis.

Example of static NAT

In the example below, a company has acquired an Internet connection with four additional addresses 195.181.54.0/29.

  • Connection Link address to internet 83.90.42.0/30
    • ISP uses 83.90.42.2/32
    • Company Router 83.90.42.1/32
  • The network 195.181.54.0/29 is routed to 83.90.42.1 by the ISP
  • 195.181.54.1/29 is a real IP address the company wants to use to their WEB-server
    • The companys WEB-server is located on the internal private network on local IP Address 192.168.22.110
  • 195.181.54.2/29 is a real IP address the company wants to use to their MAIL-server
    • The companys MAIL-server is located on the internal private network on local IP Address 192.168.22.111
Cisco Static NAT example
ip nat inside source static 192.168.22.110 195.181.54.1
ip nat inside source static 192.168.22.111 195.181.54.2
!
interface fastethernet 0/0
 description Connected to ISP (Outside)
 ip address 83.90.42.1 255.255.255.252
 ip nat outside
!
interface fastethernet 0/1
 description Local private LAN (Inside)
 ip address 192.168.22.1 255.255.255.0
 ip nat inside

Another example of static NAT

Redirecting one IP address from inside to another IP address on the outside. In the example below inside uders attempt to access IP address 8.8.8.8 but are redirected to 1.1.1.1 on the outside, 

ip nat outside source static 1.1.1.1 8.8.8.8 extendable
!
interface fastethernet 0/0
 description Connected to ISP (Outside)
 ip address 83.90.42.1 255.255.255.252
 ip nat outside
!
interface fastethernet 0/1
 description Local private LAN (Inside)
 ip address 192.168.22.1 255.255.255.0
 ip nat inside

Note: The translation happens after Routing so there has to be a route to 8.8.8.8.

Dynamic NAT

Dynamic NAT translates internal addresses to a random pool of outside addresses.

Dynamic NAT example

Internal addresses 192.168.1.9 to 192.168.1.14 are NAT'ed to outside 195.181.54.1 to 195.181.54.6 dynamically, not knowing which inside address are NAT'ed to which outside address. 

ip nat pool DYNAMIC-IP-POOL 195.181.54.1 195.181.54.6 netmask 255.255.255.248
!
access-list 54 permit 192.168.1.8 255.255.255.248
!
ip nat inside source list 54 pool DYNAMIC-IP-POOL
!
interface FastEthernet 0/0
 description Inside private network
 ip address 192.168.1.1
 ip nat inside
!
interface FastEthernet 0/1
 description Outside Connection to internet
 ip address dhcp
 ip nat outside

Overloading or PAT

Overloading or PAT - Port Address Translation - is often used, when you have a private internal LAN for example 192.168.1.0/24 and connect to the Internet through your ISP that lend you a Pulic IP address, through DHCP like a small SOHO router.

Overloading example 1: Connection with fixed WAN IP Address

  • Internal private network: 192.168.1.0/24
  • Fixed WAN IP address: 83.90.1.30/30
interface FastEthernet0/0
 description Inside. Internal LAN
 ip address 192.168.1.1 255.255.255.0
 ip nat inside
!
interface FastEthernet0/1
  description Outside: Internet connection to ISP
 ip address 83.90.1.30 255.255.255.252
 ip nat outside
!
ip nat inside source list 38 interface FastEthernet0/1 overload
!
access-list 38 remark Permit traffic from RFC1918 private net
access-list 38 permit 10.0.0.0 0.255.255.255
access-list 38 permit 172.16.0.0 0.15.255.255
access-list 38 permit 192.168.0.0 0.0.255.255

Overloading example 2: Connection with floating WAN IP Address (DHCP)

  • Internal private network: 192.168.1.0/24
  • WAN Address: DHCP
interface FastEthernet0/0
 description Inside. Internal LAN
 ip address 192.168.1.1 255.255.255.0
 ip nat inside
!
interface FastEthernet0/1
  description Outside: Internet connection to ISP
 ip address dhcp
 ip nat outside
!
ip nat inside source list 38 interface FastEthernet0/1 overload
!
access-list 38 remark Permit traffic from RFC1918 private net
access-list 38 permit 10.0.0.0 0.255.255.255
access-list 38 permit 172.16.0.0 0.15.255.255
access-list 38 permit 192.168.0.0 0.0.255.255

Telneting or SSH'ing to the NAT outside interface

If you want to telnet or ssh to a routers outside interface. 

interface FastEthernet 0/1
 ip address 83.90.47.30 255.255.255.252
 ip nat outside
!
ip nat inside source static tcp 83.90.47.30 22 interface FastEthernet0/1 22
ip nat inside source static tcp 83.90.47.30 23 interface FastEthernet0/1 23

If you have a floating IP Address on the outside interface, you can use a loopback IP address to connect to 

interface loopback 0
 ip address 10.10.10.1 255.255.255.255
!
interface FastEthernet 0/1
 ip address dhcp
 ip nat outside
!
ip nat inside source static tcp 10.10.10.1 22 interface FastEthernet0/1 22
ip nat inside source static tcp 10.10.10.1 23 interface FastEthernet0/1 23

Overloading example 3: Cisco Router as a SOHO Router

  • Internal private network: 192.168.1.0/24 connected to fastethernet 0/0
  • WAN Address: DHCP client connected to fastethernet 0/1
Principle of SOHO Router

NAT, PAT (overloading) and DHCP configuration. Notice firewall not configured in this example. 

ip dhcp excluded-address 192.168.1.1 192.168.100.99
ip dhcp excluded-address 192.168.1.200 192.168.100.255
!
ip dhcp pool INTERNAL-NET
   network 192.168.1.0 255.255.255.0
   domain-name jenshansen.dk
   default-router 192.168.1.1
   import all
!
interface FastEthernet0/0
 description Inside. Internal LAN
 ip address 192.168.1.1 255.255.255.0
 ip nat inside
!
interface FastEthernet0/1
 description Outside: Internet connection to ISP
 ip address dhcp
 ip nat outside
!
ip nat inside source list 1 interface FastEthernet0/1 overload
!
access-list 1 permit 192.168.1.0 0.0.0.255

The configration with an example of a fire-wall. Remember this config is at own risc!! 

ip dhcp excluded-address 192.168.1.1 192.168.1.99
ip dhcp excluded-address 192.168.1.200 192.168.1.255
!
ip dhcp pool INTERNAL-NET
   network 192.168.1.0 255.255.255.0
   domain-name jenshansen.dk
   default-router 192.168.1.1
   import all
!
interface FastEthernet0/0
 description Inside. Internal LAN
 ip address 192.168.1.1 255.255.255.0
 ip nat inside
!
interface FastEthernet0/1
 description Outside: Internet connection to ISP
 ip address dhcp
 ip nat outside
 no ip source-route
!
ip nat inside source list 1 interface FastEthernet0/1 overload
!
access-list 1 permit 192.168.1.0 0.0.0.255
!
! Access-list 110. Incoming from Internet!
!  Add anti-spoofing entries.
access-list 110 deny ip 127.0.0.0 0.255.255.255 any
access-list 110 deny ip 192.0.2.0 0.0.0.255 any
access-list 110 deny ip 224.0.0.0 31.255.255.255 any
access-list 110 deny ip host 0.0.0.0 any
! Reject RFC1918 addresses from outside (Private)
access-list 110 deny ip 10.0.0.0 0.255.255.255 any
access-list 110 deny ip 172.16.0.0 0.15.255.255 any
access-list 110 deny ip 192.168.0.0 0.0.255.255 any
access-list 110 deny ip 169.254.0.0 0.0.255.255 any
! Permit ICMP return traffic but reject incoming
access-list 110 permit icmp any any echo-reply
access-list 110 permit icmp any any unreachable
access-list 110 permit icmp any any time-exceeded
access-list 110 deny   icmp any any
! Permit established connections
access-list 110 permit tcp any any established


Having a WEB-server on the inside network

If you want a WEB server on the internal network 192.168.1.88 to be accessed from the outside, you could issue the following nat rule. 

ip nat inside source static tcp 192.168.1.88 80 interface FastEthernet0/1 80

NAT Virtual Interface

NAT virtual interface (NVI), which removes the requirement to configure an interface as inside or outside. 

R1(config)# <input>interface ethernet 0/0</input>
R1(config-if)# <input>ip nat enable</input>
R1(config-if)# <input>interface ethernet 0/1</input>
R1(config-if)# <input>ip nat enable</input>
R1(config-if)# <input>interface ethernet 0/2</input>
R1(config-if)# <input>ip nat enable</input>

R1(config)# <input>access-list 10 permit 192.168.10.0 0.0.0.255</input>
R1(config)# <input>ip nat pool NVI 209.165.201.5 209.165.201.10 prefix-length 27</input>
R1(config)# <input>ip nat source list 10 interface Ethernet0/2 overload</input>  ! PAT
R1(config)# <input>ip nat source static 172.16.10.10 209.165.201.2</input>

Overlapping

Server load distribution - Load balancing between servers

You can load use nat pools to load balance between multiple IP addresses. Just remember a nat pool must be contiguous IP addresses.

Load balancing example

Load balancing between six WEB-servers to distribute the load among them.
In the real World www.tekkom.dk would for example resolve to IP Address 195.181.54.1 to which all users would connect.
In the figure below you see the company has six equal WEB-servers with the same content.

Load balance heavy user access to WEB-site between six WEB-servers

To load balance between several servers, you need to define a virtual IP address to which the users connect. 

access-list 37 permit 195.181.54.1

See the full configuration below 

ip nat pool WEB-SERVERS 192.168.22.9 192.168.22.14 netmask 255.255.255.0 type rotary
ip nat inside destination list 37 pool WEB-SERVERS
!
interface fastethernet 0/0
 description Connected to ISP (Outside)
 ip address 83.90.42.1 255.255.255.252
 ip nat outside
!
interface fastethernet 0/1
 description Local private LAN (Inside)
 ip address 192.168.22.1 255.255.255.0
 ip nat inside
!
access-list 37 permit 195.181.54.1

NAT Sensitive protocols

NAT Sensitive protocols and their behavior
Protocol Behavior
IPsec NAT changes certain IP header fields such as IP Address and the IP header checksum. This can conflict with IPsec integrity.
ICMP Many ICMP packets, such as Destination Unreachable, carry embedded IP header information inside the ICMP message payload, not matching IP packet's translated address.
SIP Protocols such as SIP negotiate address and port numbers at the application layer, which can become invalid through a NAT device.

Checking and debugging NAT

current NAT translations

To show current NAT translations use show ip nat translations. See example below. 

Mercantec#<input>show ip nat translations</input>
Pro Inside global      Inside local       Outside local      Outside global
tcp 192.168.22.178:23     10.0.0.1:23           192.168.22.73:52076   192.168.22.73:52076
tcp 192.168.22.178:23     10.0.0.1:23           ---                   ---
udp 192.168.22.178:161    80.166.167.96:161     ---                   ---
udp 192.168.22.178:162    80.166.167.96:162     ---                   ---
udp 192.168.22.178:68     192.168.22.178:68     192.168.22.73:67      192.168.22.73:67
icmp 192.168.22.178:512   192.168.22.178:512    58.80.117.74:512      58.80.117.74:512

debuging NAT

Be aware Debugging NAT on a heavily loaded Router could slow down the Router and overload the connection to the monitor terminal.
NOTE: To stop the debug in flight, enter no debug all and press <ENTER>. This will stop debugging. Even if you cant see the command on the screen, because of to much debugging output. It will stop. 

Mercantec#<input>terminal monitor</input>
Mercantec#<input>debug ip nat</input>
IP NAT debugging is on
TDC_SNMP#
Mar 10 05:53:02.302: NAT: s=10.0.0.1->192.168.22.178, d=192.168.22.73 [34292]
Mar 10 05:53:02.302: NAT*: s=192.168.22.73, d=192.168.22.178->10.0.0.1 [55215]
Mar 10 05:53:03.886: NAT: s=10.0.0.1->192.168.22.178, d=192.168.22.73 [34293]
Mar 10 05:53:03.986: NAT*: s=192.168.22.73, d=192.168.22.178->10.0.0.1 [55220]
Mar 10 05:53:05.886: NAT: s=10.0.0.1->192.168.22.178, d=192.168.22.73 [34294]
Mar 10 05:53:05.986: NAT*: s=192.168.22.73, d=192.168.22.178->10.0.0.1 [55224]
Mar 10 05:53:07.886: NAT: s=10.0.0.1->192.168.22.178, d=192.168.22.73 [34295]
Mar 10 05:53:07.986: NAT*: s=192.168.22.73, d=192.168.22.178->10.0.0.1 [55228]
Mar 10 05:53:08.826: NAT: expiring 192.168.22.178 (10.0.0.1) tcp 23 (23)
Mar 10 05:53:08.826: NAT: expiring 192.168.22.178 (192.168.22.178) tcp 17 (23)<input>no de</input>
Mar 10 05:53:09.886: NAT: s=10.0.0.1->192.168.22.178, d=192.168.22.73 [34296]<input>bug all</input>
Mar 10 05:53:09.986: NAT*: s=192.168.22.73, d=192.168.22.178->10.0.0.1 [55233]
Mar 10 05:53:11.094: NAT*: s=192.168.22.73, d=192.168.22.178->10.0.0.1 [55235]
Mar 10 05:53:11.094: NAT: s=10.0.0.1->192.168.22.178, d=192.168.22.73 [34297]
Mar 10 05:53:11.194: NAT*: s=192.168.22.73, d=192.168.22.178->10.0.0.1 [55237]
Mar 10 05:53:11.314: NAT*: s=192.168.22.73, d=192.168.22.178->10.0.0.1 [55238]
Mar 10 05:53:11.318: NAT: s=10.0.0.1->192.168.22.178, d=192.168.22.73 [34298]

Is DHCP enabled

Show ip sockets[1] 

R1#<input>sh ip sockets</input>
Proto    Remote      Port      Local       Port  In Out Stat TTY OutputIF
R1#

Start DHCP service 

R1(config)#<input>service dhcp</input>
R1(config)#<input>^Z</input>

R1#<input>sh ip sockets</input>
Proto    Remote      Port      Local       Port  In Out Stat TTY OutputIF
 17 0.0.0.0             0 10.10.10.1         67   0   0 2211   0
R1#

Order of operations in IOS

Sometimes you need to understand the order of operations when setting up complex configurations

Order of operations for the inside-to-outside

  1. If IPSec, then check input access list
  2. Decryption—for Cisco Encryption Technology (CET) or IPSec
  3. Check input access list
  4. Check input rate limits
  5. Input accounting
  6. Policy routing
  7. Routing
  8. Redirect to Web cache
  9. NAT inside to outside (local to global translation)
  10. Crypto (check map and mark for encryption)
  11. Check output access list
  12. Inspect context-based access control (CBAC)
  13. TCP intercept
  14. Encryption

Order of operations for the outside-to-inside

  1. If IPSec, then check input access list
  2. Decryption—for CET or IPSec
  3. Check input access list
  4. Check input rate limits
  5. Input accounting
  6. NAT outside to inside (global to local translation)
  7. Policy routing
  8. Routing
  9. Redirect to Web cache
  10. Crypto (check map and mark for encryption)
  11. Check output access list
  12. Inspect CBAC
  13. TCP intercept
  14. Encryption

Links

Q&A

Q. How many concurrent NAT sessions are supported in Cisco IOS NAT?[2]

A. The NAT session limit is bounded by the amount of available DRAM in the router. Each NAT translation consumes about 312 bytes in DRAM. As a result, 10,000 translations (more than would generally be handled on a single router) consume about 3 MB. Therefore, typical routing hardware has more than enough memory to support thousands of NAT translations.

Referencer

  1. ↑ http://www.cisco.com/en/US/docs/ios/12_3/ipaddr/command/reference/ip1_s2g.html#wp1080801
  2. ↑ http://www.cisco.com/c/en/us/support/docs/ip/network-address-translation-nat/26704-nat-faq-00.html
Retrieved from "http://mars.merhot.dk/w/index.php?title=NAT_Cisco_IOS&oldid=40678"