Control: tags -1 + bullseye

On Wed, Feb 02, 2022 at 08:36:22AM +0100, Binarus wrote:
> IMPORTANT NOTE:
> According to other reports of the same problem, ping behaves correctly when 
> IPv6 is *not* disabled at the kernel command line, but *is* instead disabled 
> via sysctl (e.g. sysctl -w net.ipv6.conf.all.disable_ipv6=1). The problem 
> occurs only when IPv6 is disabled at the kernel command line. Please note 
> also that disabling it via sysctl *in addition* to disabling it at the kernel 
> command line does not solve the problem. Actually, it does not change 
> anything, because the respective sysctl option does not have any effect if 
> IPv6 is already disabled at the kernel command line.
> 
> ping's misbehavior in this situation is not acceptable. Many people have IPv6 
> disabled at the kernel command line, and ping's misbehavior breaks a lot of 
> Nagios scripts for them, which is why I have assigned the "critical" severity 
> level.
> 
> Please fix this as soon as possible. This bug is well-known and has been 
> fixed upstream 4 (yes: four!) months ago. Please refer to the following 
> discussion:
> 
> https://github.com/iputils/iputils/issues/293

This bug by itself is entirely cosmetic and doesn't impact ping's
functionality, so I don't think it'd warrant a fix to stable by itself.
However, #920434, which covers measurement inaccuracies in ping, is
significantly more important and does warrant a stable update.  So I
think we can bundle the fix for this one with its fix and get both of
them resolved in a stable update.

Will prepare an upload and follow up with the release team.

noah

Reply via email to