Herrschaft, собственно не хотелось бы Вас отвлекать от великих дел, однако.
Наблюдаются некоторые потери (хм, до 17%, ничего себе некоторые) при выходе в Интернет через pptp-туннель с реальным ip (контрольное время 11:00 - 11:15)
Для примера беру свои ресурсы 194.79.20.10 и 212.90.160.40. "Свои" подразумевает, что я целиком и полностью способен контролировать поведение этих ресурсов в Сети.
Для начала 194.79.20.10: Код:
~$ mtr -c100 -r 194.79.20.10
HOST: gremlin Loss% Snt Last Avg Best Wrst StDev
1. ip6.vital.ks.ua 17.0% 100 0.8 1658. 0.8 16201 4121.0
2. 80.93.116.1 8.0% 100 1.1 1954. 0.9 16058 4107.2
3. odessa1-ge-0-0-0-148.ett.ua 15.0% 100 4.5 1946. 4.2 17144 4433.5
4. ett-gw.ix.net.ua 35.0% 100 11.4 913.4 11.1 17001 3452.3
5. uarnet-10G-gw.ix.net.ua 27.0% 100 11.5 575.7 11.2 16858 2713.0
6. 194.44.100.246 30.0% 100 21.9 557.4 21.7 16715 2721.7
7. mail2.olympus.net.ua 29.0% 100 22.3 634.9 22.0 16572 2784.4
Параллельно был запущен тест на 10.100.43.1: Код:
~$ mtr -c100 -r 10.100.43.1
HOST: gremlin Loss% Snt Last Avg Best Wrst StDev
1. 10.100.43.1 1.0% 100 0.9 2.1 0.7 55.2 5.9
Ресурс 212.90.160.40, дабы не было желания спихнуть все "непонятки" на ЕТТ: Код:
~$ mtr -c100 -r 212.90.160.40
HOST: gremlin Loss% Snt Last Avg Best Wrst StDev
1. ns2.vital.ks.ua 12.0% 100 11.2 951.4 0.9 15654 3530.3
2. 80.93.116.1 12.0% 100 7.9 820.9 1.1 15549 3342.3
3. odessa1-ge-0-0-0-148.ett.ua 12.0% 100 9.2 820.0 4.3 15405 3310.8
4. ett-gw.ukrhub.net 25.0% 100 15.6 596.6 11.4 15352 2835.3
5. 212.90.160.130.kiev.ukrhub.n 12.0% 100 15.1 684.6 11.9 15209 3010.7
6. ge0-1-ramts-1.ukrhub.net 12.0% 100 15.4 679.6 12.7 15816 3045.3
7. fa0-0-rm22-1.ukrhub.net 12.0% 100 20.8 672.5 12.5 15716 3019.0
8. olden.ukrhub.net 2.3% 86 22.1 18.9 12.2 51.5 5.2
ну и параллельно на 10.100.43.1: Код:
~$ mtr -c100 -r 10.100.43.1
HOST: gremlin Loss% Snt Last Avg Best Wrst StDev
1. 10.100.43.1 1.0% 100 1.0 1.3 0.8 15.1 2.0
Опять-таки, чтобы не нарваться на вопрос о загруженности pptp-туннеля в этот момент, был запущен tshark на порту: Код:
~$ sudo tshark -tad -pni ppp99
собственно никакого "левого" трафика, который мог бы так пригрузить канал - не было!
Ну и напоследок был проведен еще один эксперимент: Код:
~$ sudo ip r r default via 10.100.43.1
Результат: Код:
~$ mtr -c100 -r 194.79.20.10
HOST: gremlin Loss% Snt Last Avg Best Wrst StDev
1. 10.100.14.1 72.0% 100 0.8 0.8 0.7 1.1 0.1
2. 10.100.100.1 88.0% 100 0.3 0.7 0.3 1.1 0.3
3. 1.2.3.5 88.0% 100 0.6 1.1 0.6 2.3 0.6
4. ip225.vital.ks.ua 59.0% 100 1.7 1.6 0.7 9.1 1.5
5. odessa1-ge-0-0-0-148.ett.ua 39.0% 100 4.5 5.6 4.0 43.0 5.2
6. ett-gw.ix.net.ua 9.0% 100 12.7 16.0 10.9 74.5 12.2
7. uarnet-10G-gw.ix.net.ua 3.0% 100 11.8 13.3 11.0 108.9 10.1
8. 194.44.100.246 72.0% 100 30.8 22.8 21.5 30.8 2.1
9. mail2.olympus.net.ua 84.0% 100 22.1 23.3 22.1 25.1 1.1
~$ mtr -c100 -r 212.90.160.40
HOST: gremlin Loss% Snt Last Avg Best Wrst StDev
1. 10.100.14.1 64.0% 100 6.6 4.1 0.7 55.7 11.9
2. 10.100.100.1 17.0% 100 0.7 0.7 0.4 3.3 0.4
3. 1.2.3.5 1.0% 100 0.6 0.9 0.4 5.2 0.6
4. ip225.vital.ks.ua 15.0% 100 0.7 2.0 0.6 19.7 3.3
5. odessa1-ge-0-0-0-148.ett.ua 0.0% 100 4.6 6.8 3.9 43.0 6.5
6. ett-gw.ukrhub.net 0.0% 100 11.5 14.4 10.8 74.4 9.6
7. 212.90.160.130.kiev.ukrhub.n 0.0% 100 12.1 14.2 11.6 83.6 8.3
8. ge0-1-ramts-1.ukrhub.net 30.0% 100 16.5 14.3 12.2 23.9 2.1
9. fa0-0-rm22-1.ukrhub.net 59.0% 100 13.7 19.5 12.0 205.2 30.7
10. olden.org.ua 79.0% 100 12.9 14.5 11.8 27.0 3.8
Я был несколько удивлен. Послушал свой локальный интерфейс: Код:
~$ tshark -pni eth1
Running as user "root" and group "root". This could be dangerous.
Capturing on eth1
2009-04-06 11:16:47.085474 93164284.000ea63779c4 -> 00000000.ffffffffffff IPX SAP Nearest Query
2009-04-06 11:16:47.362951 00:1b:fc:31:39:ae -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.41.90? Tell 10.100.41.74
2009-04-06 11:16:47.506178 93164284.0018f3b23809 -> 93164284.ffffffffffff IPX RIP Response
2009-04-06 11:16:47.628917 00:19:aa:40:96:c6 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.44.166? Tell 10.100.44.1
2009-04-06 11:16:47.753406 93164284.000ea63779c4 -> 00000000.ffffffffffff IPX SAP Nearest Query
2009-04-06 11:16:47.838026 00:19:aa:40:96:c6 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.43.10? Tell 10.100.43.1
2009-04-06 11:16:47.846900 00:1d:60:89:48:01 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.44.198? Tell 10.100.44.108
2009-04-06 11:16:47.936568 10.100.14.142 -> 10.255.255.255 UDP Source port: 1024 Destination port: 34009
2009-04-06 11:16:48.421331 93164284.000ea63779c4 -> 00000000.ffffffffffff IPX SAP Nearest Query
2009-04-06 11:16:48.538779 00:16:d4:ce:13:d4 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.40.1? Tell 10.100.40.67
2009-04-06 11:16:48.944167 10.100.14.142 -> 10.255.255.255 UDP Source port: 1024 Destination port: 34009
2009-04-06 11:16:49.089285 93164284.000ea63779c4 -> 00000000.ffffffffffff IPX SAP Nearest Query
2009-04-06 11:16:49.238815 00:19:aa:40:96:c6 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.43.11? Tell 10.100.43.1
2009-04-06 11:16:49.688863 00:16:d4:ce:13:d4 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.40.1? Tell 10.100.40.67
2009-04-06 11:16:49.717711 00:16:d4:ce:13:d4 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.40.1? Tell 10.100.40.67
2009-04-06 11:16:49.757175 93164284.000ea63779c4 -> 00000000.ffffffffffff IPX SAP Nearest Query
2009-04-06 11:16:49.954546 10.100.14.142 -> 10.255.255.255 UDP Source port: 1024 Destination port: 34009
2009-04-06 11:16:50.164331 00:19:aa:40:96:c6 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.44.198? Tell 10.100.44.1
2009-04-06 11:16:50.425123 93164284.000ea63779c4 -> 00000000.ffffffffffff IPX SAP Nearest Query
2009-04-06 11:16:50.856485 00:1d:60:89:48:01 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.44.198? Tell 10.100.44.108
2009-04-06 11:16:50.964341 10.100.14.142 -> 10.255.255.255 UDP Source port: 1024 Destination port: 34009
2009-04-06 11:16:51.093051 93164284.000ea63779c4 -> 00000000.ffffffffffff IPX SAP Nearest Query
2009-04-06 11:16:51.563079 00:1b:fc:31:39:ae -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.41.91? Tell 10.100.41.74
2009-04-06 11:16:51.760974 93164284.000ea63779c4 -> 00000000.ffffffffffff IPX SAP Nearest Query
2009-04-06 11:16:51.956456 00:1d:60:89:48:01 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.44.199? Tell 10.100.44.108
2009-04-06 11:16:51.974479 10.100.14.142 -> 10.255.255.255 UDP Source port: 1024 Destination port: 34009
2009-04-06 11:16:52.428893 93164284.000ea63779c4 -> 00000000.ffffffffffff IPX SAP Nearest Query
2009-04-06 11:16:52.984331 10.100.14.142 -> 10.255.255.255 UDP Source port: 1024 Destination port: 34009
2009-04-06 11:16:52.992155 00:19:aa:40:96:c6 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.44.182? Tell 10.100.44.1
2009-04-06 11:16:53.097129 93164284.000ea63779c4 -> 00000000.ffffffffffff IPX SAP General Query
2009-04-06 11:16:53.346682 00:18:f3:12:4e:2b -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.42.91? Tell 10.100.42.216
2009-04-06 11:16:53.738708 00:19:aa:40:96:c6 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.43.14? Tell 10.100.43.1
2009-04-06 11:16:53.764767 93164284.000ea63779c4 -> 00000000.ffffffffffff IPX SAP General Query
2009-04-06 11:16:53.892171 00:19:aa:40:96:c6 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.44.209? Tell 10.100.44.1
2009-04-06 11:16:53.994084 10.100.14.142 -> 10.255.255.255 UDP Source port: 1024 Destination port: 34009
2009-04-06 11:16:54.273516 10.100.41.110 -> 10.100.41.255 NBNS Name query NB FLEYC.LU<00>
2009-04-06 11:16:54.432677 93164284.000ea63779c4 -> 00000000.ffffffffffff IPX SAP General Query
2009-04-06 11:16:54.760386 00:16:d4:ce:13:d4 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.40.1? Tell 10.100.40.67
2009-04-06 11:16:54.854359 00:19:aa:40:96:c6 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.42.72? Tell 10.100.42.1
2009-04-06 11:16:54.855594 00:19:aa:40:96:91 -> 01:00:0c:cc:cc:cc CDP Device ID: apophis Port ID: GigabitEthernet1/0/17
2009-04-06 11:16:54.910763 00:16:d4:ce:13:d4 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.40.1? Tell 10.100.40.67
2009-04-06 11:16:54.951807 00:16:d4:ce:13:d4 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.40.1? Tell 10.100.40.67
2009-04-06 11:16:55.004175 10.100.14.142 -> 10.255.255.255 UDP Source port: 1024 Destination port: 34009
2009-04-06 11:16:55.022596 10.100.41.110 -> 10.100.41.255 NBNS Name query NB FLEYC.LU<00>
2009-04-06 11:16:55.100630 93164284.000ea63779c4 -> 00000000.ffffffffffff IPX SAP General Query
2009-04-06 11:16:55.763270 00:1b:fc:31:39:ae -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.41.92? Tell 10.100.41.74
2009-04-06 11:16:55.772573 10.100.41.110 -> 10.100.41.255 NBNS Name query NB FLEYC.LU<00>
2009-04-06 11:16:55.813314 10.100.14.74 -> 224.0.0.251 MDNS Standard query PTR _bittorrent._tcp.local, "QM" question
2009-04-06 11:16:55.960030 00:e0:4d:18:d9:38 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.41.1? Tell 10.100.41.97
2009-04-06 11:16:55.981487 93164284.001921220624 -> 00000000.ffffffffffff NBIPX Find name EVETA<20>
2009-04-06 11:16:56.014301 10.100.14.142 -> 10.255.255.255 UDP Source port: 1024 Destination port: 34009
2009-04-06 11:16:56.065861 00:1d:60:89:48:01 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.44.200? Tell 10.100.44.108
2009-04-06 11:16:56.216109 00:19:aa:40:96:c6 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.44.215? Tell 10.100.44.1
2009-04-06 11:16:56.604043 00:19:aa:40:96:c6 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.44.220? Tell 10.100.44.1
2009-04-06 11:16:57.024037 10.100.14.142 -> 10.255.255.255 UDP Source port: 1024 Destination port: 34009
2009-04-06 11:16:58.034021 10.100.14.142 -> 10.255.255.255 UDP Source port: 1024 Destination port: 34009
2009-04-06 11:16:58.463992 00:19:aa:40:96:c6 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.45.17? Tell 10.100.45.1
2009-04-06 11:16:58.527981 00:19:aa:40:96:c6 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.44.226? Tell 10.100.44.1
2009-04-06 11:16:59.046101 10.100.14.142 -> 10.255.255.255 UDP Source port: 1024 Destination port: 34009
2009-04-06 11:16:59.075888 00:50:8d:57:87:29 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.14.186? Tell 10.100.14.228
2009-04-06 11:16:59.963443 00:1b:fc:31:39:ae -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.41.93? Tell 10.100.41.74
2009-04-06 11:16:59.996206 00:16:d4:ce:13:d4 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.40.1? Tell 10.100.40.67
2009-04-06 11:17:00.037748 00:16:d4:ce:13:d4 -> ff:ff:ff:ff:ff:ff ARP Who has 10.100.40.1? Tell 10.100.40.67
^C63 packets captured
Куча layer2 бродкастов, и чей-то бродкастовый IPX трафик внутри сегмента сети (с mac-адреса 00:0e:a6:37:79:c4), и, как я подозреваю, на "кошке" не отключен cdp. Оффтоп Прошу прощенья, а зачем включать cdp на клиентских портах сети? Может в этом есть какой-то тайный смысл? Поделитесь травой :) Хотя мне конечно-же интересно знать, что Шуменский подключен через 17 порт 0-го модуля в 1-м контейнере :) Прикупить-бы себе домой 851-ю киску, можно было бы более интересно поизучать структуру сети :)
Полностью отключить cdp:
#conf t
(config)#no cdp run
(config)#end
#
Отключить cdp на конкретном порту:
#conf t
(config)#interface GigabitEthernet1/0/17
cisco(config-if)#no cdp enable
cisco(config-if)#end
#
Да еще чьи-то (10.100.14.74) мультикастовые рассылки :(
Можно сказать, что обычный сетевой мусор... Но... Но откуда-же столько потерь и откуда такие задержки? :( Откроете секрет? ;)
ps: Собственно это даже не жалоба... Сегодня вечером уезжаю в Киев и мне будет глубоко параллельно как функционирует ваша сеть, но... - истина дороже :) Ведь услуги предоставляемые компанией "Витал" я все-таки регулярно оплачиваю :)
LinkBack URL
About LinkBacks
Потери на pptp-включении....
