Package: fping Version: 4.0-6 Severity: important Dear Maintainer,
fping is broken with the kernel is given the option ipv6.disable=1 See https://github.com/schweikert/fping/issues/118 (patch being worked on) Also https://github.com/voidlinux/void-packages/issues/6456 My symptoms are exactly as above, so i wont post them redundantly -- Package-specific info: -rwxr-xr-x 1 root root 43904 Jan 2 20:13 /usr/bin/fping lrwxrwxrwx 1 root root 5 Jan 2 20:13 /usr/bin/fping6 -> fping /usr/bin/fping = cap_net_raw+ep -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fping depends on: ii libc6 2.26-6 ii libcap2-bin 1:2.25-1.2 ii netbase 5.4 fping recommends no packages. fping suggests no packages. -- no debconf information Psst! It's possible that this email contains information that is on the super secret side of confidential. So if you received it accidentally, let the sender know straight away and delete it (and the email you sent them). Also, we should let you know that any emails that come and go through Winc™ might be scanned, stored or read by Winc™ at its discretion. If you've got a question, please give us a buzz on +61 2 9335 0555 (Australia) or +64 9 271 7600 (NZ). Oh, and Winc™ does its best to avoid errors on emails it sends, but we can't promise that it will be error free. So, please don't hold it against us.
