... | ... | @@ -465,6 +465,41 @@ document](https://www.ohwr.org/project/white-rabbit/uploads/0e90236d5e9b48b41424 |
|
|
??Author: Maciej Lipinski, Erik van der Bij,
|
|
|
[CERN](http://cern.ch??)
|
|
|
|
|
|
### Q: Why WR Switch is not able to get path to dot-config via DHCP when dnsmasq is used as DHCP server?
|
|
|
|
|
|
A: To fix this problem please use "dhcp-no-override" in the dnsmasq
|
|
|
configuration.
|
|
|
|
|
|
It looks like dnsmasq implementation is buggy (at least up to version
|
|
|
2.68). When switch explicitly requests "bootfile" option via DHCP, then
|
|
|
dnsmasq puts filename into the option 67 (bootfile name) in the
|
|
|
response. This is not compliant with rfc2132:
|
|
|
|
|
|
9.5 Bootfile name
|
|
|
|
|
|
This option is used to identify a bootfile when the 'file' field in
|
|
|
the DHCP header has been used for DHCP options.
|
|
|
|
|
|
If situation described above applies, then dhcp response shall contain
|
|
|
also option 52 (which it doesn't):
|
|
|
|
|
|
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.
|
|
|
[...]
|
|
|
|
|
|
No such problems with dhcpd were seen.
|
|
|
|
|
|
??Author: Adam Wujek,
|
|
|
[CERN](http://cern.ch??)
|
|
|
|
|
|
-----
|
|
|
|
|
|
## Updating firmware
|
... | ... | |