tags 905752 + upstream forwarded 905752 https://github.com/oetiker/SmokePing/issues/95 thanks
Hi there, On 2018-08-08 08:49 PM, Mark Kamichoff wrote: > It appears that as of 3.16, FPing is no longer a multi-call binary and > /usr/bin/fping and /usr/bin/fping6 act the same. This ultimately > prevents the FPing probe from working properly because if a target with > both A & AAAA records is used, FPing prefers the AAAA record and > initiates a ping using IPv6 and not IPv4, which is not the intention. > The FPing probe does not support an address-family option to pass -4 or > -6 to the FPing binary so there is no way to force IPv4 name resolution. > As a result, there is no way of adding dual-stack targets to be probed > over IPv4. it appears as though this was already reported upstream: https://github.com/oetiker/SmokePing/issues/95 The bug report does have a workaround: writing wrapper scripts that add the -4 or -6 parameters to the fping binary. In order to support this without the wrapper scripts, I believe a patch to the FPing.pm and FPing6.pm probe files would need to be written to add some option that can trigger adding the appropriate flags for forcing fping to use a certain protocol. I would help out with creating such a patch but I unfortunately have no IPv6 to test it out :\ Cheers
signature.asc
Description: OpenPGP digital signature
