Advanges:
- To keep the registred addresses
- it helps to solve IP overlaps
- No need to renumber as the network changes
Disadvantage:
- NAT increases delays
- No End-toEnd traces
- Some applications don't support NAT
Below there's a basic example from Cisco's Document: Configuring Network Address Translation:Getting Started
NAT statements allow to map an address to different one, based on source, destination or other rules. The first step is to define, what are the inside and outside interfaces.
For the example 1:We want to allow users to get to the internet, but we have only 1 Public IP used by the router's interface Serial0 (outside). We need to NAT our network to be able to get traffic from the internet in our LAN.
LAN: 10.10.10.1Router's E0: 10.1.1.1Router's S0: 172.16.10.64
First, we must configure an IP address in the E0 interface and define it as inside
interface ethernet 0
ip address 10.10.10.1 255.255.255.0
ip nat inside
Then, E1 will be configured the same
interface ethernet 1
ip address 10.10.20.1 255.255.255.0
ip nat inside
Serial0, configuring an IP and defined as outside interface
interface serial 0
ip address 172.16.10.64 255.255.255.0
ip nat outside
Now, we need a NAT pool with the name no-overload; the IP range is 172.16.10.1 to 172.16.10.63
ip nat pool no-overload 172.16.10.1 172.16.10.63 prefix 24
ip nat inside source list 7 pool no-overload
Indicates: any packets received on the inside interface and permitted by access-list 7 will have as source address translated to an address out of the NAT pool "no-overload".
access-list 7 permit 10.10.10.0 0.0.0.31
access-list 7 permit 10.10.20.0 0.0.0.31
!--- Access-list 7 permits packets with source addresses ranging from
!--- 10.10.10.0 through 10.10.10.31 and 10.10.20.0 through 10.10.20.31
No hay comentarios. :
Publicar un comentario