X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Fri, 13 Jun 2008 10:07:59 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Bug in ping?  ICMP Sequence Number octets are reversed
Message-ID: <20080613140759.GB12561@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20080613053909 DOT GE9710 AT suncomp1 DOT spk DOT agilent DOT com> <20080613072427 DOT GA12653 AT trikaliotis DOT net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080613072427.GA12653@trikaliotis.net>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Fri, Jun 13, 2008 at 09:24:27AM +0200, Spiro Trikaliotis wrote:
>Hello,
>
>I just had a (short) session with Wireshark:
>
>* On Thu, Jun 12, 2008 at 10:39:09PM -0700 Gary Johnson wrote:
>
>> I've been using Cygwin's ping (/usr/bin/ping, ping-1.0-1) to do some 
>> testing of IP over a wireless modem.
>[...]
> 
>> It looks like someone just wrote a short integer to the sequence 
>> number field without calling htons() to perform the possible 
>> little-endian to big-endian conversion.
>
>I can confirm this for both cygwin ping and for Windows (XP SP2) ping.
>
>> I 
>> would compare it to ping on other systems, but I don't have a 
>> convenient way to sniff those packets.
>
>Well, Debian/Linux (Etch, v4.0) does it in network byte order, as one
>(might) expect. Differently to the Windows and Cygwin ping, it starts
>the sequence number with 1, not with 0.
>
>Should it be changed? I don't know, I never had a problem with it, but
>others might.

ping does not have a maintainer currently so, unless someone wants to take
over maintainership, it is not likely to be changed and bug reports against
ping are not likely to be acted upon.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/