(DUP!) ping现象

64 bytes from 10.70.70.3: icmp_seq=177 ttl=61 time=22.3 ms
64 bytes from 10.70.70.3: icmp_seq=177 ttl=61 time=24.1 ms (DUP!)
64 bytes from 10.70.70.3: icmp_seq=178 ttl=61 time=23.5 ms
64 bytes from 10.70.70.3: icmp_seq=178 ttl=61 time=24.3 ms (DUP!)
64 bytes from 10.70.70.3: icmp_seq=179 ttl=61 time=21.9 ms
64 bytes from 10.70.70.3: icmp_seq=179 ttl=61 time=23.5 ms (DUP!)
64 bytes from 10.70.70.3: icmp_seq=180 ttl=61 time=23.1 ms
64 bytes from 10.70.70.3: icmp_seq=180 ttl=61 time=24.2 ms (DUP!)
64 bytes from 10.70.70.3: icmp_seq=181 ttl=61 time=22.3 ms
64 bytes from 10.70.70.3: icmp_seq=181 ttl=61 time=23.7 ms (DUP!)
64 bytes from 10.70.70.3: icmp_seq=182 ttl=61 time=22.8 ms
64 bytes from 10.70.70.3: icmp_seq=182 ttl=61 time=24.4 ms (DUP!)
64 bytes from 10.70.70.3: icmp_seq=183 ttl=61 time=22.5 ms
64 bytes from 10.70.70.3: icmp_seq=183 ttl=61 time=23.6 ms (DUP!)
64 bytes from 10.70.70.3: icmp_seq=184 ttl=61 time=22.7 ms
64 bytes from 10.70.70.3: icmp_seq=184 ttl=61 time=24.3 ms (DUP!)

 

 

(DUP!)是来标记重复应答的。就是响应一个echo-request时，除了第一个echo-reply以外都标记成(DUP!)，windows系统上不会有这样的结果，因为微软的Ping程序不对多个回应进行解包，收到第一个包以后就丢弃后面的了，同样微软的系统默认也不回应广播地址的包，所以这种情况一般发生在linux机器上。

查了资料后发现产生这种情况有一些可能的原因：

1、对方网络使用了很多静态路由，导致产生了环路

2、对方路由器负载很高

3、有多个设备使用同个地址，比喻你ping广播地址会产生大量的这样的包