diff options
| author | iedowse <iedowse@FreeBSD.org> | 2001-09-25 21:02:10 +0000 |
|---|---|---|
| committer | iedowse <iedowse@FreeBSD.org> | 2001-09-25 21:02:10 +0000 |
| commit | c6a3ab8fc67f4bf691c736efb178a8032e64d625 (patch) | |
| tree | a04ce0be4a63acbe2c95a7c92f94e67beae260fa /sys/kern | |
| parent | 2cba2e955a43aa51407b34fbec17c91a9b625161 (diff) | |
| download | FreeBSD-src-c6a3ab8fc67f4bf691c736efb178a8032e64d625.zip FreeBSD-src-c6a3ab8fc67f4bf691c736efb178a8032e64d625.tar.gz | |
RFC2132 is not clear about whether the "Maximum DHCP Message Size"
refers to the size of the whole ethernet packet, just the DHCP
message within the UDP payload, or something else. bootpd interpreted
it as a maximum UDP payload size, so it could end up sending
fragmented packets to clients (such as some versions of Etherboot)
that used different interpretations of the maximum message size.
Switch to the most conservative interpretation: ensure that the
ethernet packet containing the response is no larger than the
specified maximum message size. This matches the behaviour of
the ISC dhcpd.
MFC after: 1 week
Diffstat (limited to 'sys/kern')
0 files changed, 0 insertions, 0 deletions
