Привет, уважаемые.
Что такое дупы пингов?
Пингую вот такой соседский роутер:
-------------------------------------------------------------
R1#sh ver
IOS (tm) 7200 Software (C7200-JS-M), Version 12.2(2)T2, RELEASE SOFTWARE
(fc1)
ROM: System Bootstrap, Version 12.1(20000710:044039) [nlaw-121E_npeb 117],
BOOTFLASH: 7200 Software (C7200-KBOOT-M), Version 12.1(7)E,
R1 uptime is 9 weeks, 18 hours, 30 minutes
System returned to ROM by reload at 17:02:59 MSD Mon Aug 12 2002
System image file is "disk0:c7200-js-mz.122-2.T2.bin"
cisco 7206VXR (NPE400) processor (revision A) with 491520K/32768K bytes of
memory
Processor board ID 23689493
R7000 CPU at 350Mhz, Implementation 39, Rev 3.2, 256KB L2, 4096KB L3 Cache
6 slot VXR midplane, Version 2.3
Last reset from power-on
2 FastEthernet/IEEE 802.3 interface(s)
1 Channelized E3 port(s)
Configuration register is 0x2102
---------------------------------------------------------
Получаю вот такое:
======================================
[vt@jumbo vt]$ ping 80.243.96.254
PING 80.243.96.254 (80.243.96.254) from 217.76.32.10 : 56(84) bytes of data.
64 bytes from 80.243.96.254: icmp_seq=0 ttl=253 time=1.772 msec
64 bytes from 80.243.96.254: icmp_seq=0 ttl=251 time=2.073 msec (DUP!)
64 bytes from 80.243.96.254: icmp_seq=0 ttl=249 time=2.104 msec (DUP!)
64 bytes from 80.243.96.254: icmp_seq=0 ttl=247 time=2.366 msec (DUP!)
64 bytes from 80.243.96.254: icmp_seq=0 ttl=245 time=2.383 msec (DUP!)
64 bytes from 80.243.96.254: icmp_seq=0 ttl=243 time=2.669 msec (DUP!)
64 bytes from 80.243.96.254: icmp_seq=0 ttl=241 time=2.743 msec (DUP!)
64 bytes from 80.243.96.254: icmp_seq=0 ttl=239 time=3.003 msec (DUP!)
[and so on...]
64 bytes from 80.243.96.254: icmp_seq=0 ttl=17 time=21.079 msec (DUP!)
64 bytes from 80.243.96.254: icmp_seq=0 ttl=13 time=21.403 msec (DUP!)
64 bytes from 80.243.96.254: icmp_seq=0 ttl=15 time=21.537 msec (DUP!)
64 bytes from 80.243.96.254: icmp_seq=0 ttl=11 time=21.692 msec (DUP!)
64 bytes from 80.243.96.254: icmp_seq=0 ttl=9 time=21.952 msec (DUP!)
64 bytes from 80.243.96.254: icmp_seq=0 ttl=5 time=22.027 msec (DUP!)
64 bytes from 80.243.96.254: icmp_seq=0 ttl=7 time=22.108 msec (DUP!)
64 bytes from 80.243.96.254: icmp_seq=0 ttl=3 time=22.325 msec (DUP!)
64 bytes from 80.243.96.254: icmp_seq=0 ttl=1 time=22.395 msec (DUP!)
--- 80.243.96.254 ping statistics ---
1 packets transmitted, 1 packets received, +126 duplicates, 0% packet loss
round-trip min/avg/max/mdev = 1.772/12.248/22.553/6.026 ms
============
[vt@jumbo vt]$ ping 80.243.96.254 -c 1 -R
PING 80.243.96.254 (80.243.96.254) from 217.76.32.10 : 56(124) bytes of
data.
64 bytes from 80.243.96.254: icmp_seq=0 ttl=253 time=6.121 msec
NOP
RR: 217.76.32.10
217.76.33.1
80.243.97.10
80.243.96.254
193.232.244.54
217.76.33.2
217.76.32.6
217.76.32.10
--- 80.243.96.254 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/mdev = 3.473/4.797/6.121/1.324 ms
==========
[vt@jumbo vt]$ /usr/sbin/traceroute 80.243.96.254
traceroute to 80.243.96.254 (80.243.96.254), 30 hops max, 38 byte packets
1 r0-fe0-1.k16.moscow.ccs.ru (217.76.32.6) 1.857 ms 1.325 ms 1.045 ms
2 r0-fe0-16.m10.moscow.ccs.ru (217.76.33.2) 4.155 ms unreachable
(217.76.33.170) 2.265 ms r0-fe0-16.m10.moscow.ccs.ru (217.76.33.2) 1.622
ms
3 80.243.97.9 (80.243.97.9) 3.745 ms * 3.490 ms
==========================================
Моя логика ничего не подсказывает. Она просто в тупике. Как такое может
быть?
Хоть намекните?
С уважением,
Vladimir Tregub (VT60-RIPE)
CCS NOC
PS: явно происходит где-то раздвоение пакетов, причём явно на уровне IP, но
что-то я не припомню такой фичи вообще. Или это FAQ?
=============================================================================
"inet-admins" Internet access mailing list. Maintained by East Connection ISP.
Mail "unsubscribe inet-admins" to Majordomo@info.east.ru if you want to quit.
Archive is accessible on
