Demonstration: Dynamic NAT for Network Address Translation

Demonstration: Dynamic NAT for Network Address Translation

Join the group for technical exchange and Q & amp; A: 1952289

Demonstration objectives:Use Dynamic NAT to translate private network addresses.

Demo environment:As shown in figure 9.63.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/1610451313-0.png "title =" 1.png" alt = "221105645.png"/>

Demonstration Background:This demo environment maintains the basic network configuration of the PAT demo environment, and then uses dynamic NAT to translate private network addresses and access the public network, however, in this demonstration environment, only two public IP addresses are provided for private dedicated hosts, and three private network dedicated hosts exist in the network, dynamic NAT translation provides one-to-one relationship between private addresses and public addresses. In this case, one of the three private network dedicated hosts cannot access the public network, this will be confirmed in this demo environment.

Demo steps:

Step 1:Configure dynamic NAT on router R1 as follows:

Basic configurations of dynamic NAT:

R1 (config) # ip nat pool lab 202.202.1.3 202.202.1.4 netmask1_255.255.0

* Create a public address pool named "lab". The initial address is 202.202.1.3 and the ending address is 202.202.1.4. In the event pool, there are two available public addresses, netmask indicates the subnet mask of the IP address in the NAT address pool.

R1 (config) # access-list 1 permit 192.168.2.0 0.0.255

* Defining the translation traffic of interest actually indicates which private network will be translated.

R1 (config) # ip nat inside source list 1 pool lab

* Translate the internal source address defined in ACL List 1. pool lab instructs you to translate the internal source address defined in ACL List 1 into the public IP address defined in the NAT address pool lab.

R1 (config) # inte e1/1

R1 (config-if) # ip nat outside * configure E1/1 as an external interface for NAT.

R1 (config-if) # exit

R1 (config) # inte e1/0

R1 (config-if) # ip nat inside * Internal interface with E1/0 configured as NAT.

R1 (config-if) # exit

Step 2:After configuring dynamic NAT, ping the host 202.202.2.100 on the public network to the host A192.168.2.2), host B192.168.2.3), and host C192.168.2.4 respectively, the execution result is that host A and B can successfully ping the host 202.202.2.100 on the public network, but host C displays the result shown in Figure 9.64, it cannot communicate with hosts on the public network. You can execute show ip nat translations on router R1 to display the result shown in 9.65. We can see that the relationship between private addresses and public addresses is one-to-one, because the public address pool defined by NAT has only two available IP addresses, but there are three hosts on the private network, one private host cannot access the public network according to the one-to-one relationship, this is in line with the theory of the dynamic NAT part. Note that the four NAT address types in the translation table are. 3. 4. Understanding the NAT address type in Case 1 is the same as the NAT address department. In this case, you can further understand the NAT address type in the practice environment.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/16104515P-1.png "title =" 2.png" alt = "221238989.png"/>

This article is from the "unknown Christ" blog. For more information, contact the author!