forked from SpiderLabs/Responder
-
-
Notifications
You must be signed in to change notification settings - Fork 771
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
DHCP poisoner crashes for IP addresses ending in F #181
Comments
im having the same issue and the workarounds above do not work. any update on this issue? |
just ran into the same issue |
Same issue here. Trying out the second workaround option. |
Adding that I just saw this as well. Attempting ncc-brian's workaround. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The DHCP poisoner Fails to handle some packets with the following error:
IP address is selected by regex at
Responder/poisoners/DHCP.py
Line 243 in 5cf6922
b'\xac\x165L'
This then lands at
Responder/poisoners/DHCP.py
Line 268 in 5cf6922
A bit of digging shows that for the packets that fail, the value for IP returned from FindIP is a byte short. When this value is then fed into inet_ntoa it errors.
Example (this is the IP that was erroring):
For the moment I'm working around it as follows:
It also appears to work if the regex adds a dot before the star:
I won't say either fix is a good idea, just that it seems to be working for me. I suggest further investigation by people who know more than I do about this.
Thanks!
The text was updated successfully, but these errors were encountered: