Not handling packets with empty body properly? about staticdhcpd

[GoogleCodeExporter]

I've got a more transparent solution for this problem, though I'm quite 
surprised you actually encountered it. Do you happen to know what device was 
sending these packets?

Thank you very much for this report.

Original comment by red.hamsterx on 15 Jan 2011 at 2:40

• Changed state: Started

[GoogleCodeExporter]

http://code.google.com/p/staticdhcpd/source/detail?r=304 addresses this issue; 
the fix is in the dev/ branch.

My solution was to make all of the is?Packet() functions return False in the 
event that the message-type is not set. This will cause the packet to fail 
through all of the tests and get caught by the general handler, without needing 
to look at a private variable.

I'll merge it into trunk after it's had a chance to soak on my server over the 
weekend, and once I've revamped logging and the web interface. You should 
probably expect an official release later this weekend or early next week.

Original comment by red.hamsterx on 15 Jan 2011 at 2:55

• Changed state: Fixed

[GoogleCodeExporter]

I do not know where the packets came from.

Original comment by [email protected] on 15 Jan 2011 at 12:35

[GoogleCodeExporter]

That's too bad. :(

If you do find out, please let me know. That's a pretty significant RFC 
violation and I'd like to report it to the device's vendor, since they may not 
be aware of the problem. 

Original comment by red.hamsterx on 15 Jan 2011 at 7:07