Ping question

Bill Moran wmoran at collaborativefusion.com
Thu Oct 12 14:32:56 UTC 2006


In response to "Balgansuren Batsukh" <balgaa at micom.mn>:

> Hello,
> 
> I am using FreeBSD-6.2-PRERELEASE and when I ping to outside IP address get below result.
> 
> gk# ping y.y.y.y
> PING y.y.y.y (y.y.y.y): 56 data bytes
> 64 bytes from y.y.y.y: icmp_seq=0 ttl=43 time=482.571 ms
> 64 bytes from y.y.y.y: icmp_seq=0 ttl=43 time=482.934 ms (DUP!)
> 64 bytes from y.y.y.y: icmp_seq=0 ttl=43 time=483.431 ms (DUP!)
> 64 bytes from y.y.y.y: icmp_seq=1 ttl=43 time=441.772 ms
> 64 bytes from y.y.y.y: icmp_seq=1 ttl=43 time=441.978 ms (DUP!)
> 64 bytes from y.y.y.y: icmp_seq=1 ttl=43 time=442.256 ms (DUP!)
> 64 bytes from y.y.y.y: icmp_seq=2 ttl=43 time=492.160 ms
> 64 bytes from y.y.y.y: icmp_seq=3 ttl=43 time=477.828 ms
> 64 bytes from y.y.y.y: icmp_seq=4 ttl=43 time=440.011 ms
> 64 bytes from y.y.y.y: icmp_seq=4 ttl=43 time=440.372 ms (DUP!)
> 64 bytes from y.y.y.y: icmp_seq=4 ttl=43 time=440.744 ms (DUP!)
> 64 bytes from y.y.y.y: icmp_seq=5 ttl=43 time=422.430 ms
> 64 bytes from y.y.y.y: icmp_seq=5 ttl=43 time=422.790 ms (DUP!)
> 64 bytes from y.y.y.y: icmp_seq=5 ttl=43 time=423.040 ms (DUP!)
> 64 bytes from y.y.y.y: icmp_seq=6 ttl=43 time=452.691 ms
> 64 bytes from y.y.y.y: icmp_seq=7 ttl=43 time=489.581 ms
> 64 bytes from y.y.y.y: icmp_seq=8 ttl=43 time=479.235 ms
> 64 bytes from y.y.y.y: icmp_seq=9 ttl=43 time=473.910 ms
> 64 bytes from y.y.y.y: icmp_seq=9 ttl=43 time=474.271 ms (DUP!)
> 64 bytes from y.y.y.y: icmp_seq=9 ttl=43 time=474.644 ms (DUP!)
> 64 bytes from y.y.y.y: icmp_seq=10 ttl=43 time=443.461 ms
> 64 bytes from y.y.y.y: icmp_seq=11 ttl=43 time=496.951 ms
> 64 bytes from y.y.y.y: icmp_seq=12 ttl=43 time=500.120 ms
> 64 bytes from y.y.y.y: icmp_seq=13 ttl=43 time=481.664 ms
> 64 bytes from y.y.y.y: icmp_seq=13 ttl=43 time=519.755 ms (DUP!)
> 64 bytes from y.y.y.y: icmp_seq=13 ttl=43 time=520.129 ms (DUP!)
> 
> Above result shows there some row has (DUP!) message. I don't know why there such message. Where can I get more detail information about it or it is error happen to NIC?

It's unlikely that this has anything to do with FreeBSD.  It's more
likely that a networking problem is causing packets to take multiple
routes back at times, thus arriving twice.

-- 
Bill Moran
Collaborative Fusion Inc.


More information about the freebsd-stable mailing list