Your message dated Fri, 11 Oct 2024 11:02:21 +0000
with message-id <[email protected]>
and subject line Bug#1040313: fixed in iputils 3:20221126-1+deb12u1
has caused the Debian Bug report #1040313,
regarding iputils-ping: incorrect results (responses from different addresses
should not be accounted as received)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1040313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040313
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: iputils-ping
Version: 3:20221126-1
Severity: normal
Hi,
After upgrading our monitoring host from bullseye to bookworm, our
check_ping plugin suddenly reports that hosts that have been down for
months are up again for a few minutes.
I've looked into this and it seems we are running so many ping checks,
that the randomly selected id from a ping to host A sometimes matches
to the id of the ping to host B. Since all icmp responses are forwarded
to both ping processes on the system. I've looked at the code between
the ping command from bullseye and bookworm and it seems that the code
from bookworm accounts for these wrong packets: it shows the response
but marks it as "DIFFERENT ADDRESS!".
This is correct, but these packets are then accounted for in the number
of responses received and this makes it seem that a host is up when it
isn't:
root@iridium:~# ping 10.89.22.23 -v
ping: sock4.fd: 3 (socktype: SOCK_RAW), sock6.fd: 4 (socktype: SOCK_RAW),
hints.ai_family: AF_UNSPEC
ai->ai_family: AF_INET, ai->ai_canonname: '10.89.22.23'
PING 10.89.22.23 (10.89.22.23) 56(84) bytes of data.
64 bytes from 10.89.22.179: icmp_seq=1 ident=47195 ttl=252 time=1.04 ms
(DIFFERENT ADDRESS!)
64 bytes from 10.89.22.179: icmp_seq=2 ident=47195 ttl=252 time=5.79 ms
(DIFFERENT ADDRESS!)
64 bytes from 10.89.22.179: icmp_seq=3 ident=47195 ttl=252 time=69.8 ms
(DIFFERENT ADDRESS!)
64 bytes from 10.89.22.179: icmp_seq=4 ident=47195 ttl=252 time=0.988 ms
(DIFFERENT ADDRESS!)
64 bytes from 10.89.22.179: icmp_seq=5 ident=47195 ttl=252 time=0.975 ms
(DIFFERENT ADDRESS!)
^C
--- 10.89.22.23 ping statistics ---
1022 packets transmitted, 5 received, 99.5108% packet loss, time 1045246ms
rtt min/avg/max/mdev = 0.975/15.720/69.808/27.107 ms, pipe 994
Since 10.89.22.23 (the one we are pinging) is down, there are no responses from
this system.
But because the ident (47195 in the example above) matches a different ping to
10.89.22.179,
the responses are also parsed by this ping. It correctly shows that the
response came from
a different address, but still adds the 5 packets as 5 valid received packets,
which makes
the packet loss 99.5% instead of 100%.
Those invalid packets should not count as valid responses as they are not from
the correct
host.
I've compared the source code of ping between the bullseye and bookworm
version, and the
bullseye version discarded the packets if this occured.
This change results in hosts that are actually down being reported as up in our
monitoring
system.
Regards,
Rik
-- System Information:
Debian Release: 12.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-9-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages iputils-ping depends on:
ii libc6 2.36-9
ii libcap2 1:2.66-4
ii libcap2-bin 1:2.66-4
ii libidn2-0 2.3.3-1+b1
iputils-ping recommends no packages.
iputils-ping suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: iputils
Source-Version: 3:20221126-1+deb12u1
Done: Noah Meyerhans <[email protected]>
We believe that the bug you reported is fixed in the latest version of
iputils, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Noah Meyerhans <[email protected]> (supplier of updated iputils package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 24 Sep 2024 13:00:36 -0400
Source: iputils
Architecture: source
Version: 3:20221126-1+deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Noah Meyerhans <[email protected]>
Changed-By: Noah Meyerhans <[email protected]>
Closes: 1040313
Changes:
iputils (3:20221126-1+deb12u1) bookworm; urgency=medium
.
* Import upstream fix for incorrect ping receiving packets intended for other
processes (Closes: #1040313)
Checksums-Sha1:
3bcdb0bd309db9b0eeb34cfa13bdffed0768b56a 2211 iputils_20221126-1+deb12u1.dsc
103b20ca7d2a02839c2d2c792ac2407dffa58086 11876
iputils_20221126-1+deb12u1.debian.tar.xz
f2cdd45676c45d2f60b7efca45aed2efd4de6eee 6907
iputils_20221126-1+deb12u1_source.buildinfo
Checksums-Sha256:
570f4053315d3c5dcaed6d0902dc9302581c29023eea805dc92bc34199192f07 2211
iputils_20221126-1+deb12u1.dsc
028568563e037c0a5631c63dfe04e5a2649bbbb867b36bd772aa0290b3e1cab8 11876
iputils_20221126-1+deb12u1.debian.tar.xz
639b04c55bc45a75edef0d546a6ebeb2b28b5cba24794fbdc51d574874613393 6907
iputils_20221126-1+deb12u1_source.buildinfo
Files:
a3b03dab762eb7a8e2c698db2cfb6a77 2211 net optional
iputils_20221126-1+deb12u1.dsc
0cfd32fd5301f58e0972c3a0b1d6ecb1 11876 net optional
iputils_20221126-1+deb12u1.debian.tar.xz
744fbaf1cd4ac4cc487f210ce3d4b3f9 6907 net optional
iputils_20221126-1+deb12u1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE5G+E0xEKhJuZ7RJ34+c1IpshdTUFAmcH9RwRHG5vYWhtQGRl
Ymlhbi5vcmcACgkQ4+c1IpshdTVs2g/9GTV1HOHIU67EnCV20STZn7pnbjS6VhAy
ctQX9Qf9nbRjM7qZ5BbGY1ksgtoAnTxVPLrwe79XTCy491i6PsqjUhu/yuD8mfpI
j9VZEkx2a3XdLbp9MdbE+9BFCd5HgU1V+hmNhtwY5uzNU8CxndjybK03VURLHZ9E
rpRkwYiU2bSIWaiFVsN1Kj4ViAphEUpVoUA2bLVHqpPieYDNjt+raaMbrlmPLmaG
SXz4HPMHP3ll21lm6CdFzlJGcIHjWjunS15O6jIZnGbRak/irKok9GJkp/338J9h
o7AkMHKIRJxAW13G7U+itvCTrlF3LqJ1G5NRrMEdXM6UqfvInDITqcFCd4VgpkY4
3RYDxpGBsunWCwNxixTFHPpvAkP2H0gFt0Zc7U8Gox32NfK3yuhpBoSrqnjOG42w
5F+TmQSIAGHguruqiaLPUtGA6QiANnVueyOPbvwb7Hzod9FHIejEQ8GGUY7gskdI
TfiHPsZ3aJ/n2m+YRgKe1RVLA9JzY5CP0xnAb2hyn8G9XF3TqnJdsqcWedM4flYb
f5sevjhRorvg7sPz6SHwbpFYYc0VLvxBnh+PdVMR0S6K1sLG8iVWP0RPS+ZGn5yA
RkF2iRs1u3qCwJaF6WNbBiVRaF/t4LA9jPK9BxaUm/7cjfPwvfw/Zq4cA6WreHCG
4cBFuEho3oU=
=NbKE
-----END PGP SIGNATURE-----
pgpG7AKyshBnK.pgp
Description: PGP signature
--- End Message ---
