
2-44
Cisco PIX Firewall and VPN Configuration Guide
78-15033-01
Chapter 2 Establishing Connectivity
Policy NAT
Limitations
The following configuration limitations apply to policy NAT:
• Access lists must contain permit statements only. Access lists for policy NAT cannot contain deny
statements.
• An access list must be used only once with the nat command. For example, the following
configuration would produce an error:
nat (inside) 1 access-list mylist-A
nat (inside) 2 access-list mylist-A
Whereas, the following configuration would not produce an error:
nat (inside) 1 access-list mylist-A
nat (inside) 2 access-list mylist-B
• Use an access list only once between the nat and static commands.
• A global address cannot be used concurrently for NAT and PAT.
• static commands are matched and executed before nat commands.
• Policy NAT does not support SQL*Net, which is supported by regular NAT.
Configuring Policy NAT
This section describes how to configure both global translations and static translations. Refer to
Figure 2-12 on page 2-42 and proceed with the configuration that fits the needs of your network.
Configuring Global Translations
Step 1 Configure IP addresses for the inside and outside interfaces.
ip address inside 10.1.2.1 255.255.255.0
ip address outside 209.165.202.129 255.255.255.255
Step 2 Configure access lists to define traffic for translation.
Note Access lists for policy NAT cannot contain deny statements.
access-list NET1 permit ip 10.1.2.0 255.255.255.0 209.165.201.0 255.255.255.224
access-list NET2 permit ip 10.1.2.0 255.255.255.0 209.165.200.224 255.255.255.224
Step 3 Enter nat commands that use the same identifier as those defined with the access-list statements in
Step
2.
nat (inside) 1 access-list NET1
nat (inside) 2 access-list NET2
Komentarze do niniejszej Instrukcji