You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When performing the arping function of a /24 subnet, the returned ARPingResult 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.
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 threaded parameter later. But iirc, we already tried with the same unsuccessful results.
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: