-
Notifications
You must be signed in to change notification settings - Fork 344
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
ping endlessly running in case the network interface is lost while the pinger is not yet finished #195
Comments
I compared the behavior to the standard ping on Ubuntu which treats these packets as lost packets:
Based on that I think the PacketsSent counter should still be increased even if the write fails. |
…+ exit run loop in case count is reached
…e from the PacketsSent counter
I now had a very similar issue at a customer setup that I think has the same root cause. There the Network interface is nicely up and running but the system is directly connected to an LTE modem and the ping packets are sent but not a single response is received. Pinger in this case never reaches the .OnFinish callback.
And that's it. --> so I think when the interface is up but not a single response is received the pinger also hangs as with a network interface that is going down during pings. Note: I will now try at this customer my patch from the pull request to see if it also helps for this issue. |
My System:
Steps to reproduce:
In the console the following can be seen endlessly
In the code I saw a "FIXME" where it hangs (line 485)
The text was updated successfully, but these errors were encountered: