lunes, 28 de abril de 2008

Configuring NAT (1)

Network Address Translation or NAT was created to represent a large number of private IP addresses for a limited quantity of public IPs; but it's useful for network migrations and mergers (when two networks have similar IP addressing), server load sharing and to create "virtual hosts".


  1. To keep the registred addresses
  2. it helps to solve IP overlaps
  3. No need to renumber as the network changes


  1. NAT increases delays
  2. No End-toEnd traces
  3. 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:'s E0:'s S0:

First, we must configure an IP address in the E0 interface and define it as inside

interface ethernet 0
ip address
ip nat inside

Then, E1 will be configured the same

interface ethernet 1
ip address
ip nat inside

Serial0, configuring an IP and defined as outside interface

interface serial 0
ip address
ip nat outside

Now, we need a NAT pool with the name no-overload; the IP range is to

ip nat pool no-overload 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
access-list 7 permit
!--- Access-list 7 permits packets with source addresses ranging from
!--- through and through

No hay comentarios. :

Publicar un comentario