-
Notifications
You must be signed in to change notification settings - Fork 252
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
'setting SO_TIMESTAMPNS option: Protocol not available' error fping 5.1-1 on Ubuntu 22.04 over WSL1 #272
Comments
Can you please execute the following two commands inside your WSL1 Ubuntu enviroment and send back the output? Command-1 Command-2 |
Good day, below the results root@server:~# uname -a root@server:~# gcc -dM -E - </dev/null |
Can you please run the following commands? These commands look for the string
|
Should I run the commands having fping 5.1 installed or it doesn't matter? I have on the server running with version 4.2-1 because it is production server. |
Just run it, fping does not need to be installed |
root@server:~# cd /usr/include |
The better "really user-friendly" UX here, given that SO_TIMESTAMP* often require privileges not available (containers, outdated security module/syscall filters configuration, etc) would be to detect which one can be used at runtime, if any, and just do it. And be silent about it unless in debug or very-verbose mode, I guess... |
I wanted to run fping inside of my Docker container and I get the same permission issue. I don't have enough unix-fu to know which permission or capability to give my Docker container to use |
Fixed with pull request #279 |
Hi @sergiossl, could you describe the problem in more detail, perhaps copy & paste the output of The original report comprises two issues:
The first issue was addressed in the development version of (Please note that I do not have Windows and thus cannot reproduce the problem(s), neither can I verify any potential fixes.) Thanks, |
@sergiossl Please open a separate issue and describe the problem. I am closing this one as fixed since #279 has been merged. |
As the title mentioned we have Ubuntu 22.04 running over WSL1 on Windows Server 2019 and face the below error when using the fping application. Of cource the IP 192.168.1.1 is reachable from the server. The issue was replicated on three different servers with the same specs and versions.
root@server: fping 192.168.1.1
setting SO_TIMESTAMNS option: Protocol not available
setting SO_TIMESTAMNS option (IPv6): Protocol not available
192.168.1.1 is unreachable
We have tested also version 5.0-1 with the same result.
Finally we have downgraded to 4.2-1 and it worked normally.
The text was updated successfully, but these errors were encountered: