Práctica 5#

Equipo ARFA-FGFG-ROFM#

  1. Arganis Ramírez Francisco - 108003620
  2. Flores García Fernando - 314107035
  3. Romo Olea Fhernanda - 314284286

Topología de red empleada#

El archivo con el escenario implementado en Packet Tracer se encuentra aquí.

Topología de la red

Cada una de las dependencias de la UNAM existentes en nuestro diagrama se representa con un color distinto, dentro de cada una de éstas (salvo en el rectángulo amarillo compuesto por las redes WAN) se hallan dos subredes que componen a las dependencias, la subred de LAN y la subred de DMZ, conectadas cada una de éstas a dispositivos capa 2 ajenos, que a su vez son conectados a un router perteneciente a la seción de redes WAN.

Cada uno de los router que comunica a cada dependencia con el resto de la red se halla a su vez conectado a un router central, desde el cuál es posible acceder a un servidor DNS, lo anterior hace que se tenga una topología de estrella en la red, siendo el nodo central el servidor al que todos los router y el servidor DNS se encuentran conectados, y las hojas los equipos finales dentro de las dependencias y el servidor DNS. Cualquier equipo que desee realizar un envío de mensajes solamente debe realizar a lo más dos saltos entre router para alcanzar el servidor DNS y hallar la IP a la cuál dirigirse en caso que así lo requiera, con que un paquete alcance el router central, se encontrará a sólo otro salto de la puerta a la red que tiene por destino.

Las conexiones entre routers se dan por medio de interfaces Gigabit Ethernet, mientras que en las conexiones Router-Switch y dentro de las dependencias, en las redes LAN y DMZ sólamente son utilizadas interfaces Fast Ethernet.

Para cada dependencia de la UNAM, su router correspondiente tiene configurados los servicios de NAT overload para la red LAN y NAT estático para la red DMZ. Los clientes en la red LAN salen con la IP de la interfaz en la red WAN del router, mientras que el servidor en la red DMZ se expone al exterior con una IP reservada 192.0.2.X. Las redes LAN y DMZ se consideran "dentro" del NAT y las redes WAN "afuera" del NAT.

Nombre de la red IP Máscara Color
Red LAN Ingeniería 192.168.1.0 255.255.255.0 Violeta
Red DMZ Ingeniería 10.0.1.0 255.255.255.0 Violeta
Red LAN Administración 192.168.2.0 255.255.255.0 Azul
Red DMZ Administración 10.0.2.0 255.255.255.0 Azul
Red LAN Ciencias 192.168.3.0 255.255.255.0 Verde
Red DMZ Ciencias 10.0.3.0 255.255.255.0 Verde
Red LAN Química 192.168.4.0 255.255.255.0 Naranja
Red DMZ Química 10.0.4.0 255.255.255.0 Naranja
Red WAN R-0,1 192.0.2.16 255.255.255.240 Amarillo
Red WAN R-0,2 192.0.2.32 255.255.255.240 Amarillo
Red WAN R-0,3 192.0.2.48 255.255.255.240 Amarillo
Red WAN R-0,4 192.0.2.64 255.255.255.240 Amarillo

Tabla de equipos#

Routers#

Nombre de host Interfaz IP Conexión
Router0 Gig 0/0
Gig 1/0
Gig 2/0
Gig 3/0
Gig 4/0
192.0.2.17
192.0.2.33
192.0.2.49
192.0.2.65
192.0.2.81
Router1
Router2
Router3
Router4
DNS-Server
Router1 Gig 0/0
Fa 2/0
Fa 3/0
192.0.2.18
192.168.1.254
10.0.1.254
Router0
Switch-LAN-1
Switch-DMZ-1
Router2 Gig 0/0
Fa 2/0
Fa 3/0
192.0.2.34
192.168.2.254
10.0.2.254
Router0
Switch-LAN-2
Switch-DMZ-2
Router3 Gig 0/0
Fa 2/0
Fa 3/0
192.0.2.50
192.168.3.254
10.0.3.254
Router0
Switch-LAN-3
Switch-DMZ-3
Router4 Gig 0/0
Fa 2/0
Fa 3/0
192.0.2.66
192.168.4.254
10.0.4.254
Router0
Switch-LAN-4
Switch-DMZ-4

Switches#

Nombre de host Interfaz IP Conexión
Switch-LAN-1 Fa 0/1
Fa 1/1
Fa 2/1
vlan 1
-
-
-
192.168.1.1
Router1
PC1
-
-
Switch-DMZ-1 Fa 0/1
Fa 1/1
vlan 1
-
-
10.0.1.1
Router1
Server1
-
Switch-LAN-2 Fa 0/1
Fa 1/1
Fa 2/1
vlan 1
-
-
-
192.168.2.1
Router2
PC2
Laptop2
-
Switch-DMZ-2 Fa 0/1
Fa 1/1
vlan 1
-
-
10.0.2.1
Router2
Server2
-
Switch-LAN-3 Fa 0/1
Fa 1/1
Fa 2/1
vlan 1
-
-
-
192.168.3.1
Router3
PC3
Laptop3
-
Switch-DMZ-3 Fa 0/1
Fa 1/1
vlan 1
-
-
10.0.3.1
Router3
Server3
-
Switch-LAN-4 Fa 0/1
Fa 1/1
Fa 2/1
vlan 1
-
-
-
192.168.4.1
Router4
PC4
-
-
Switch-DMZ-4 Fa 0/1
Fa 1/1
vlan 1
-
-
10.0.4.1
Router4
Server4
-

Servidores#

Nombre de host Interfaz IP Conexión
Server1 Fa 0 10.0.1.17 (expuesto en la IP pública 192.0.2.19) Switch-DMZ-1
Server2 Fa 0 10.0.2.17 (expuesto en la IP pública 192.0.2.35) Switch-DMZ-2
Server3 Fa 0 10.0.3.17 (expuesto en la IP pública 192.0.2.51) Switch-DMZ-3
Server4 Fa 0 10.0.4.17 (expuesto en la IP pública 192.0.2.67) Switch-DMZ-4
DNS-Server Gig 0 192.0.2.82 Router0

Clientes#

Nombre de host Interfaz IP Conexión
PC1 Fa 0 DHCP Switch-LAN-1
PC2 Fa 0 DHCP Switch-LAN-2
Laptop2 Fa 0 DHCP Switch-LAN-2
PC3 Fa 0 DHCP Switch-LAN-3
Laptop3 Fa 0 DHCP Switch-LAN-3
PC4 Fa 0 DHCP Switch-LAN-4

Servidor DNS#

El servidor DNS, con dirección IP 192.0.2.82, tiene los siguientes 17 registros: 1 registro corresponde al mismo servidor DNS. 12 registros corresponden a las interfaces de los routers. 4 registros corresponden a los servidores en las redes DMZ.

Registros tipo A en DNS-Server

Tablas de traducción de NAT#

Equipos Gateway Dirección IP externa
Clientes en Red LAN Ingeniería 192.168.1.254 192.0.2.18
Server1 en Red DMZ Ingeniería 10.0.1.254 192.0.2.19
Clientes en Red LAN Administración 192.168.2.254 192.0.2.34
Server2 en Red DMZ Administración 10.0.2.254 192.0.2.35
Clientes en Red LAN Ciencias 192.168.3.254 192.0.2.50
Server3 en Red DMZ Ciencias 10.0.3.254 192.0.2.51
Clientes en Red LAN Química 192.168.4.254 192.0.2.66
Server4 en Red DMZ Química 10.0.4.254 192.0.2.67

Por ejemplo, supóngase que el cliente PC4 en Red LAN Química desea enviar un paquete al servidor de Administración expuesto en 192.0.2.35. Como el destino no está en la red local, se envía el paquete al gateway en 192.168.4.254, que es Router4. El router traduce la dirección IP de origen 192.168.4.17 (por la configuración de NAT overload) y redirige el paquete, ahora con IP origen 192.0.2.66 y con IP destino 192.0.2.35. Cuando el paquete llega a Router2, se verifica que el destino es la dirección reservada 192.0.2.35 y se traduce a la dirección IP de Server2 en 10.0.2.17 (por la configuración de NAT estático).

Pruebas de conectividad#

Pruebas desde Ingeniería#

  • Ping desde PC1 en Red LAN Ingeniería a la dirección pública 192.0.2.35 de Server2 en Red DMZ Administración
C:\>ping 192.0.2.35

Pinging 192.0.2.35 with 32 bytes of data:

Reply from 192.0.2.35: bytes=32 time<1ms TTL=125
Reply from 192.0.2.35: bytes=32 time<1ms TTL=125
Reply from 192.0.2.35: bytes=32 time<1ms TTL=125
Reply from 192.0.2.35: bytes=32 time<1ms TTL=125

Ping statistics for 192.0.2.35:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>
  • Ping desde PC1 en Red LAN Ingeniería a la dirección pública 192.0.2.51 de Server3 en Red DMZ Ciencias
C:\>ping 192.0.2.51

Pinging 192.0.2.51 with 32 bytes of data:

Reply from 192.0.2.51: bytes=32 time<1ms TTL=125
Reply from 192.0.2.51: bytes=32 time<1ms TTL=125
Reply from 192.0.2.51: bytes=32 time<1ms TTL=125
Reply from 192.0.2.51: bytes=32 time<1ms TTL=125

Ping statistics for 192.0.2.51:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>
  • Ping desde PC1 en Red LAN Ingeniería a la dirección pública 192.0.2.67 de Server4 en Red DMZ Química
C:\>ping 192.0.2.67

Pinging 192.0.2.67 with 32 bytes of data:

Reply from 192.0.2.67: bytes=32 time<1ms TTL=125
Reply from 192.0.2.67: bytes=32 time<1ms TTL=125
Reply from 192.0.2.67: bytes=32 time=1ms TTL=125
Reply from 192.0.2.67: bytes=32 time=1ms TTL=125

Ping statistics for 192.0.2.67:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\>
Acceso desde PC1 a la página de Administración usando la dirección pública 192.0.2.35 de Server2
Acceso desde PC1 a la página de Ciencias usando el nombre de dominio server.ciencias.edu de Server2

Pruebas desde Administración#

  • Ping desde Laptop2 en Red LAN Administración a la dirección pública 192.0.2.19 de Server1 en Red DMZ Ingeniería
C:\>ping 192.0.2.19

Pinging 192.0.2.19 with 32 bytes of data:

Reply from 192.0.2.19: bytes=32 time<1ms TTL=125
Reply from 192.0.2.19: bytes=32 time=1ms TTL=125
Reply from 192.0.2.19: bytes=32 time<1ms TTL=125
Reply from 192.0.2.19: bytes=32 time<1ms TTL=125

Ping statistics for 192.0.2.19:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\>
  • Ping desde Laptop2 en Red LAN Administración a la dirección pública 192.0.2.51 de Server3 en Red DMZ Ciencias
C:\>ping 192.0.2.51

Pinging 192.0.2.51 with 32 bytes of data:

Reply from 192.0.2.51: bytes=32 time=25ms TTL=125
Reply from 192.0.2.51: bytes=32 time<1ms TTL=125
Reply from 192.0.2.51: bytes=32 time<1ms TTL=125
Reply from 192.0.2.51: bytes=32 time=16ms TTL=125

Ping statistics for 192.0.2.51:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 25ms, Average = 10ms

C:\>
  • Ping desde Laptop2 en Red LAN Administración a la dirección pública 192.0.2.67 de Server4 en Red DMZ Química
C:\>ping 192.0.2.67

Pinging 192.0.2.67 with 32 bytes of data:

Reply from 192.0.2.67: bytes=32 time<1ms TTL=125
Reply from 192.0.2.67: bytes=32 time<1ms TTL=125
Reply from 192.0.2.67: bytes=32 time<1ms TTL=125
Reply from 192.0.2.67: bytes=32 time=18ms TTL=125

Ping statistics for 192.0.2.67:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 18ms, Average = 4ms

C:\>
Acceso desde Laptop2 a la página de Ingeniería usando la dirección pública 192.0.2.19 de Server1
Acceso desde Laptop2 a la página de Química usando el nombre de dominio server.quimica.info de Server4

Pruebas desde Ciencias#

  • Ping desde Laptop3 en Red LAN Ciencias a la dirección pública 192.0.2.19 de Server1 en Red DMZ Ingeniería
C:\>ping 192.0.2.19

Pinging 192.0.2.19 with 32 bytes of data:

Reply from 192.0.2.19: bytes=32 time<1ms TTL=125
Reply from 192.0.2.19: bytes=32 time=1ms TTL=125
Reply from 192.0.2.19: bytes=32 time<1ms TTL=125
Reply from 192.0.2.19: bytes=32 time<1ms TTL=125

Ping statistics for 192.0.2.19:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\>
  • Ping desde Laptop3 en Red LAN Ciencias a la dirección pública 192.0.2.35 de Server2 en Red DMZ Administración
C:\>ping 192.0.2.35

Pinging 192.0.2.35 with 32 bytes of data:

Reply from 192.0.2.35: bytes=32 time=1ms TTL=125
Reply from 192.0.2.35: bytes=32 time<1ms TTL=125
Reply from 192.0.2.35: bytes=32 time<1ms TTL=125
Reply from 192.0.2.35: bytes=32 time<1ms TTL=125

Ping statistics for 192.0.2.35:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\>
  • Ping desde Laptop3 en Red LAN Ciencias a la dirección pública 192.0.2.67 de Server4 en Red DMZ Química
C:\>ping 192.0.2.67

Pinging 192.0.2.67 with 32 bytes of data:

Reply from 192.0.2.67: bytes=32 time<1ms TTL=125
Reply from 192.0.2.67: bytes=32 time<1ms TTL=125
Reply from 192.0.2.67: bytes=32 time<1ms TTL=125
Reply from 192.0.2.67: bytes=32 time<1ms TTL=125

Ping statistics for 192.0.2.67:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>
Acceso desde Laptop3 a la página de Química usando la dirección pública 192.0.2.67 de Server4
Acceso desde Laptop3 a la página de Ingeniería usando el nombre de dominio server.ing.com de Server1

Pruebas desde Química#

  • Ping desde PC4 en Red LAN Química a la dirección pública 192.0.2.19 de Server1 en Red DMZ Ingeniería
C:\>ping 192.0.2.19

Pinging 192.0.2.19 with 32 bytes of data:

Reply from 192.0.2.19: bytes=32 time<1ms TTL=125
Reply from 192.0.2.19: bytes=32 time<1ms TTL=125
Reply from 192.0.2.19: bytes=32 time<1ms TTL=125
Reply from 192.0.2.19: bytes=32 time=3ms TTL=125

Ping statistics for 192.0.2.19:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 3ms, Average = 0ms

C:\>
  • Ping desde PC4 en Red LAN Química a la dirección pública 192.0.2.35 de Server2 en Red DMZ Administración
C:\>ping 192.0.2.35

Pinging 192.0.2.35 with 32 bytes of data:

Reply from 192.0.2.35: bytes=32 time<1ms TTL=125
Reply from 192.0.2.35: bytes=32 time<1ms TTL=125
Reply from 192.0.2.35: bytes=32 time<1ms TTL=125
Reply from 192.0.2.35: bytes=32 time<1ms TTL=125

Ping statistics for 192.0.2.35:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>
  • Ping desde PC4 en Red LAN Química a la dirección pública 192.0.2.51 de Server3 en Red DMZ Ciencias
C:\>ping 192.0.2.51

Pinging 192.0.2.51 with 32 bytes of data:

Reply from 192.0.2.51: bytes=32 time<1ms TTL=125
Reply from 192.0.2.51: bytes=32 time<1ms TTL=125
Reply from 192.0.2.51: bytes=32 time<1ms TTL=125
Reply from 192.0.2.51: bytes=32 time<1ms TTL=125

Ping statistics for 192.0.2.51:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>
Acceso desde PC4 a la página de Ciencias usando la dirección pública 192.0.2.51 de Server3
Acceso desde PC4 a la página de Administración usando el nombre de dominio server.admin.org de Server2

Traceroute#

  • De Laptop3 en Red LAN Ciencias a la interfaz WAN de Router2
C:\>tracert 192.0.2.34

Tracing route to 192.0.2.34 over a maximum of 30 hops:

  1   0 ms      0 ms      0 ms      192.168.3.254
  2   0 ms      0 ms      0 ms      192.0.2.49
  3   0 ms      0 ms      0 ms      192.0.2.34

Trace complete.

C:\>

Como se observa, para alcanzar Router2, la ruta es:

  1. El paquete sale al gateway: 192.168.3.254 (interfaz de Router3 en Red LAN Ciencias)
  2. El router de Ciencias redirige el paquete al router central: 192.0.2.49 (interfaz de Router0 en Red WAN R-0,3)
  3. El router central redirige el paquete al router de Administración: 192.0.2.34 (interfaz de Router2 en Red WAN R-0,2)

Tablas de rutas y RIP#

Router0#

  • Tabla de rutas
Router0#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       * - candidate default, U - per-user static route, o - ODR
       P - periodic downloaded static route

Gateway of last resort is not set

     192.0.2.0/28 is subnetted, 5 subnets
C       192.0.2.16 is directly connected, GigabitEthernet0/0
C       192.0.2.32 is directly connected, GigabitEthernet1/0
C       192.0.2.48 is directly connected, GigabitEthernet2/0
C       192.0.2.64 is directly connected, GigabitEthernet3/0
C       192.0.2.80 is directly connected, GigabitEthernet4/0

Router0#
  • Tabla RIP
Router0#show ip rip database
192.0.2.16/28    auto-summary
192.0.2.16/28    directly connected, GigabitEthernet0/0
192.0.2.32/28    auto-summary
192.0.2.32/28    directly connected, GigabitEthernet1/0
192.0.2.48/28    auto-summary
192.0.2.48/28    directly connected, GigabitEthernet2/0
192.0.2.64/28    auto-summary
192.0.2.64/28    directly connected, GigabitEthernet3/0
192.0.2.80/28    auto-summary
192.0.2.80/28    directly connected, GigabitEthernet4/0
Router0#

Router1#

  • Tabla de rutas
Router1#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       * - candidate default, U - per-user static route, o - ODR
       P - periodic downloaded static route

Gateway of last resort is not set

     10.0.0.0/24 is subnetted, 1 subnets
C       10.0.1.0 is directly connected, FastEthernet3/0
     192.0.2.0/28 is subnetted, 5 subnets
C       192.0.2.16 is directly connected, GigabitEthernet0/0
R       192.0.2.32 [120/1] via 192.0.2.17, 00:00:20, GigabitEthernet0/0
R       192.0.2.48 [120/1] via 192.0.2.17, 00:00:20, GigabitEthernet0/0
R       192.0.2.64 [120/1] via 192.0.2.17, 00:00:20, GigabitEthernet0/0
R       192.0.2.80 [120/1] via 192.0.2.17, 00:00:20, GigabitEthernet0/0
C    192.168.1.0/24 is directly connected, FastEthernet2/0

Router1#
  • Tabla RIP
Router1#show ip rip database
192.0.2.16/28    auto-summary
192.0.2.16/28    directly connected, GigabitEthernet0/0
192.0.2.32/28    auto-summary
192.0.2.32/28
    [1] via 192.0.2.17, 00:00:26, GigabitEthernet0/0
192.0.2.48/28    auto-summary
192.0.2.48/28
    [1] via 192.0.2.17, 00:00:26, GigabitEthernet0/0
192.0.2.64/28    auto-summary
192.0.2.64/28
    [1] via 192.0.2.17, 00:00:26, GigabitEthernet0/0
192.0.2.80/28    auto-summary
192.0.2.80/28
    [1] via 192.0.2.17, 00:00:26, GigabitEthernet0/0
Router1#

Router2#

  • Tabla de rutas
Router2#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       * - candidate default, U - per-user static route, o - ODR
       P - periodic downloaded static route

Gateway of last resort is not set

     10.0.0.0/24 is subnetted, 1 subnets
C       10.0.2.0 is directly connected, FastEthernet3/0
     192.0.2.0/28 is subnetted, 5 subnets
R       192.0.2.16 [120/1] via 192.0.2.33, 00:00:13, GigabitEthernet0/0
C       192.0.2.32 is directly connected, GigabitEthernet0/0
R       192.0.2.48 [120/1] via 192.0.2.33, 00:00:13, GigabitEthernet0/0
R       192.0.2.64 [120/1] via 192.0.2.33, 00:00:13, GigabitEthernet0/0
R       192.0.2.80 [120/1] via 192.0.2.33, 00:00:13, GigabitEthernet0/0
C    192.168.2.0/24 is directly connected, FastEthernet2/0

Router2#
  • Tabla RIP
Router2#show ip rip database
192.0.2.16/28    auto-summary
192.0.2.16/28
    [1] via 192.0.2.33, 00:00:01, GigabitEthernet0/0
192.0.2.32/28    auto-summary
192.0.2.32/28    directly connected, GigabitEthernet0/0
192.0.2.48/28    auto-summary
192.0.2.48/28
    [1] via 192.0.2.33, 00:00:01, GigabitEthernet0/0
192.0.2.64/28    auto-summary
192.0.2.64/28
    [1] via 192.0.2.33, 00:00:01, GigabitEthernet0/0
192.0.2.80/28    auto-summary
192.0.2.80/28
    [1] via 192.0.2.33, 00:00:01, GigabitEthernet0/0
Router2#

Router3#

  • Tabla de rutas
Router3#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       * - candidate default, U - per-user static route, o - ODR
       P - periodic downloaded static route

Gateway of last resort is not set

     10.0.0.0/24 is subnetted, 1 subnets
C       10.0.3.0 is directly connected, FastEthernet3/0
     192.0.2.0/28 is subnetted, 5 subnets
R       192.0.2.16 [120/1] via 192.0.2.49, 00:00:05, GigabitEthernet0/0
R       192.0.2.32 [120/1] via 192.0.2.49, 00:00:05, GigabitEthernet0/0
C       192.0.2.48 is directly connected, GigabitEthernet0/0
R       192.0.2.64 [120/1] via 192.0.2.49, 00:00:05, GigabitEthernet0/0
R       192.0.2.80 [120/1] via 192.0.2.49, 00:00:05, GigabitEthernet0/0
C    192.168.3.0/24 is directly connected, FastEthernet2/0

Router3#
  • Tabla RIP
Router3#show ip rip database
192.0.2.16/28    auto-summary
192.0.2.16/28
    [1] via 192.0.2.49, 00:00:09, GigabitEthernet0/0
192.0.2.32/28    auto-summary
192.0.2.32/28
    [1] via 192.0.2.49, 00:00:09, GigabitEthernet0/0
192.0.2.48/28    auto-summary
192.0.2.48/28    directly connected, GigabitEthernet0/0
192.0.2.64/28    auto-summary
192.0.2.64/28
    [1] via 192.0.2.49, 00:00:09, GigabitEthernet0/0
192.0.2.80/28    auto-summary
192.0.2.80/28
    [1] via 192.0.2.49, 00:00:09, GigabitEthernet0/0
Router3#

Router4#

  • Tabla de rutas
Router4#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       * - candidate default, U - per-user static route, o - ODR
       P - periodic downloaded static route

Gateway of last resort is not set

     10.0.0.0/24 is subnetted, 1 subnets
C       10.0.4.0 is directly connected, FastEthernet3/0
     192.0.2.0/28 is subnetted, 5 subnets
R       192.0.2.16 [120/1] via 192.0.2.65, 00:00:03, GigabitEthernet0/0
R       192.0.2.32 [120/1] via 192.0.2.65, 00:00:03, GigabitEthernet0/0
R       192.0.2.48 [120/1] via 192.0.2.65, 00:00:03, GigabitEthernet0/0
C       192.0.2.64 is directly connected, GigabitEthernet0/0
R       192.0.2.80 [120/1] via 192.0.2.65, 00:00:03, GigabitEthernet0/0
C    192.168.4.0/24 is directly connected, FastEthernet2/0

Router4#
  • Tabla RIP
Router4#show ip rip database
192.0.2.16/28    auto-summary
192.0.2.16/28
    [1] via 192.0.2.65, 00:00:20, GigabitEthernet0/0
192.0.2.32/28    auto-summary
192.0.2.32/28
    [1] via 192.0.2.65, 00:00:20, GigabitEthernet0/0
192.0.2.48/28    auto-summary
192.0.2.48/28
    [1] via 192.0.2.65, 00:00:20, GigabitEthernet0/0
192.0.2.64/28    auto-summary
192.0.2.64/28    directly connected, GigabitEthernet0/0
192.0.2.80/28    auto-summary
192.0.2.80/28
    [1] via 192.0.2.65, 00:00:20, GigabitEthernet0/0
Router4#

Estadísticas de NAT y tabla de traducciones#

Router0#

  • Estadísticas NAT
Router0#show ip nat statistics
Router0#
  • Tabla de traducciones
Router0#show ip nat translations
Router0#

Router1#

  • Estadísticas NAT
Router1#show ip nat statistics
Total translations: 9 (1 static, 8 dynamic, 8 extended)
Outside Interfaces: GigabitEthernet0/0
Inside Interfaces: FastEthernet2/0 , FastEthernet3/0
Hits: 83  Misses: 262
Expired translations: 54
Dynamic mappings:
Router1#
  • Tabla de traducciones
Router1#show ip nat translations
Pro  Inside global     Inside local       Outside local      Outside global
icmp 192.0.2.18:29     192.168.1.17:29    192.0.2.66:29      192.0.2.66:29
icmp 192.0.2.18:30     192.168.1.17:30    192.0.2.66:30      192.0.2.66:30
icmp 192.0.2.18:31     192.168.1.17:31    192.0.2.66:31      192.0.2.66:31
icmp 192.0.2.18:32     192.168.1.17:32    192.0.2.66:32      192.0.2.66:32
---  192.0.2.19        10.0.1.17          ---                ---
tcp 192.0.2.18:1025    192.168.1.17:1025  192.0.2.35:80      192.0.2.35:80
tcp 192.0.2.18:1026    192.168.1.17:1026  192.0.2.51:80      192.0.2.51:80
tcp 192.0.2.19:80      10.0.1.17:80       192.0.2.34:1025    192.0.2.34:1025
tcp 192.0.2.19:80      10.0.1.17:80       192.0.2.50:1025    192.0.2.50:1025

Router1#

Router2#

  • Estadísticas NAT
Router2#show ip nat statistics
Total translations: 13 (1 static, 12 dynamic, 12 extended)
Outside Interfaces: GigabitEthernet0/0
Inside Interfaces: FastEthernet2/0 , FastEthernet3/0
Hits: 132  Misses: 267
Expired translations: 52
Dynamic mappings:
Router2#
  • Tabla de traducciones
Router2#show ip nat translations
Pro  Inside global     Inside local       Outside local      Outside global
icmp 192.0.2.34:10     192.168.2.18:10    192.0.2.50:10      192.0.2.50:10
icmp 192.0.2.34:11     192.168.2.18:11    192.0.2.50:11      192.0.2.50:11
icmp 192.0.2.34:12     192.168.2.18:12    192.0.2.50:12      192.0.2.50:12
icmp 192.0.2.34:9      192.168.2.18:9     192.0.2.50:9       192.0.2.50:9
---  192.0.2.35        10.0.2.17          ---                ---
tcp 192.0.2.34:1024    192.168.2.18:1025  192.0.2.51:80      192.0.2.51:80
tcp 192.0.2.34:1025    192.168.2.17:1025  192.0.2.19:80      192.0.2.19:80
tcp 192.0.2.34:1026    192.168.2.17:1026  192.0.2.67:80      192.0.2.67:80
tcp 192.0.2.34:1027    192.168.2.18:1027  192.0.2.35:80      192.0.2.35:80
tcp 192.0.2.34:1028    192.168.2.18:1028  192.0.2.35:80      192.0.2.35:80
tcp 192.0.2.34:1029    192.168.2.18:1029  192.0.2.35:80      192.0.2.35:80
tcp 192.0.2.35:80      10.0.2.17:80       192.0.2.18:1025    192.0.2.18:1025
tcp 192.0.2.35:80      10.0.2.17:80       192.0.2.66:1026    192.0.2.66:1026

Router2#

Router3#

  • Estadísticas NAT
Router3#show ip nat statistics
Total translations: 10 (1 static, 9 dynamic, 9 extended)
Outside Interfaces: GigabitEthernet0/0
Inside Interfaces: FastEthernet2/0 , FastEthernet3/0
Hits: 82  Misses: 271
Expired translations: 41
Dynamic mappings:
Router3#
  • Tabla de traducciones
Router3#show ip nat translations
Pro  Inside global     Inside local       Outside local      Outside global
icmp 192.0.2.50:1      192.168.3.18:1     192.0.2.35:1       192.0.2.35:1
icmp 192.0.2.50:2      192.168.3.18:2     192.0.2.35:2       192.0.2.35:2
icmp 192.0.2.50:3      192.168.3.18:3     192.0.2.35:3       192.0.2.35:3
icmp 192.0.2.50:4      192.168.3.18:4     192.0.2.35:4       192.0.2.35:4
---  192.0.2.51        10.0.3.17          ---                ---
tcp 192.0.2.50:1025    192.168.3.17:1025  192.0.2.19:80      192.0.2.19:80
tcp 192.0.2.50:1026    192.168.3.17:1026  192.0.2.67:80      192.0.2.67:80
tcp 192.0.2.51:80      10.0.3.17:80       192.0.2.18:1026    192.0.2.18:1026
tcp 192.0.2.51:80      10.0.3.17:80       192.0.2.34:1024    192.0.2.34:1024
tcp 192.0.2.51:80      10.0.3.17:80       192.0.2.66:1025    192.0.2.66:1025

Router3#

Router4#

  • Estadísticas NAT
Router4#show ip nat statistics
Total translations: 9 (1 static, 8 dynamic, 8 extended)
Outside Interfaces: GigabitEthernet0/0
Inside Interfaces: FastEthernet2/0 , FastEthernet3/0
Hits: 67  Misses: 267
Expired translations: 36
Dynamic mappings:
Router4#
  • Tabla de traducciones
Router4#show ip nat translations
Pro  Inside global     Inside local       Outside local      Outside global
icmp 192.0.2.66:13     192.168.4.17:13    192.0.2.51:13      192.0.2.51:13
icmp 192.0.2.66:14     192.168.4.17:14    192.0.2.51:14      192.0.2.51:14
icmp 192.0.2.66:15     192.168.4.17:15    192.0.2.51:15      192.0.2.51:15
icmp 192.0.2.66:16     192.168.4.17:16    192.0.2.51:16      192.0.2.51:16
---  192.0.2.67        10.0.4.17          ---                ---
tcp 192.0.2.66:1025    192.168.4.17:1025  192.0.2.51:80      192.0.2.51:80
tcp 192.0.2.66:1026    192.168.4.17:1026  192.0.2.35:80      192.0.2.35:80
tcp 192.0.2.67:80      10.0.4.17:80       192.0.2.34:1026    192.0.2.34:1026
tcp 192.0.2.67:80      10.0.4.17:80       192.0.2.50:1026    192.0.2.50:1026

Router4#

Archivos#

Archivo Descripción
Router0_startup-config startup config de Router0
Router1_startup-config startup config de Router1
Router2_startup-config startup config de Router2
Router3_startup-config startup config de Router3
Router4_startup-config startup config de Router4
Switch-LAN-1_startup-config startup config de Switch-LAN-1
Switch-DMZ-1_startup-config startup config de Switch-DMZ-1
Switch-LAN-2_startup-config startup config de Switch-LAN-2
Switch-DMZ-2_startup-config startup config de Switch-DMZ-2
Switch-LAN-3_startup-config startup config de Switch-LAN-3
Switch-DMZ-3_startup-config startup config de Switch-DMZ-3
Switch-LAN-4_startup-config startup config de Switch-LAN-4
Switch-DMZ-4_startup-config startup config de Switch-DMZ-4
Server1-index.html Código fuente de la página web de Server1 en Red DMZ Ingeniería
Server2-index.html Código fuente de la página web de Server2 en Red DMZ Administración
Server3-index.html Código fuente de la página web de Server3 en Red DMZ Ciencias
Server4-index.html Código fuente de la página web de Server4 en Red DMZ Química