Beruflich Dokumente
Kultur Dokumente
Objectives
Part 1: Investigate NAT Operation Across the Intranet
Part 2: Investigate NAT Operation Across the Internet
Part 3: Conduct Further Investigations
Scenario
As a frame travels across a network, the MAC addresses may change. IP
addresses can also change when a packet is forwarded by a device configured
with NAT. In this activity, we will investigate what happens to IP addresses during
the NAT process.
Part 1: Investigate NAT Operation Across the Intranet
b. Switch to Simulation mode and edit the filters to show only HTTP requests.
c. Click Go in the browser, a PDU envelope will appear.
d. Click Capture / Forward until the PDU is over D1 or D2. Record the source and
destination
IP addresses. To what devices do those addresses belong? 10.3.0.4 and
64.100.200.1 The PC3 and R4.
e. Click Capture / Forward until the PDU is over R2. Record the source and
destination IP addresses in the outbound packet. To what devices do those
addresses belong? 64.100.100.X and 64.100.200.1 The first address is not
assigned to an interface. R4 is the second address.
Y la IP de destino pertenece a
f. Login to R2 using class to enter privileged EXEC and show the running
configuration. The address came from the following address pool:
i. On both R2 and R4, run the following command and match the IP addresses and
ports recorded above to the correct line of output:
Step 1: Generate an HTTP request from any computer in the home office.
a. Open the Web Browser of any computer in the home office and type the
following without pressing enter or clicking Go: http://centralserver.pka.
b. Switch to Simulation mode. The filters should already be set to show only
HTTP requests.
c. Click Go in the browser, a PDU envelope will appear.
d. Click Capture / Forward until the PDU is over WRS. Record the inbound
source and destination IP addresses and the outbound source and
destination addresses. To what devices do those addresses belong?
192.168.0.X and 64.100.100.2, 64.104.223.2 and 64.100.100.2 The
computer and R2, WRS and R2.
interface Serial0/0/0
ip address 64.100.100.2 255.255.255.224
encapsulation ppp
ppp authentication pap
ppp pap sent-username R2 password 0 cisco
ip nat outside
clock rate 2000000
e. Click Capture / Forward until the PDU is over R2. Record the source and
destination IP addresses in the outbound packet. To what devices do those
addresses belong? 64.104.223.2 and 10.10.10.2 WRS and
centralserver.pka.
En el paquete de salida podemos verificar que la ip de origen es la
64.104.223.2 que es la interface que pertenece a la interface internet del
equipo WRS y la ip 10.01.10.2 pertenece a la ip del server
centralserver.pka.
f. On R2, run the following command and match the IP addresses and ports
recorded above to the correct line of output:
Al ver la carga del servidor este logra cargar todas las pginas
Este tipo de dispositivos no realizan este tipo de asociaciones por ser equipos
de distribucin Este equipo no maneja este tipo de estructura
Esta es una de las estructuras ms utilizadas para los usuario finales ya que este
tipo de conexiones validan autenticacin al medio ya los equipos capa 3 son lo
que permiten identificar si estn dentro de los equipos permitidos en la red
Est definido para poder identificar la ruta complete por donde est realizando al
traduccin desde las direcciones locales hasta pasar por losas direcciones
globales la cueles indican a donde dele llegar el paquete al llegar a la red externa.
Conclusiones