This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Bug in ping? ICMP Sequence Number octets are reversed


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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]