Package: iputils-ping Version: 3:20180629-2 Severity: normal Dear Maintainer,
I just got the following output from "ping ipv6-test.com": PING ipv6-test.com (5.135.165.173) 56(84) bytes of data. 64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=1 ttl=54 time=13.7 ms 64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=2 ttl=54 time=13.10 ms 64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=3 ttl=54 time=13.6 ms 64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=4 ttl=54 time=13.6 ms 64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=5 ttl=54 time=13.6 ms 64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=6 ttl=54 time=13.6 ms 64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=7 ttl=54 time=13.6 ms 64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=8 ttl=54 time=13.8 ms 64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=9 ttl=54 time=13.6 ms 64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=10 ttl=54 time=13.7 ms 64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=11 ttl=54 time=13.6 ms 64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=12 ttl=54 time=13.6 ms 64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=13 ttl=54 time=13.6 ms 64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=14 ttl=54 time=13.6 ms ^C --- ipv6-test.com ping statistics --- 14 packets transmitted, 14 received, 0% packet loss, time 33ms rtt min/avg/max/mdev = 13.586/13.671/13.979/0.156 ms The second response looks rather curious: why would it print that with a precision of 2 digits when everything else is printed with 1 digit? Looking, however, and the min/max numbers in the end, the min time is 13.586 ms -- so there actually was no measurement of 13.10 ms! And moreover, the maximum is 13.979 ms, so there should be a 14.0 ms in the list, but there is not. My guess is that ping incorrectly "rounds up" 13.979 to 13.10 (10 being "first digit after the period + 1" = 9+1) , not realizing that it should instead increment the number of seconds by 1 (and set the digit after the period to 0). In other words, it looks like decimal overflow is not handled properly. Kind regards, Ralf -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages iputils-ping depends on: ii libc6 2.28-8 ii libcap2 1:2.25-2 ii libidn2-0 2.0.5-1 ii libnettle6 3.4.1-1 Versions of packages iputils-ping recommends: ii libcap2-bin 1:2.25-2 iputils-ping suggests no packages. -- no debconf information
