-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
ARPingResult of subnet is incomplete and missing results when comparing with tcpdump #4168
Comments
Hi. Did you try increasing the timeout ? |
@gpotter2 yes, no difference in result when modifying the timeout (even tried increasing it to 60 without result) |
What about with Very sorry for the delay btw. |
Hey @gpotter2, no problem. We have made our own implementation by starting a tcpdump process before executing the arping function and then processing that file when it's done. I will test with the |
Brief description
When performing the
arping
function of a /24 subnet, the returnedARPingResult
is not complete.When taking a tcpdump in the background, we can see that we receive results from a .1 up until a .254 address (with some IPs in between that do not report anything, but that is expected). If we loop over the ARPingResult object returned from the
arping
method, we get inconsistent results. Sometimes it's up until a .185 address, sometimes a .187 or best case a .190 address.Scapy version
2.5.0
Python version
3.11.2
Operating system
Debian 6.1.55-1
Additional environment information
No response
How to reproduce
Actual result
Last three lines of the response:
Expected result
Last three lines of the simultaneous running tcpdump process:
Related resources
No response
The text was updated successfully, but these errors were encountered: