From owner-freebsd-current@FreeBSD.ORG  Sun Apr 13 11:25:30 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 32AC837B401
	for <current@freebsd.org>; Sun, 13 Apr 2003 11:25:30 -0700 (PDT)
Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6DA9C43F85
	for <current@freebsd.org>; Sun, 13 Apr 2003 11:25:29 -0700 (PDT)
	(envelope-from barney@pit.databus.com)
Received: from pit.databus.com (localhost [127.0.0.1])
	by pit.databus.com (8.12.9/8.12.9) with ESMTP id h3DIPSdN078257
	for <current@freebsd.org>; Sun, 13 Apr 2003 14:25:28 -0400 (EDT)
	(envelope-from barney@pit.databus.com)
Received: (from barney@localhost)
	by pit.databus.com (8.12.9/8.12.9/Submit) id h3DIPSM6078256
	for current@freebsd.org; Sun, 13 Apr 2003 14:25:28 -0400 (EDT)
Date: Sun, 13 Apr 2003 14:25:28 -0400
From: Barney Wolff <barney@pit.databus.com>
To: current@freebsd.org
Message-ID: <20030413182528.GA78228@pit.databus.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
Subject: Re: ping oddity
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2003 18:25:30 -0000

The "wrong data byte" output from ping is a cosmetic bug in ping - it
starts the compare too early, with the timestamp.  So any time the
response comes back after the next request has already been sent, the
check will fail.
I've filed a PR with a suggested fix to ping.c.

-- 
Barney Wolff         http://www.databus.com/bwresume.pdf
I'm available by contract or FT, in the NYC metro area or via the 'Net.