From owner-freebsd-stable@FreeBSD.ORG Thu Oct 12 14:32:56 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CABC016A494 for ; Thu, 12 Oct 2006 14:32:56 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D0DA43D9E for ; Thu, 12 Oct 2006 14:31:24 +0000 (GMT) (envelope-from wmoran@collaborativefusion.com) Received: from collaborativefusion.com (mx01.pub.collaborativefusion.com [206.210.89.201]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Thu, 12 Oct 2006 10:31:20 -0400 id 00056427.452E51B8.0000CAB1 Received: from Internal Mail-Server (206.210.89.202) by mx01 (envelope-from wmoran@collaborativefusion.com) with AES256-SHA encrypted SMTP; 12 Oct 2006 10:27:11 -0400 Date: Thu, 12 Oct 2006 10:31:19 -0400 From: Bill Moran To: Balgansuren Batsukh Message-Id: <20061012103119.b7f86096.wmoran@collaborativefusion.com> In-Reply-To: <000601c6ee07$7d1c0d50$0201000a@JACK> References: <000601c6ee07$7d1c0d50$0201000a@JACK> Organization: Collaborative Fusion X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Ping question X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 14:32:56 -0000 In response to "Balgansuren Batsukh" : > 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.