Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

debian no longer ships a fping6 binary #95

Closed
normanr opened this issue Aug 28, 2017 · 3 comments
Closed

debian no longer ships a fping6 binary #95

normanr opened this issue Aug 28, 2017 · 3 comments

Comments

@normanr
Copy link

normanr commented Aug 28, 2017

I upgraded to fping v4 on my debian machine and noticed that all my FPing6 probes stopped working. I ended up making two tiny fping4/fping6 scripts to pass -4/-6 to fping, but it would be nice to be able to set protocol version in FPing probe settings and not use wrapper scripts.

@oetiker
Copy link
Owner

oetiker commented Aug 28, 2017

I agree ... care to provide a patch ?

@lelutin
Copy link
Contributor

lelutin commented Aug 18, 2018

@oetiker would a patch adding a config option for the probes FPing and FPing6 probes that "enforces protocol" that would then add the parameters to the binary calls be what you had in mind, or should be just change the calls directly and not care to make it configurable?

@oetiker
Copy link
Owner

oetiker commented Aug 21, 2018

how about a patch that makes the FPing probe with the current version of fping ? we then would not need Fping6 anymore.

lelutin referenced this issue in lelutin/SmokePing Aug 26, 2018
Starting with FPing 3.16, the IPv6 functionality was merged in the main
binary and fping now respects the system-wide setting for address
resolution. This means that when we add a target that has both an A
record and a AAAA record, the probe tests the IPv6 address by default.

This breaks the expectation that the FPing probe tests IPv4 and that the
FPing6 probe checks IPv6.

To restore this, we can now add a parameter to the probes to force the
protocol version to be 4 or 6.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants