e private IP address 192. 168.1.10. The second translates 10.0.0.11 to the private IP address 192.168.1.11: global (outside) 1 interface nat (inside) 1 0.0.0.0 0.0.0.0 0 0 static (inside, outside) 10.0.0.10 192.168.1.10 netmask 255.255.255.255 0 0 static (inside,outside) 10.0.0.11 192.168.1.11 netmask 255.255.255.255 0 0 static statements override the more generic nat statement, SO these commands can be used together in this way without issue. Be wary when configuring static state- ments, however. The order of interfaces and networks can be confusing. If you look carefully at the preceding example, you'll see that the references are essentially: (inside-int,outside-int) outside-net inside-net Remember that these static statements are allowing connections from outside to come into these two IP addresses, which reside inside the secure network. This may sound dangerous, but because the outside interface has a security level of 0, and the inside interface has a security level of 100, traffic cannot flow from outside to inside unless it's permitted with an access list. In other words, an access list must now be created to allow the desired traffic to pass. Port redirection Port redirection is different from Port Address Translation. While PAT translates a pool of addresses to a single address by translating the ports within the packets being sent, port redirection does something else entirely. Port redirection allows you to configure a static NAT where, though there is one IP address on the public side, there can be many IP addresses on the private side, each of which responds to a different port. PAT does not permit inbound connections. Port translation does. Imagine you have only eight IP addresses on your public network, which are all in use: .0 - Network address .1 - ISP Router VIP (HSRP) .2 - ISP Router 1 .3 - ISP Router 2 .4 - Primary PIX .5 - Secondary PIX .6 - Web server public IP .7 - Broadcast address While it might not seem realistic to have SO much resilient equipment on such a small network, you might be