German-Service-Network
German-Service-Network
I think it is the same problem as #272
SO_TIMESTAMPNS exists since fping 5.0 fping 4.3 works because it is not present there. When building the lates version it is checked if "SO_TIMESTAMPNS" is set on the system. The...
Can you build https://github.com/gsnw/fping/tree/issue/272-273 and check this? I have add a runtime check for SO_TIMESTAMPNS with fallback to SO_TIMESTAMP I hope this help and works.
You can use `./configure --disable-timestamp`, this "Disable kernel-based packet timestaping (SO_TIMESTAMPNS)"
Please check again https://github.com/gsnw/fping/tree/issue/272-273. I had an error in my first version. Have it now the check at runtime again built. I hope it works, but unfortunately I can't test...
Sorry for the late reply. I was looking for a way to reproduce the message. Unfortunately I couldn't do it under Debian Docker. But now I have Windows 10 running...
Can you please check again https://github.com/gsnw/fping/tree/issue/272-273 I have add fallback to SO_TIMESTAMP. If both do not work, fping is not usable from my point of view
Fixed with pull request #279
@schweikert The issue can be closed as solved
If I see this correctly, the one function in `optparse.c` would first have to be created or extended so that the long name of the comman line option can be...