-
Notifications
You must be signed in to change notification settings - Fork 71
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
Scapy ARP request breaks dhcpcd #53
Comments
This causes the raspberry pi host to continually cycling through DHCP IP addresses. @gpotter2 do you have an idea why or how this is? |
This seems weird. I don't expect the packet format to differ between the two. Could you try sniffing the outgoing packets with Wireshark for instance in both case, to see if there's any difference ? |
The classes are quite different: I'll make a dump tomorrow and see what the deal is. |
Classes are different because:
But fundamentally, apart from the fact that due to the first point, kamene is likely to generate wrongly built ARP packets that may or may not be discarded by the receiver, the formats are alike. |
@gpotter2 thanks for much for the comparison between the 2! I think I've worked out the difference by looking at the packet dumps. Taken by running Here I'm sending ARP requests to a MAC that is not present on the network, you can see the ARP requests cycling through all IP addresses in the subnet but the difference is when we hit the IP address for the interface/host I'm running scapy/kamene from. kamene (192.168.178.23 was on wlan1):
scapy (192.168.178.32 was on wlan1):
scapy uses source address Any idea why this, what one is correct, and how I can do the kamene way in scapy? |
It's a bug. Happens on master |
OK cool. That's the second scapy bug I've found from use in this project 😃 Do you want me to create an issue in scapy repo? |
I use this code to send an ARP request to a MAC to see if it's alive:
If the host is alive, then
answered[0][1].hwsrc
will be the same as the destination MAC, i.e. the host replied.The problem is, when I run this 4 times in a row on my raspberry pi, I get these errors from
dhcpcd
:With
kamene
it works fine.The text was updated successfully, but these errors were encountered: