Отчет по лабораторной работе №5 «Маршрутизация в протоколе ip» по курсу «Сети ЭВМ и средства телекоммуникаций»
Скачать 96.27 Kb.
|
| ФЕДЕРАЛЬНОЕ АГЕНСТВО ПО ОБРАЗОВАНИЮ Государственное образовательное учреждение высшего профессионального образования Московский государственный институт электроники и математики (Технический университет) Кафедра ИКТ ОТЧЕТ ПО ЛАБОРАТОРНОЙ РАБОТЕ №5 «Маршрутизация в протоколе IP» по курсу «Сети ЭВМ и средства телекоммуникаций» ВЫПОЛНИЛ: Клюев А.А., группа С-65 Москва 2011 Задание 1. Выведите таблицу маршрутизации с помощью команд route и ip route. Какой из выводов вам показался удобнее? root@ubuntu:/home/andrey# route -n Таблица маршутизации ядра протокола IP Destination Gateway Genmask Flags Metric Ref Use Iface 85.21.88.130 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.16 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.72.83 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.52.254 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.21 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.0.178 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.0.178 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.26 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 89.179.135.67 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.40.141 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.93 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.90.0 10.181.8.1 255.255.255.0 UG 0 0 0 eth0 78.107.23.0 10.181.8.1 255.255.255.0 UG 0 0 0 eth0 85.21.79.0 10.181.8.1 255.255.255.0 UG 0 0 0 eth0 10.181.8.0 0.0.0.0 255.255.248.0 U 1 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0 10.0.0.0 10.181.8.1 255.0.0.0 UG 0 0 0 eth0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0 root@ubuntu:/home/andrey# ip route show 85.21.88.130 via 10.181.8.1 dev eth0 195.14.50.16 via 10.181.8.1 dev eth0 85.21.72.83 via 10.181.8.1 dev eth0 85.21.52.254 via 10.181.8.1 dev eth0 195.14.50.21 via 10.181.8.1 dev eth0 85.21.0.178 via 10.181.8.1 dev eth0 85.21.0.178 via 10.181.8.1 dev eth0 src 10.181.11.115 195.14.50.26 via 10.181.8.1 dev eth0 89.179.135.67 via 10.181.8.1 dev eth0 195.14.40.141 via 10.181.8.1 dev eth0 195.14.50.93 via 10.181.8.1 dev eth0 85.21.90.0/24 via 10.181.8.1 dev eth0 78.107.23.0/24 via 10.181.8.1 dev eth0 85.21.79.0/24 via 10.181.8.1 dev eth0 10.181.8.0/21 dev eth0 proto kernel scope link src 10.181.11.115 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 10.0.0.0/8 via 10.181.8.1 dev eth0 default dev ppp0 scope link root@ubuntu:/home/andrey# Вывод таблицы маршрутизации при помощи команды route удобнее, т. к. все выводящиеся данные выровнены по столбцам. Задание 2. Добавьте в таблицу маршрутизации одну произвольную запись. root@ubuntu:/home/andrey# route add -net 172.168.1.0 netmask 255.255.255.0 gw 10.181.8.2 root@ubuntu:/home/andrey# route -n Таблица маршутизации ядра протокола IP Destination Gateway Genmask Flags Metric Ref Use Iface 85.21.88.130 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.16 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.72.83 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.52.254 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.21 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.0.178 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.0.178 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.26 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 89.179.135.67 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.40.141 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.93 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 172.168.1.0 10.181.8.2 255.255.255.0 UG 0 0 0 eth0 85.21.90.0 10.181.8.1 255.255.255.0 UG 0 0 0 eth0 78.107.23.0 10.181.8.1 255.255.255.0 UG 0 0 0 eth0 85.21.79.0 10.181.8.1 255.255.255.0 UG 0 0 0 eth0 10.181.8.0 0.0.0.0 255.255.248.0 U 1 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0 10.0.0.0 10.181.8.1 255.0.0.0 UG 0 0 0 eth0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0 root@ubuntu:/home/andrey# Задание 3. Измените значение шлюза по-умолчанию. root@ubuntu:/home/andrey# traceroute ya.ru traceroute to ya.ru (87.250.250.3), 30 hops max, 60 byte packets 1 * * * 2 * * * 3 mo-crs-teng0-0-0-2.msk.corbina.net (195.14.54.255) 22.613 ms 22.604 ms 22.591 ms 4 m9-crs-be3.msk.corbina.net (195.14.54.141) 14.577 ms 14.566 ms 14.556 ms 5 m9-bb-po5-80G.msk.corbina.net (78.107.184.216) 14.542 ms 14.531 ms 14.520 ms 6 msk-ix-m9.yandex.net (193.232.244.93) 30.649 ms 20.450 ms 20.438 ms 7 zinc-ugr-vlan803.yandex.net (77.88.56.62) 7.929 ms 7.918 ms 7.907 ms 8 l3-s3600-s1300.yandex.net (213.180.213.75) 7.897 ms 28.445 ms 28.432 ms 9 www.yandex.ru (87.250.250.3) 8.058 ms 8.054 ms 8.034 ms root@ubuntu:/home/andrey# sudo route add default gw 195.14.54.255 root@ubuntu:/home/andrey# route -n Таблица маршутизации ядра протокола IP Destination Gateway Genmask Flags Metric Ref Use Iface 85.21.88.130 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.16 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.72.83 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.52.254 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.21 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.0.178 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.0.178 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.26 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 89.179.135.67 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.40.141 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.93 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 172.168.1.0 10.181.8.2 255.255.255.0 UG 0 0 0 eth0 85.21.90.0 10.181.8.1 255.255.255.0 UG 0 0 0 eth0 78.107.23.0 10.181.8.1 255.255.255.0 UG 0 0 0 eth0 85.21.79.0 10.181.8.1 255.255.255.0 UG 0 0 0 eth0 10.181.8.0 0.0.0.0 255.255.248.0 U 1 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0 10.0.0.0 10.181.8.1 255.0.0.0 UG 0 0 0 eth0 0.0.0.0 195.14.54.255 0.0.0.0 UG 0 0 0 ppp0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0 root@ubuntu:/home/andrey# Задание 4. Удалите одну из записей в таблице маршрутизации. root@ubuntu:/home/andrey# sudo route del -net 0.0.0.0 gw 195.14.54.255 root@ubuntu:/home/andrey# route -n Таблица маршутизации ядра протокола IP Destination Gateway Genmask Flags Metric Ref Use Iface 85.21.88.130 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.16 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.72.83 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.52.254 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.21 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.0.178 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.0.178 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.26 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 89.179.135.67 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.40.141 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.93 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 172.168.1.0 10.181.8.2 255.255.255.0 UG 0 0 0 eth0 85.21.90.0 10.181.8.1 255.255.255.0 UG 0 0 0 eth0 78.107.23.0 10.181.8.1 255.255.255.0 UG 0 0 0 eth0 85.21.79.0 10.181.8.1 255.255.255.0 UG 0 0 0 eth0 10.181.8.0 0.0.0.0 255.255.248.0 U 1 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0 10.0.0.0 10.181.8.1 255.0.0.0 UG 0 0 0 eth0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0 root@ubuntu:/home/andrey# Задание 5. Добавьте запись типа blackhole в таблицу маршрутизации. Для чего могут быть полезны подобные записи? root@ubuntu:/home/andrey# sudo ip route add blackhole 172.168.1.0/24 root@ubuntu:/home/andrey# route -n Таблица маршутизации ядра протокола IP Destination Gateway Genmask Flags Metric Ref Use Iface 85.21.88.130 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.16 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.72.83 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.52.254 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.21 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.0.178 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 85.21.0.178 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.26 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 89.179.135.67 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.40.141 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 195.14.50.93 10.181.8.1 255.255.255.255 UGH 0 0 0 eth0 172.168.1.0 10.181.8.2 255.255.255.0 UG 0 0 0 * 85.21.90.0 10.181.8.1 255.255.255.0 UG 0 0 0 eth0 78.107.23.0 10.181.8.1 255.255.255.0 UG 0 0 0 eth0 85.21.79.0 10.181.8.1 255.255.255.0 UG 0 0 0 eth0 10.181.8.0 0.0.0.0 255.255.248.0 U 1 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0 10.0.0.0 10.181.8.1 255.0.0.0 UG 0 0 0 eth0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0 root@ubuntu:/home/andrey# Это хорошое средство для борьбы с DdoS атаками. Задание 6. Создайте в программе Cisco Packet Tracer модель сети, изображенную на иллюстрации ниже. a) Настройте для каждого из роутеров статическую маршрутизацию. b) Выведите таблицу маршрутизации для каждого роутера (команда show ip route). c) Проверьте правильность настройки с помощью команды ping и tracert в консоли каждого из компьютеров. a)  b)Для Router0: Router#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, 2 subnets C 10.0.0.0 is directly connected, FastEthernet0/0 C 10.0.1.0 is directly connected, FastEthernet1/0 S 192.168.1.0/24 [1/0] via 10.0.1.1 C 192.168.2.0/24 is directly connected, FastEthernet4/0 S 192.168.3.0/24 [1/0] via 10.0.0.1 Router# Для Router1: Router#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 10.0.0.2 to network 0.0.0.0 10.0.0.0/24 is subnetted, 1 subnets C 10.0.0.0 is directly connected, FastEthernet1/0 C 192.168.3.0/24 is directly connected, FastEthernet0/0 S* 0.0.0.0/0 [1/0] via 10.0.0.2 Router# Для Router2: Router#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 10.0.1.2 to network 0.0.0.0 10.0.0.0/24 is subnetted, 1 subnets C 10.0.1.0 is directly connected, FastEthernet1/0 C 192.168.1.0/24 is directly connected, FastEthernet0/0 S* 0.0.0.0/0 [1/0] via 10.0.1.2 Router# c)Для PC0: PC>ping 192.168.2.1 Pinging 192.168.2.1 with 32 bytes of data: Reply from 192.168.2.1: bytes=32 time=20ms TTL=254 Reply from 192.168.2.1: bytes=32 time=35ms TTL=254 Reply from 192.168.2.1: bytes=32 time=27ms TTL=254 Reply from 192.168.2.1: bytes=32 time=14ms TTL=254 Ping statistics for 192.168.2.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 35ms, Average = 24ms PC>tracert 192.168.2.1 Tracing route to 192.168.2.1 over a maximum of 30 hops: 1 6 ms 3 ms 12 ms 192.168.3.1 2 16 ms 16 ms 13 ms 192.168.2.1 Trace complete. PC>ping 192.168.1.1 Pinging 192.168.1.1 with 32 bytes of data: Reply from 192.168.1.1: bytes=32 time=20ms TTL=253 Reply from 192.168.1.1: bytes=32 time=19ms TTL=253 Reply from 192.168.1.1: bytes=32 time=23ms TTL=253 Reply from 192.168.1.1: bytes=32 time=32ms TTL=253 Ping statistics for 192.168.1.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 32ms, Average = 23ms PC>tracert 192.168.1.1 Tracing route to 192.168.1.1 over a maximum of 30 hops: 1 6 ms 2 ms 4 ms 192.168.3.1 2 10 ms 15 ms 14 ms 10.0.0.2 3 13 ms 18 ms 19 ms 192.168.1.1 Trace complete. PC> Для PC1: PC>ping 192.168.3.1 Pinging 192.168.3.1 with 32 bytes of data: Reply from 192.168.3.1: bytes=32 time=20ms TTL=254 Reply from 192.168.3.1: bytes=32 time=15ms TTL=254 Reply from 192.168.3.1: bytes=32 time=20ms TTL=254 Reply from 192.168.3.1: bytes=32 time=17ms TTL=254 Ping statistics for 192.168.3.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 15ms, Maximum = 20ms, Average = 18ms PC>tracert 192.168.3.1 Tracing route to 192.168.3.1 over a maximum of 30 hops: 1 13 ms 4 ms 6 ms 192.168.2.1 2 13 ms 13 ms 13 ms 192.168.3.1 Trace complete. PC>ping 192.168.1.1 Pinging 192.168.1.1 with 32 bytes of data: Reply from 192.168.1.1: bytes=32 time=19ms TTL=254 Reply from 192.168.1.1: bytes=32 time=12ms TTL=254 Reply from 192.168.1.1: bytes=32 time=14ms TTL=254 Reply from 192.168.1.1: bytes=32 time=27ms TTL=254 Ping statistics for 192.168.1.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 12ms, Maximum = 27ms, Average = 18ms PC>tracert 192.168.1.1 Tracing route to 192.168.1.1 over a maximum of 30 hops: 1 13 ms 3 ms 10 ms 192.168.2.1 2 16 ms 17 ms 16 ms 192.168.1.1 Trace complete. PC> Для PC2: PC>ping 192.168.3.1 Pinging 192.168.3.1 with 32 bytes of data: Reply from 192.168.3.1: bytes=32 time=32ms TTL=253 Reply from 192.168.3.1: bytes=32 time=20ms TTL=253 Reply from 192.168.3.1: bytes=32 time=16ms TTL=253 Reply from 192.168.3.1: bytes=32 time=31ms TTL=253 Ping statistics for 192.168.3.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 32ms, Average = 24ms PC>tracert 192.168.3.1 Tracing route to 192.168.3.1 over a maximum of 30 hops: 1 14 ms 9 ms 10 ms 192.168.1.1 2 19 ms 18 ms 16 ms 10.0.1.2 3 24 ms 19 ms 19 ms 192.168.3.1 Trace complete. PC>ping 192.168.2.1 Pinging 192.168.2.1 with 32 bytes of data: Reply from 192.168.2.1: bytes=32 time=19ms TTL=254 Reply from 192.168.2.1: bytes=32 time=21ms TTL=254 Reply from 192.168.2.1: bytes=32 time=15ms TTL=254 Reply from 192.168.2.1: bytes=32 time=11ms TTL=254 Ping statistics for 192.168.2.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 21ms, Average = 16ms PC>tracert 192.168.2.1 Tracing route to 192.168.2.1 over a maximum of 30 hops: 1 6 ms 4 ms 4 ms 192.168.1.1 2 13 ms 15 ms 11 ms 192.168.2.1 Trace complete. PC> Задание 1. Создайте в программе Cisco Packet Tracer модель сети, изображенную на иллюстрации ниже.Настройте сетевые интерфейсы на каждом из роутеров. a) Настройте маршрутизацию по протоколу RIP на каждом из роутеров и выведите таблицы маршрутизации (принимайте во внимание периоды рассылки таблиц маршрутизации в RIP).Проверьте правильность настройки с помощью команд ping и tracert в консоли каждого из компьютеров.  Router0: 172.20.0.0/24 is subnetted, 8 subnets C 172.20.0.0 is directly connected, FastEthernet6/0 R 172.20.1.0 [120/1] via 172.20.0.1, 00:00:23, FastEthernet6/0 C 172.20.2.0 is directly connected, FastEthernet8/0 R 172.20.3.0 [120/1] via 172.20.2.2, 00:00:18, FastEthernet8/0 [120/1] via 172.20.7.1, 00:00:01, FastEthernet7/0 R 172.20.4.0 [120/2] via 172.20.0.1, 00:00:23, FastEthernet6/0 [120/2] via 172.20.7.1, 00:00:01, FastEthernet7/0 R 172.20.5.0 [120/1] via 172.20.7.1, 00:00:01, FastEthernet7/0 R 172.20.6.0 [120/1] via 172.20.7.1, 00:00:01, FastEthernet7/0 C 172.20.7.0 is directly connected, FastEthernet7/0 R 192.168.0.0/24 [120/1] via 172.20.0.1, 00:00:23, FastEthernet6/0 Router1: 172.20.0.0/24 is subnetted, 8 subnets C 172.20.0.0 is directly connected, FastEthernet6/0 C 172.20.1.0 is directly connected, FastEthernet7/0 R 172.20.2.0 [120/1] via 172.20.0.2, 00:00:05, FastEthernet6/0 R 172.20.3.0 [120/2] via 172.20.0.2, 00:00:05, FastEthernet6/0 [120/2] via 172.20.1.2, 00:00:09, FastEthernet7/0 R 172.20.4.0 [120/1] via 172.20.1.2, 00:00:09, FastEthernet7/0 R 172.20.5.0 [120/2] via 172.20.1.2, 00:00:09, FastEthernet7/0 [120/2] via 172.20.0.2, 00:00:05, FastEthernet6/0 R 172.20.6.0 [120/1] via 172.20.1.2, 00:00:09, FastEthernet7/0 R 172.20.7.0 [120/1] via 172.20.0.2, 00:00:05, FastEthernet6/0 C 192.168.0.0/24 is directly connected, FastEthernet0/0 Для остальных роутеров таблица коммутации идентичная PC>ping 192.168.3.11 Pinging 192.168.3.11 with 32 bytes of data: Reply from 192.168.3.11: bytes=32 time=19ms TTL=126 Reply from 192.168.3.11: bytes=32 time=24ms TTL=126 Reply from 192.168.3.11: bytes=32 time=17ms TTL=126 Reply from 192.168.3.11: bytes=32 time=26ms TTL=126 Ping statistics for 192.168.3.11: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 17ms, Maximum = 26ms, Average = 21ms PC>ping 192.168.2.11 Pinging 192.168.2.11 with 32 bytes of data: Reply from 192.168.2.11: bytes=32 time=26ms TTL=125 Reply from 192.168.2.11: bytes=32 time=21ms TTL=125 Reply from 192.168.2.11: bytes=32 time=29ms TTL=125 Reply from 192.168.2.11: bytes=32 time=27ms TTL=125 Ping statistics for 192.168.2.11: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 21ms, Maximum = 29ms, Average = 25ms PC>tracert 192.168.0.11 Tracing route to 192.168.0.11 over a maximum of 30 hops: 1 8 ms 7 ms 7 ms 192.168.4.1 2 12 ms 14 ms 13 ms 172.20.4.1 3 12 ms 15 ms 18 ms 172.20.1.1 4 30 ms 18 ms 28 ms 192.168.0.11 Trace complete. PC>tracert 192.168.1.11 Tracing route to 192.168.1.11 over a maximum of 30 hops: 1 9 ms 9 ms 9 ms 192.168.4.1 2 4 ms 8 ms 10 ms 172.20.4.1 3 21 ms 22 ms 16 ms 192.168.1.11 Trace complete. Задание 2. Настройте в той же модели сети с уже настроенным протоколом RIP2 маршрутизацию по протоколу OSPF. a) Выведите таблицу маршрутизации на каждом роутере. Объясните явление замещения записей протокола RIP. b) Выведите таблицы соседей для каждого из маршрутизаторов (show ip ospf neighbor) Router0: 172.20.0.0/24 is subnetted, 8 subnets C 172.20.0.0 is directly connected, FastEthernet6/0 O 172.20.1.0 [110/2] via 172.20.0.1, 00:05:10, FastEthernet6/0 C 172.20.2.0 is directly connected, FastEthernet8/0 O 172.20.3.0 [110/2] via 172.20.2.2, 00:05:10, FastEthernet8/0 [110/2] via 172.20.7.1, 00:05:10, FastEthernet7/0 O 172.20.4.0 [110/3] via 172.20.0.1, 00:05:10, FastEthernet6/0 [110/3] via 172.20.7.1, 00:05:10, FastEthernet7/0 O 172.20.5.0 [110/2] via 172.20.7.1, 00:05:10, FastEthernet7/0 O 172.20.6.0 [110/2] via 172.20.7.1, 00:05:10, FastEthernet7/0 C 172.20.7.0 is directly connected, FastEthernet7/0 O 192.168.0.0/24 [110/2] via 172.20.0.1, 00:05:10, FastEthernet6/0 O 192.168.1.0/24 [110/3] via 172.20.0.1, 00:05:10, FastEthernet6/0 [110/3] via 172.20.7.1, 00:05:10, FastEthernet7/0 O 192.168.2.0/24 [110/2] via 172.20.2.2, 00:05:10, FastEthernet8/0 O 192.168.3.0/24 [110/2] via 172.20.7.1, 00:05:10, FastEthernet7/0 O 192.168.4.0/24 [110/3] via 172.20.7.1, 00:05:10, FastEthernet7/0 Neighbor ID Pri State Dead Time Address Interface 192.168.0.1 1 FULL/DR 00:00:37 172.20.0.1 FastEthernet6/0 192.168.3.1 1 FULL/DR 00:00:37 172.20.7.1 FastEthernet7/0 192.168.2.1 1 FULL/DR 00:00:37 172.20.2.2 FastEthernet8/0 Router1: 172.20.0.0/24 is subnetted, 8 subnets C 172.20.0.0 is directly connected, FastEthernet6/0 C 172.20.1.0 is directly connected, FastEthernet7/0 O 172.20.2.0 [110/2] via 172.20.0.2, 00:08:07, FastEthernet6/0 O 172.20.3.0 [110/3] via 172.20.0.2, 00:00:06, FastEthernet6/0 O 172.20.4.0 [110/4] via 172.20.0.2, 00:00:06, FastEthernet6/0 O 172.20.5.0 [110/3] via 172.20.0.2, 00:00:06, FastEthernet6/0 O 172.20.6.0 [110/3] via 172.20.0.2, 00:00:06, FastEthernet6/0 O 172.20.7.0 [110/2] via 172.20.0.2, 00:08:07, FastEthernet6/0 C 192.168.0.0/24 is directly connected, FastEthernet0/0 O 192.168.1.0/24 [110/4] via 172.20.0.2, 00:00:06, FastEthernet6/0 O 192.168.2.0/24 [110/3] via 172.20.0.2, 00:08:07, FastEthernet6/0 O 192.168.3.0/24 [110/3] via 172.20.0.2, 00:00:06, FastEthernet6/0 O 192.168.4.0/24 [110/4] via 172.20.0.2, 00:00:06, FastEthernet6/0 Neighbor ID Pri State Dead Time Address Interface ^ FastEthernet6/0 192.168.1.1 1 FULL/DR 00:00:36 172.20.1.2 FastEthernet7/0 Router2: 172.20.0.0/24 is subnetted, 8 subnets O 172.20.0.0 [110/2] via 172.20.1.1, 00:00:59, FastEthernet7/0 C 172.20.1.0 is directly connected, FastEthernet7/0 R 172.20.2.0 [120/2] via 172.20.6.1, 00:00:25, FastEthernet9/0 [120/2] via 172.20.1.1, 00:00:21, FastEthernet7/0 O 172.20.3.0 [110/3] via 172.20.4.2, 00:00:59, FastEthernet8/0 C 172.20.4.0 is directly connected, FastEthernet8/0 O 172.20.5.0 [110/2] via 172.20.4.2, 00:00:59, FastEthernet8/0 C 172.20.6.0 is directly connected, FastEthernet9/0 O 172.20.7.0 [110/3] via 172.20.4.2, 00:00:59, FastEthernet8/0 O 192.168.0.0/24 [110/2] via 172.20.1.1, 00:00:59, FastEthernet7/0 C 192.168.1.0/24 is directly connected, FastEthernet0/0 R 192.168.2.0/24 [120/2] via 172.20.6.1, 00:00:25, FastEthernet9/0 O 192.168.3.0/24 [110/3] via 172.20.4.2, 00:00:59, FastEthernet8/0 O 192.168.4.0/24 [110/2] via 172.20.4.2, 00:00:59, FastEthernet8/0 Neighbor ID Pri State Dead Time Address Interface 192.168.0.1 1 FULL/BDR 00:00:37 172.20.1.1 FastEthernet7/0 192.168.4.1 1 FULL/DR 00:00:37 172.20.4.2 FastEthernet8/0 192.168.3.1 1 FULL/DROTHER 00:00:37 172.20.6.1 FastEthernet9/0 Router3: 172.20.0.0/24 is subnetted, 8 subnets O 172.20.0.0 [110/2] via 172.20.2.1, 00:02:45, FastEthernet8/0 R 172.20.1.0 [120/2] via 172.20.3.1, 00:00:17, FastEthernet9/0 [120/2] via 172.20.2.1, 00:00:10, FastEthernet8/0 C 172.20.2.0 is directly connected, FastEthernet8/0 C 172.20.3.0 is directly connected, FastEthernet9/0 R 172.20.4.0 [120/2] via 172.20.3.1, 00:00:17, FastEthernet9/0 R 172.20.5.0 [120/1] via 172.20.3.1, 00:00:17, FastEthernet9/0 R 172.20.6.0 [120/1] via 172.20.3.1, 00:00:17, FastEthernet9/0 O 172.20.7.0 [110/2] via 172.20.2.1, 00:02:45, FastEthernet8/0 R 192.168.0.0/24 [120/2] via 172.20.2.1, 00:00:10, FastEthernet8/0 R 192.168.1.0/24 [120/2] via 172.20.3.1, 00:00:17, FastEthernet9/0 C 192.168.2.0/24 is directly connected, FastEthernet0/0 R 192.168.3.0/24 [120/1] via 172.20.3.1, 00:00:17, FastEthernet9/0 R 192.168.4.0/24 [120/2] via 172.20.3.1, 00:00:17, FastEthernet9/0 Neighbor ID Pri State Dead Time Address Interface ^ FastEthernet8/0 192.168.3.1 1 FULL/DROTHER 00:00:36 172.20.3.1 FastEthernet9/0 Router4: 172.20.0.0/24 is subnetted, 8 subnets O 172.20.0.0 [110/4] via 172.20.5.2, 00:04:21, FastEthernet7/0 O 172.20.1.0 [110/3] via 172.20.5.2, 00:04:21, FastEthernet7/0 R 172.20.2.0 [120/1] via 172.20.7.2, 00:00:22, FastEthernet8/0 [120/1] via 172.20.3.2, 00:00:10, FastEthernet9/0 C 172.20.3.0 is directly connected, FastEthernet9/0 O 172.20.4.0 [110/2] via 172.20.5.2, 00:04:21, FastEthernet7/0 C 172.20.5.0 is directly connected, FastEthernet7/0 C 172.20.6.0 is directly connected, FastEthernet1/0 C 172.20.7.0 is directly connected, FastEthernet8/0 O 192.168.0.0/24 [110/4] via 172.20.5.2, 00:04:21, FastEthernet7/0 O 192.168.1.0/24 [110/3] via 172.20.5.2, 00:04:21, FastEthernet7/0 R 192.168.2.0/24 [120/1] via 172.20.3.2, 00:00:10, FastEthernet9/0 C 192.168.3.0/24 is directly connected, FastEthernet0/0 O 192.168.4.0/24 [110/2] via 172.20.5.2, 00:04:21, FastEthernet7/0 Neighbor ID Pri State Dead Time Address Interface 192.168.1.1 1 FULL/DROTHER 00:00:36 172.20.6.2 FastEthernet1/0 192.168.4.1 1 FULL/DR 00:00:36 172.20.5.2 FastEthernet7/0 ^ FastEthernet8/0 192.168.2.1 1 FULL/DROTHER 00:00:36 172.20.3.2 FastEthernet9/0 Router5: 172.20.0.0/24 is subnetted, 8 subnets O 172.20.0.0 [110/3] via 172.20.4.1, 00:05:35, FastEthernet8/0 O 172.20.1.0 [110/2] via 172.20.4.1, 00:05:35, FastEthernet8/0 R 172.20.2.0 [120/2] via 172.20.5.1, 00:00:28, FastEthernet7/0 O 172.20.3.0 [110/2] via 172.20.5.1, 00:05:35, FastEthernet7/0 C 172.20.4.0 is directly connected, FastEthernet8/0 C 172.20.5.0 is directly connected, FastEthernet7/0 O 172.20.6.0 [110/2] via 172.20.4.1, 00:05:35, FastEthernet8/0 [110/2] via 172.20.5.1, 00:05:35, FastEthernet7/0 O 172.20.7.0 [110/2] via 172.20.5.1, 00:05:35, FastEthernet7/0 O 192.168.0.0/24 [110/3] via 172.20.4.1, 00:05:35, FastEthernet8/0 O 192.168.1.0/24 [110/2] via 172.20.4.1, 00:05:45, FastEthernet8/0 R 192.168.2.0/24 [120/2] via 172.20.5.1, 00:00:28, FastEthernet7/0 O 192.168.3.0/24 [110/2] via 172.20.5.1, 00:13:46, FastEthernet7/0 C 192.168.4.0/24 is directly connected, FastEthernet0/0 Neighbor ID Pri State Dead Time Address Interface 192.168.3.1 1 FULL/BDR 00:00:31 172.20.5.1 FastEthernet7/0 192.168.1.1 1 FULL/BDR 00:00:31 172.20.4.1 FastEthernet8/0 |
Добавить документ в свой блог или на сайт
Похожие:
 | Ознакомление с man- страницами утилит. Изучение ключей, используемых при запуске утилит | | Описание адаптера: Ethernet controller: Realtek Semiconductor Co., Ltd. Rtl8101E/rtl8102e pci express Fast Ethernet controller (rev... |
| Лично мне больше нравится вывод таблицы маршрутизации с помощью команды route, т. к вывод на экран таблицы гораздо читабельнее чем... | | Произведен расчет нагрузки на сеть, анализ топологии разработанной сети и выбранного оборудования. Таким образом, работа представляет... |
| Произведен расчет нагрузки на сеть, анализ топологии разработанной сети и выбранного оборудования. Таким образом, работа представляет... | | В лабораторной работе изучалась система управления сетями Transcend Manager V 0 на примере сети мо |
| Данная курсовая работа посвящена организации потокового вещания видео в браузер средствами html5 | | Данная курсовая работа посвящена организации потокового вещания видео в браузер средствами html5 |
| Исследование структурной организации матрицы транспьютеров, определение расположения транспьютера и его соседей в сети | | В лабораторной работе изучалась система управления сетями Transcend Manager V 0 на примере, входящем в комплект дистрибутива |