-
Notifications
You must be signed in to change notification settings - Fork 11
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 segfault #2
Comments
updated with addictional information |
gdb session
|
Hi guys: There's a buglet in your config. In the DHCPClassifier line
the That said I am totally willing to believe that there are many bugs in the DHCP elements. Can you create a file containing a DHCP trace that causes the bug? -- either as a gist or in a fork? I'm in the process of creating a test file for some of this, based on your configuration. I'll check in the current version to the -packages repository. Eddie |
Hi Eddie, Thanks for noticing the typo. However in our tests scenario it's CheckDHCPMsg that crashes, thus even before packets reached the classifier. It turns out that CheckDHCPMsg assumes incoming packets have already been marked with MarkIPHeader or CheckIPHeader and directly looks for the dhcp magic inside the packet without any safety checks such as I can understand the absence of safety checks was done for performance reasons, but I'd like to know if a crash was really intended behavior in this case. Thanks. |
i'm using this click configuration with dhcp as a ethernet level router, when there is a dhcp requests the click instance crash 100% of the times
the problem seems to be in checkDHCPMsg, this element seems to assume that all packets are valid ip packets doing a jump of 28 bytes.
i can change my conf to let i work but there is need of safety
The text was updated successfully, but these errors were encountered: