>On Tue, Jul 30, 2002 at 12:11:15PM +0900, [EMAIL PROTECTED] wrote:
>> the problem with it, as well as ICMP echo sequence #, is that the
>> endian varies by platforms. some platforms use network endian, some
>> uses host endian (little/big). it is not that simple.
>
>Thanks. I see the spec says nothing about byte order. Stevens'
>implementation sends everything in host byte order. I was looking at
>OpenBSD ping which does covert timeval fields to network byte order.
>I wonder if a heuristic could be used for payload time?
original ping distribution (from LBL?) used struct timeval on the system
as is, so you may see:
- 64bit timeval (32 + 32) with both endian if source is 32bit arch.
- 128bit timeval (64 + 64) with both endian if source is 64bit arch.
openbsd fixed endian issue as well as 64bit issue in May 1998
(sbin/ping/ping.c rev 1.32 and 1.33).
netbsd is still using original LBL? code.
dunno about other OSes.
itojun
-
This is the TCPDUMP workers list. It is archived at
http://www.tcpdump.org/lists/workers/index.html
To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
