[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

strange ping behavior - bug?



	This is normal.  The -s option defines the payload 
amount, not the total packet size.  The extra 8 bytes are the
ICMP header.



*********From a sparc

penny:/home/mike# ping -c 3 -s 1016 localhost         
PING localhost (127.0.0.1): 1016 data bytes
1024 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=1.5 ms
1024 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.8 ms
1024 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.8 ms

--- localhost ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.8/1.0/1.5 ms
penny:/home/mike# uname -a
Linux penny 2.2.8 #1 Thu May 13 13:35:35 CDT 1999 sparc unknown

*********From an intel machine

mattice:/var/state/apt/lists# ping -c 3 -s 1016 localhost
PING localhost (127.0.0.1): 1016 data bytes
1024 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=18.8 ms
1024 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=13.7 ms
1024 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=14.6 ms

--- localhost ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 13.7/15.7/18.8 ms
mattice:/var/state/apt/lists# uname -a
Linux mattice 2.0.36 #3 Sun Jan 31 10:42:14 CST 1999 i586 unknown


daniel alvarez writes:
 > When invoking the ping program with the -s option the packet-size is set
 > to the option's value plus eight additional bytes. As I only found this
 > behavior on my SPARCstation LX running slink and there is no obvios sense
 > it causes me to think that it wasn't intended to behave this way -> bug.
 > If my observation is confirmed by others I propose that somebody else does
 > a bug report, because I'm not an official Debian developer. Please check
 > also potato systems.
 > 
 > Daniel Alvarez
 > d-alvarez@gmx.de
 > 
 > -- 
 > Sent through Global Message Exchange - http://www.gmx.net
 > 
 > 
 > --  
 > To UNSUBSCRIBE, email to debian-sparc-request@lists.debian.org
 > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 > 


Reply to: