| 2012-05-25 07:44:10 |
Sebastian Sjoholm |
bug |
|
|
added bug |
| 2012-05-25 07:49:37 |
Sebastian Sjoholm |
description |
Issue with showing the round trip time in ping, it seems that for some reason the
roundtrip time is not visible when the packet size is smaller than 16 bytes, still
there should be all space needed to keep the time information in the packet.
Accordingt to the man page (ubuntu);
"If the data space is at least eight bytes large, ping uses the first eight bytes
of this space to include a timestamp which it uses in the computation of round trip
times. If less than eight bytes of pad are specified, no round trip times are given."
Below ping with 12 bytes packet size and 16 bytes packet size, with 12 bytes there
is no roundtrip time printed out, but with the 16 bytes packet there is.
# ping 137.58.205.245 -s 12
PING 137.58.205.245 (137.58.205.245) 12(40) bytes of data.
20 bytes from 137.58.205.245: icmp_req=1 ttl=64
20 bytes from 137.58.205.245: icmp_req=2 ttl=64
^C
--- 137.58.205.245 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
# ping 137.58.205.245 -s 16
PING 137.58.205.245 (137.58.205.245) 16(44) bytes of data.
24 bytes from 137.58.205.245: icmp_req=1 ttl=64 time=0.139 ms
24 bytes from 137.58.205.245: icmp_req=2 ttl=64 time=0.120 ms
^C
--- 137.58.205.245 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
rtt min/avg/max/mdev = 0.119/0.123/0.139/0.012 ms
root@uetest:~#
System and Ping information
# ping -V
ping utility, iputils-sss20101006
# uname -a
Linux uetest 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
#
When checking the data with wireshark
12 Byte PING :
Internet Control Message Protocol
Type: 0 (Echo (ping) reply)
Code: 0
Checksum: 0xcc5a [correct]
Identifier (BE): 5504 (0x1580)
Identifier (LE): 32789 (0x8015)
Sequence number (BE): 1 (0x0001)
Sequence number (LE): 256 (0x0100)
[Response To: 1035]
[Response Time: 0,131 ms]
Data (12 bytes)
0000 00 01 02 03 04 05 06 07 08 09 0a 0b ............
Data: 000102030405060708090a0b
[Length: 12]
16 Byte PING :
Internet Control Message Protocol
Type: 0 (Echo (ping) reply)
Code: 0
Checksum: 0x3bd6 [correct]
Identifier (BE): 5506 (0x1582)
Identifier (LE): 33301 (0x8215)
Sequence number (BE): 1 (0x0001)
Sequence number (LE): 256 (0x0100)
[Response To: 2266]
[Response Time: 0,112 ms]
Data (16 bytes)
0000 83 2c bf 4f 00 00 00 00 6a 2a 02 00 00 00 00 00 .,.O....j*......
Data: 832cbf4f000000006a2a020000000000
[Length: 16]
As can be seen here is, that the roundtrip time exists in both cases, but for some reason the PING
application in Ubuntu will not show it.
To compare with OpenSUSE distribution with an different version of ping, here we can see that the ping
version is newer, as well that we get roundtrip time when the packet size is 12 and 8 bytes, with 6 bytes
we have no roundtrip time anymore.
$ ping www.ubuntu.com -s 12
PING www.ubuntu.com (91.189.90.41) 12(40) bytes of data.
20 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38 time=38.8 ms
20 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38 time=36.8 ms
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 36.821/37.837/38.853/1.016 ms
$ ping www.ubuntu.com -s 8
PING www.ubuntu.com (91.189.90.41) 8(36) bytes of data.
16 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38 time=35.7 ms
16 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38 time=36.3 ms
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 35.772/36.046/36.320/0.274 ms
$ ping www.ubuntu.com -s 6
PING www.ubuntu.com (91.189.90.41) 6(34) bytes of data.
14 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38
14 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
$ ping -V
ping utility, iputils-ss021109
$ uname -a
Linux ws7041 2.6.32.29-0.3-pae #1 SMP 2011-02-25 13:36:59 +0100 i686 i686 i386 GNU/Linux
$ lsb_release -a
LSB Version: core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-ia32:core-3.2-ia32:core-4.0-ia32:desktop-4.0-ia32:desktop-4.0-noarch:graphics-2.0-ia32:graphics-2.0-noarch:graphics-3.2-ia32:graphics-3.2-noarch:graphics-4.0-ia32:graphics-4.0-noarch
Distributor ID: SUSE LINUX
Description: SUSE Linux Enterprise Desktop 11 (i586)
Release: 11
Codename: n/a
$ |
Issue with showing the round trip time in ping, it seems that for some reason the roundtrip time is not visible when the packet size is smaller than 16 bytes, still there should be all space needed to keep the time information in the packet.
Accordingt to the man page (ubuntu);
"If the data space is at least eight bytes large, ping uses the first eight bytes of this space to include a timestamp which it uses in the computation of round trip times. If less than eight bytes of pad are specified, no round trip times are given."
Below ping with 12 bytes packet size and 16 bytes packet size, with 12 bytes there is no roundtrip time printed out, but with the 16 bytes packet there is.
# ping 137.58.205.245 -s 12
PING 137.58.205.245 (137.58.205.245) 12(40) bytes of data.
20 bytes from 137.58.205.245: icmp_req=1 ttl=64
20 bytes from 137.58.205.245: icmp_req=2 ttl=64
^C
--- 137.58.205.245 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
# ping 137.58.205.245 -s 16
PING 137.58.205.245 (137.58.205.245) 16(44) bytes of data.
24 bytes from 137.58.205.245: icmp_req=1 ttl=64 time=0.139 ms
24 bytes from 137.58.205.245: icmp_req=2 ttl=64 time=0.120 ms
^C
--- 137.58.205.245 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
rtt min/avg/max/mdev = 0.119/0.123/0.139/0.012 ms
root@uetest:~#
System and Ping information
# ping -V
ping utility, iputils-sss20101006
# uname -a
Linux uetest 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
#
When checking the data with wireshark
12 Byte PING :
Internet Control Message Protocol
Type: 0 (Echo (ping) reply)
Code: 0
Checksum: 0xcc5a [correct]
Identifier (BE): 5504 (0x1580)
Identifier (LE): 32789 (0x8015)
Sequence number (BE): 1 (0x0001)
Sequence number (LE): 256 (0x0100)
[Response To: 1035]
[Response Time: 0,131 ms]
Data (12 bytes)
0000 00 01 02 03 04 05 06 07 08 09 0a 0b ............
Data: 000102030405060708090a0b
[Length: 12]
16 Byte PING :
Internet Control Message Protocol
Type: 0 (Echo (ping) reply)
Code: 0
Checksum: 0x3bd6 [correct]
Identifier (BE): 5506 (0x1582)
Identifier (LE): 33301 (0x8215)
Sequence number (BE): 1 (0x0001)
Sequence number (LE): 256 (0x0100)
[Response To: 2266]
[Response Time: 0,112 ms]
Data (16 bytes)
0000 83 2c bf 4f 00 00 00 00 6a 2a 02 00 00 00 00 00 .,.O....j*......
Data: 832cbf4f000000006a2a020000000000
[Length: 16]
As can be seen here is, that the roundtrip time exists in both cases, but for some reason the PING application in Ubuntu will not show it.
To compare with OpenSUSE distribution with an different version of ping, here we can see that the ping version is newer, as well that we get roundtrip time when the packet size is 12 and 8 bytes, with 6 bytes we have no roundtrip time anymore.
$ ping www.ubuntu.com -s 12
PING www.ubuntu.com (91.189.90.41) 12(40) bytes of data.
20 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38 time=38.8 ms
20 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38 time=36.8 ms
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 36.821/37.837/38.853/1.016 ms
$ ping www.ubuntu.com -s 8
PING www.ubuntu.com (91.189.90.41) 8(36) bytes of data.
16 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38 time=35.7 ms
16 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38 time=36.3 ms
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 35.772/36.046/36.320/0.274 ms
$ ping www.ubuntu.com -s 6
PING www.ubuntu.com (91.189.90.41) 6(34) bytes of data.
14 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38
14 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
$ ping -V
ping utility, iputils-ss021109
$ uname -a
Linux ws7041 2.6.32.29-0.3-pae #1 SMP 2011-02-25 13:36:59 +0100 i686 i686 i386 GNU/Linux
$ lsb_release -a
LSB Version: core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-ia32:core-3.2-ia32:core-4.0-ia32:desktop-4.0-ia32:desktop-4.0-noarch:graphics-2.0-ia32:graphics-2.0-noarch:graphics-3.2-ia32:graphics-3.2-noarch:graphics-4.0-ia32:graphics-4.0-noarch
Distributor ID: SUSE LINUX
Description: SUSE Linux Enterprise Desktop 11 (i586)
Release: 11
Codename: n/a
$ |
|
| 2012-05-25 12:40:54 |
Sebastian Sjoholm |
description |
Issue with showing the round trip time in ping, it seems that for some reason the roundtrip time is not visible when the packet size is smaller than 16 bytes, still there should be all space needed to keep the time information in the packet.
Accordingt to the man page (ubuntu);
"If the data space is at least eight bytes large, ping uses the first eight bytes of this space to include a timestamp which it uses in the computation of round trip times. If less than eight bytes of pad are specified, no round trip times are given."
Below ping with 12 bytes packet size and 16 bytes packet size, with 12 bytes there is no roundtrip time printed out, but with the 16 bytes packet there is.
# ping 137.58.205.245 -s 12
PING 137.58.205.245 (137.58.205.245) 12(40) bytes of data.
20 bytes from 137.58.205.245: icmp_req=1 ttl=64
20 bytes from 137.58.205.245: icmp_req=2 ttl=64
^C
--- 137.58.205.245 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
# ping 137.58.205.245 -s 16
PING 137.58.205.245 (137.58.205.245) 16(44) bytes of data.
24 bytes from 137.58.205.245: icmp_req=1 ttl=64 time=0.139 ms
24 bytes from 137.58.205.245: icmp_req=2 ttl=64 time=0.120 ms
^C
--- 137.58.205.245 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
rtt min/avg/max/mdev = 0.119/0.123/0.139/0.012 ms
root@uetest:~#
System and Ping information
# ping -V
ping utility, iputils-sss20101006
# uname -a
Linux uetest 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
#
When checking the data with wireshark
12 Byte PING :
Internet Control Message Protocol
Type: 0 (Echo (ping) reply)
Code: 0
Checksum: 0xcc5a [correct]
Identifier (BE): 5504 (0x1580)
Identifier (LE): 32789 (0x8015)
Sequence number (BE): 1 (0x0001)
Sequence number (LE): 256 (0x0100)
[Response To: 1035]
[Response Time: 0,131 ms]
Data (12 bytes)
0000 00 01 02 03 04 05 06 07 08 09 0a 0b ............
Data: 000102030405060708090a0b
[Length: 12]
16 Byte PING :
Internet Control Message Protocol
Type: 0 (Echo (ping) reply)
Code: 0
Checksum: 0x3bd6 [correct]
Identifier (BE): 5506 (0x1582)
Identifier (LE): 33301 (0x8215)
Sequence number (BE): 1 (0x0001)
Sequence number (LE): 256 (0x0100)
[Response To: 2266]
[Response Time: 0,112 ms]
Data (16 bytes)
0000 83 2c bf 4f 00 00 00 00 6a 2a 02 00 00 00 00 00 .,.O....j*......
Data: 832cbf4f000000006a2a020000000000
[Length: 16]
As can be seen here is, that the roundtrip time exists in both cases, but for some reason the PING application in Ubuntu will not show it.
To compare with OpenSUSE distribution with an different version of ping, here we can see that the ping version is newer, as well that we get roundtrip time when the packet size is 12 and 8 bytes, with 6 bytes we have no roundtrip time anymore.
$ ping www.ubuntu.com -s 12
PING www.ubuntu.com (91.189.90.41) 12(40) bytes of data.
20 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38 time=38.8 ms
20 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38 time=36.8 ms
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 36.821/37.837/38.853/1.016 ms
$ ping www.ubuntu.com -s 8
PING www.ubuntu.com (91.189.90.41) 8(36) bytes of data.
16 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38 time=35.7 ms
16 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38 time=36.3 ms
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 35.772/36.046/36.320/0.274 ms
$ ping www.ubuntu.com -s 6
PING www.ubuntu.com (91.189.90.41) 6(34) bytes of data.
14 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38
14 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
$ ping -V
ping utility, iputils-ss021109
$ uname -a
Linux ws7041 2.6.32.29-0.3-pae #1 SMP 2011-02-25 13:36:59 +0100 i686 i686 i386 GNU/Linux
$ lsb_release -a
LSB Version: core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-ia32:core-3.2-ia32:core-4.0-ia32:desktop-4.0-ia32:desktop-4.0-noarch:graphics-2.0-ia32:graphics-2.0-noarch:graphics-3.2-ia32:graphics-3.2-noarch:graphics-4.0-ia32:graphics-4.0-noarch
Distributor ID: SUSE LINUX
Description: SUSE Linux Enterprise Desktop 11 (i586)
Release: 11
Codename: n/a
$ |
Issue with showing the round trip time in ping, it seems that for some reason the roundtrip time is not visible when the packet size is smaller than 16 bytes, still there should be all space needed to keep the time information in the packet.
Accordingt to the man page (ubuntu);
"If the data space is at least eight bytes large, ping uses the first eight bytes of this space to include a timestamp which it uses in the computation of round trip times. If less than eight bytes of pad are specified, no round trip times are given."
Below ping with 12 bytes packet size and 16 bytes packet size, with 12 bytes there is no roundtrip time printed out, but with the 16 bytes packet there is.
# ping 137.58.205.245 -s 12
PING 137.58.205.245 (137.58.205.245) 12(40) bytes of data.
20 bytes from 137.58.205.245: icmp_req=1 ttl=64
20 bytes from 137.58.205.245: icmp_req=2 ttl=64
^C
--- 137.58.205.245 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
# ping 137.58.205.245 -s 16
PING 137.58.205.245 (137.58.205.245) 16(44) bytes of data.
24 bytes from 137.58.205.245: icmp_req=1 ttl=64 time=0.139 ms
24 bytes from 137.58.205.245: icmp_req=2 ttl=64 time=0.120 ms
^C
--- 137.58.205.245 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
rtt min/avg/max/mdev = 0.119/0.123/0.139/0.012 ms
root@uetest:~#
System and Ping information
# ping -V
ping utility, iputils-sss20101006
# uname -a
Linux uetest 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
#
When checking the data with wireshark
12 Byte PING :
Internet Control Message Protocol
Type: 0 (Echo (ping) reply)
Code: 0
Checksum: 0xcc5a [correct]
Identifier (BE): 5504 (0x1580)
Identifier (LE): 32789 (0x8015)
Sequence number (BE): 1 (0x0001)
Sequence number (LE): 256 (0x0100)
[Response To: 1035]
[Response Time: 0,131 ms]
Data (12 bytes)
0000 00 01 02 03 04 05 06 07 08 09 0a 0b ............
Data: 000102030405060708090a0b
[Length: 12]
16 Byte PING :
Internet Control Message Protocol
Type: 0 (Echo (ping) reply)
Code: 0
Checksum: 0x3bd6 [correct]
Identifier (BE): 5506 (0x1582)
Identifier (LE): 33301 (0x8215)
Sequence number (BE): 1 (0x0001)
Sequence number (LE): 256 (0x0100)
[Response To: 2266]
[Response Time: 0,112 ms]
Data (16 bytes)
0000 83 2c bf 4f 00 00 00 00 6a 2a 02 00 00 00 00 00 .,.O....j*......
Data: 832cbf4f000000006a2a020000000000
[Length: 16]
As can be seen here is, that the roundtrip time exists in both cases, but for some reason the PING application in Ubuntu will not show it.
To compare with OpenSUSE distribution with an different version of ping, here we can see that the ping version is older, as well that we get roundtrip time when the packet size is 12 and 8 bytes, with 6 bytes we have no roundtrip time anymore.
$ ping www.ubuntu.com -s 12
PING www.ubuntu.com (91.189.90.41) 12(40) bytes of data.
20 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38 time=38.8 ms
20 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38 time=36.8 ms
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 36.821/37.837/38.853/1.016 ms
$ ping www.ubuntu.com -s 8
PING www.ubuntu.com (91.189.90.41) 8(36) bytes of data.
16 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38 time=35.7 ms
16 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38 time=36.3 ms
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 35.772/36.046/36.320/0.274 ms
$ ping www.ubuntu.com -s 6
PING www.ubuntu.com (91.189.90.41) 6(34) bytes of data.
14 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38
14 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
$ ping -V
ping utility, iputils-ss021109
$ uname -a
Linux ws7041 2.6.32.29-0.3-pae #1 SMP 2011-02-25 13:36:59 +0100 i686 i686 i386 GNU/Linux
$ lsb_release -a
LSB Version: core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-ia32:core-3.2-ia32:core-4.0-ia32:desktop-4.0-ia32:desktop-4.0-noarch:graphics-2.0-ia32:graphics-2.0-noarch:graphics-3.2-ia32:graphics-3.2-noarch:graphics-4.0-ia32:graphics-4.0-noarch
Distributor ID: SUSE LINUX
Description: SUSE Linux Enterprise Desktop 11 (i586)
Release: 11
Codename: n/a
$ |
|
| 2012-06-11 05:43:22 |
Sebastian Sjoholm |
summary |
Ping does not show roundtrip time |
Ping does not show roundtrip time (64bit issue) |
|
| 2012-06-11 05:52:49 |
Sebastian Sjoholm |
description |
Issue with showing the round trip time in ping, it seems that for some reason the roundtrip time is not visible when the packet size is smaller than 16 bytes, still there should be all space needed to keep the time information in the packet.
Accordingt to the man page (ubuntu);
"If the data space is at least eight bytes large, ping uses the first eight bytes of this space to include a timestamp which it uses in the computation of round trip times. If less than eight bytes of pad are specified, no round trip times are given."
Below ping with 12 bytes packet size and 16 bytes packet size, with 12 bytes there is no roundtrip time printed out, but with the 16 bytes packet there is.
# ping 137.58.205.245 -s 12
PING 137.58.205.245 (137.58.205.245) 12(40) bytes of data.
20 bytes from 137.58.205.245: icmp_req=1 ttl=64
20 bytes from 137.58.205.245: icmp_req=2 ttl=64
^C
--- 137.58.205.245 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
# ping 137.58.205.245 -s 16
PING 137.58.205.245 (137.58.205.245) 16(44) bytes of data.
24 bytes from 137.58.205.245: icmp_req=1 ttl=64 time=0.139 ms
24 bytes from 137.58.205.245: icmp_req=2 ttl=64 time=0.120 ms
^C
--- 137.58.205.245 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
rtt min/avg/max/mdev = 0.119/0.123/0.139/0.012 ms
root@uetest:~#
System and Ping information
# ping -V
ping utility, iputils-sss20101006
# uname -a
Linux uetest 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
#
When checking the data with wireshark
12 Byte PING :
Internet Control Message Protocol
Type: 0 (Echo (ping) reply)
Code: 0
Checksum: 0xcc5a [correct]
Identifier (BE): 5504 (0x1580)
Identifier (LE): 32789 (0x8015)
Sequence number (BE): 1 (0x0001)
Sequence number (LE): 256 (0x0100)
[Response To: 1035]
[Response Time: 0,131 ms]
Data (12 bytes)
0000 00 01 02 03 04 05 06 07 08 09 0a 0b ............
Data: 000102030405060708090a0b
[Length: 12]
16 Byte PING :
Internet Control Message Protocol
Type: 0 (Echo (ping) reply)
Code: 0
Checksum: 0x3bd6 [correct]
Identifier (BE): 5506 (0x1582)
Identifier (LE): 33301 (0x8215)
Sequence number (BE): 1 (0x0001)
Sequence number (LE): 256 (0x0100)
[Response To: 2266]
[Response Time: 0,112 ms]
Data (16 bytes)
0000 83 2c bf 4f 00 00 00 00 6a 2a 02 00 00 00 00 00 .,.O....j*......
Data: 832cbf4f000000006a2a020000000000
[Length: 16]
As can be seen here is, that the roundtrip time exists in both cases, but for some reason the PING application in Ubuntu will not show it.
To compare with OpenSUSE distribution with an different version of ping, here we can see that the ping version is older, as well that we get roundtrip time when the packet size is 12 and 8 bytes, with 6 bytes we have no roundtrip time anymore.
$ ping www.ubuntu.com -s 12
PING www.ubuntu.com (91.189.90.41) 12(40) bytes of data.
20 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38 time=38.8 ms
20 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38 time=36.8 ms
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 36.821/37.837/38.853/1.016 ms
$ ping www.ubuntu.com -s 8
PING www.ubuntu.com (91.189.90.41) 8(36) bytes of data.
16 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38 time=35.7 ms
16 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38 time=36.3 ms
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 35.772/36.046/36.320/0.274 ms
$ ping www.ubuntu.com -s 6
PING www.ubuntu.com (91.189.90.41) 6(34) bytes of data.
14 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38
14 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
$ ping -V
ping utility, iputils-ss021109
$ uname -a
Linux ws7041 2.6.32.29-0.3-pae #1 SMP 2011-02-25 13:36:59 +0100 i686 i686 i386 GNU/Linux
$ lsb_release -a
LSB Version: core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-ia32:core-3.2-ia32:core-4.0-ia32:desktop-4.0-ia32:desktop-4.0-noarch:graphics-2.0-ia32:graphics-2.0-noarch:graphics-3.2-ia32:graphics-3.2-noarch:graphics-4.0-ia32:graphics-4.0-noarch
Distributor ID: SUSE LINUX
Description: SUSE Linux Enterprise Desktop 11 (i586)
Release: 11
Codename: n/a
$ |
Update, 2012-06-11, Please see my updated description in the comment #1.
Issue with showing the round trip time in ping, it seems that for some reason the roundtrip time is not visible when the packet size is smaller than 16 bytes, still there should be all space needed to keep the time information in the packet.
Accordingt to the man page (ubuntu);
"If the data space is at least eight bytes large, ping uses the first eight bytes of this space to include a timestamp which it uses in the computation of round trip times. If less than eight bytes of pad are specified, no round trip times are given."
Below ping with 12 bytes packet size and 16 bytes packet size, with 12 bytes there is no roundtrip time printed out, but with the 16 bytes packet there is.
# ping 137.58.205.245 -s 12
PING 137.58.205.245 (137.58.205.245) 12(40) bytes of data.
20 bytes from 137.58.205.245: icmp_req=1 ttl=64
20 bytes from 137.58.205.245: icmp_req=2 ttl=64
^C
--- 137.58.205.245 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
# ping 137.58.205.245 -s 16
PING 137.58.205.245 (137.58.205.245) 16(44) bytes of data.
24 bytes from 137.58.205.245: icmp_req=1 ttl=64 time=0.139 ms
24 bytes from 137.58.205.245: icmp_req=2 ttl=64 time=0.120 ms
^C
--- 137.58.205.245 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
rtt min/avg/max/mdev = 0.119/0.123/0.139/0.012 ms
root@uetest:~#
System and Ping information
# ping -V
ping utility, iputils-sss20101006
# uname -a
Linux uetest 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
#
When checking the data with wireshark
12 Byte PING :
Internet Control Message Protocol
Type: 0 (Echo (ping) reply)
Code: 0
Checksum: 0xcc5a [correct]
Identifier (BE): 5504 (0x1580)
Identifier (LE): 32789 (0x8015)
Sequence number (BE): 1 (0x0001)
Sequence number (LE): 256 (0x0100)
[Response To: 1035]
[Response Time: 0,131 ms]
Data (12 bytes)
0000 00 01 02 03 04 05 06 07 08 09 0a 0b ............
Data: 000102030405060708090a0b
[Length: 12]
16 Byte PING :
Internet Control Message Protocol
Type: 0 (Echo (ping) reply)
Code: 0
Checksum: 0x3bd6 [correct]
Identifier (BE): 5506 (0x1582)
Identifier (LE): 33301 (0x8215)
Sequence number (BE): 1 (0x0001)
Sequence number (LE): 256 (0x0100)
[Response To: 2266]
[Response Time: 0,112 ms]
Data (16 bytes)
0000 83 2c bf 4f 00 00 00 00 6a 2a 02 00 00 00 00 00 .,.O....j*......
Data: 832cbf4f000000006a2a020000000000
[Length: 16]
As can be seen here is, that the roundtrip time exists in both cases, but for some reason the PING application in Ubuntu will not show it.
To compare with OpenSUSE distribution with an different version of ping, here we can see that the ping version is older, as well that we get roundtrip time when the packet size is 12 and 8 bytes, with 6 bytes we have no roundtrip time anymore.
$ ping www.ubuntu.com -s 12
PING www.ubuntu.com (91.189.90.41) 12(40) bytes of data.
20 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38 time=38.8 ms
20 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38 time=36.8 ms
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 36.821/37.837/38.853/1.016 ms
$ ping www.ubuntu.com -s 8
PING www.ubuntu.com (91.189.90.41) 8(36) bytes of data.
16 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38 time=35.7 ms
16 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38 time=36.3 ms
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 35.772/36.046/36.320/0.274 ms
$ ping www.ubuntu.com -s 6
PING www.ubuntu.com (91.189.90.41) 6(34) bytes of data.
14 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=1 ttl=38
14 bytes from jujube.canonical.com (91.189.90.41): icmp_seq=2 ttl=38
^C
--- www.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
$ ping -V
ping utility, iputils-ss021109
$ uname -a
Linux ws7041 2.6.32.29-0.3-pae #1 SMP 2011-02-25 13:36:59 +0100 i686 i686 i386 GNU/Linux
$ lsb_release -a
LSB Version: core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-ia32:core-3.2-ia32:core-4.0-ia32:desktop-4.0-ia32:desktop-4.0-noarch:graphics-2.0-ia32:graphics-2.0-noarch:graphics-3.2-ia32:graphics-3.2-noarch:graphics-4.0-ia32:graphics-4.0-noarch
Distributor ID: SUSE LINUX
Description: SUSE Linux Enterprise Desktop 11 (i586)
Release: 11
Codename: n/a
$ |
|
| 2012-11-08 09:58:20 |
YOSHIFUJI Hideaki / =?iso-2022-jp?B?GyRCNUhGIzFRTEAbKEI=?= |
iputils (Ubuntu): status |
New |
Invalid |
|
| 2012-11-08 10:40:37 |
Sebastian Sjoholm |
iputils (Ubuntu): status |
Invalid |
New |
|
| 2020-11-09 17:57:48 |
Launchpad Janitor |
iputils (Ubuntu): status |
New |
Confirmed |
|
