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
I'm not sure what it should look like. One option would be to look for the "option overload" option and if it's present along with the underlying BOOTP layer parse the "file" and "sname" fields and add them to the DHCP options:
9.3. Option Overload
This option is used to indicate that the DHCP 'sname' or 'file'
fields are being overloaded by using them to carry DHCP options. A
DHCP server inserts this option if the returned parameters will
exceed the usual space allotted for options.
If this option is present, the client interprets the specified
additional fields after it concludes interpretation of the standard
option fields.
The code for this option is 52, and its length is 1. Legal values
for this option are:
Value Meaning
----- --------
1 the 'file' field is used to hold options
2 the 'sname' field is used to hold options
3 both fields are used to hold options
Admittedly it's an obscure feature but it comes up from time to time when it's necessary to extract all the options generated by, say, fuzzers to try to figure out what exactly they've generated or whether certain options are present. As far as I can remember an option that crashed the dhcp client in systemd/systemd#30952 (comment) was buried in the "file" field initially and it took me a while to turn it into something I can digest :-)
The text was updated successfully, but these errors were encountered:
Brief description
The DHCP "option overload" option isn't supported so it's necessary to parse DHCP options stuffed into the "file" and "sname" fields manually.
Scapy version
2b58b51
Python version
3.12.2
Operating system
Linux 6.7.10-200.fc39.x86_64
Additional environment information
No response
How to reproduce
Actual result
Expected result
I'm not sure what it should look like. One option would be to look for the "option overload" option and if it's present along with the underlying BOOTP layer parse the "file" and "sname" fields and add them to the DHCP options:
or it could do something else entirely.
(It's possible to parse the "file" and "sname" fields manually though using something like
DHCP(BOOTP(raw(p)).file)
)Related resources
According to https://datatracker.ietf.org/doc/html/rfc2132#section-9.3
Admittedly it's an obscure feature but it comes up from time to time when it's necessary to extract all the options generated by, say, fuzzers to try to figure out what exactly they've generated or whether certain options are present. As far as I can remember an option that crashed the dhcp client in systemd/systemd#30952 (comment) was buried in the "file" field initially and it took me a while to turn it into something I can digest :-)
The text was updated successfully, but these errors were encountered: