Revision tags: release/14.0.0 |
|
#
b3e76948 |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: two-line .h pattern
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0, release/12.3.0, release/13.0.0, release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0, release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0, release/8.4.0, release/9.1.0, release/8.3.0_cvs, release/8.3.0, release/9.0.0, release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0, release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0, release/6.0.0_cvs, release/6.0.0, release/5.4.0_cvs, release/5.4.0, release/4.11.0_cvs, release/4.11.0, release/5.3.0_cvs, release/5.3.0, release/4.10.0_cvs, release/4.10.0, release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0, release/5.1.0_cvs, release/5.1.0, release/4.8.0_cvs, release/4.8.0, release/5.0.0_cvs, release/5.0.0, release/4.7.0_cvs, release/4.6.2_cvs, release/4.6.2, release/4.6.1, release/4.6.0_cvs, release/4.5.0_cvs, release/4.4.0_cvs |
|
#
3f48bf18 |
| 25-Sep-2001 |
Ian Dowse <iedowse@FreeBSD.org> |
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
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
show more ...
|
Revision tags: release/4.3.0_cvs, release/4.3.0, release/4.2.0, release/4.1.1_cvs, release/4.1.0, release/3.5.0_cvs, release/4.0.0_cvs, release/3.4.0_cvs |
|
#
8ef94ce8 |
| 12-Nov-1999 |
Marcel Moolenaar <marcel@FreeBSD.org> |
Fix bootpd for Alpha.
bptypes.h originally defined int32 to be of type long. This obviously doesn't work on the Alpha. By defining int32 (and u_int32) in terms of int32_t (and u_int32_t) it now is w
Fix bootpd for Alpha.
bptypes.h originally defined int32 to be of type long. This obviously doesn't work on the Alpha. By defining int32 (and u_int32) in terms of int32_t (and u_int32_t) it now is what it says it should be.
Two occurrences of 'unsigned int32' have been changed to 'u_int32' for consistency.
Submitted by: Wilko Bulte <wilko@yedi.iaf.nl>
show more ...
|
Revision tags: release/3.3.0_cvs |
|
#
7f3dea24 |
| 28-Aug-1999 |
Peter Wemm <peter@FreeBSD.org> |
$Id$ -> $FreeBSD$
|
Revision tags: release/3.2.0, release/3.1.0, release/3.0.0, release/2.2.8, release/2.2.7, release/2.2.6, release/2.2.5_cvs, release/2.2.2_cvs, release/2.2.1_cvs, release/2.2.0, release/2.1.7_cvs |
|
#
9e522f7a |
| 22-Feb-1997 |
Peter Wemm <peter@FreeBSD.org> |
Revert $FreeBSD$ to $Id$
|
Revision tags: release/2.1.6_cvs, release/2.1.6.1 |
|
#
1130b656 |
| 14-Jan-1997 |
Jordan K. Hubbard <jkh@FreeBSD.org> |
Make the long-awaited change from $Id$ to $FreeBSD$
This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so
Make the long-awaited change from $Id$ to $FreeBSD$
This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
show more ...
|
Revision tags: release/2.1.5_cvs |
|
#
e08ac58b |
| 23-Jan-1996 |
Paul Traina <pst@FreeBSD.org> |
Import bootpd-2.4.3 from ftp.mc.com
|
Revision tags: release/2.1.0_cvs, release/2.0.5_cvs, release/2.0 |
|
#
44099b7b |
| 30-Sep-1994 |
Paul Traina <pst@FreeBSD.org> |
Rearrange bootpd
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0, release/12.3.0, release/13.0.0, release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0, release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0, release/8.4.0, release/9.1.0, release/8.3.0_cvs, release/8.3.0, release/9.0.0, release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0, release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0, release/6.0.0_cvs, release/6.0.0, release/5.4.0_cvs, release/5.4.0, release/4.11.0_cvs, release/4.11.0, release/5.3.0_cvs, release/5.3.0, release/4.10.0_cvs, release/4.10.0, release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0, release/5.1.0_cvs, release/5.1.0, release/4.8.0_cvs, release/4.8.0, release/5.0.0_cvs, release/5.0.0, release/4.7.0_cvs, release/4.6.2_cvs, release/4.6.2, release/4.6.1, release/4.6.0_cvs, release/4.5.0_cvs, release/4.4.0_cvs |
|
#
3f48bf18 |
| 25-Sep-2001 |
Ian Dowse <iedowse@FreeBSD.org> |
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
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
show more ...
|
Revision tags: release/4.3.0_cvs, release/4.3.0, release/4.2.0, release/4.1.1_cvs, release/4.1.0, release/3.5.0_cvs, release/4.0.0_cvs, release/3.4.0_cvs |
|
#
8ef94ce8 |
| 12-Nov-1999 |
Marcel Moolenaar <marcel@FreeBSD.org> |
Fix bootpd for Alpha.
bptypes.h originally defined int32 to be of type long. This obviously doesn't work on the Alpha. By defining int32 (and u_int32) in terms of int32_t (and u_int32_t) it now is w
Fix bootpd for Alpha.
bptypes.h originally defined int32 to be of type long. This obviously doesn't work on the Alpha. By defining int32 (and u_int32) in terms of int32_t (and u_int32_t) it now is what it says it should be.
Two occurrences of 'unsigned int32' have been changed to 'u_int32' for consistency.
Submitted by: Wilko Bulte <wilko@yedi.iaf.nl>
show more ...
|
Revision tags: release/3.3.0_cvs |
|
#
7f3dea24 |
| 28-Aug-1999 |
Peter Wemm <peter@FreeBSD.org> |
$Id$ -> $FreeBSD$
|
Revision tags: release/3.2.0, release/3.1.0, release/3.0.0, release/2.2.8, release/2.2.7, release/2.2.6, release/2.2.5_cvs, release/2.2.2_cvs, release/2.2.1_cvs, release/2.2.0, release/2.1.7_cvs |
|
#
9e522f7a |
| 22-Feb-1997 |
Peter Wemm <peter@FreeBSD.org> |
Revert $FreeBSD$ to $Id$
|
Revision tags: release/2.1.6_cvs, release/2.1.6.1 |
|
#
1130b656 |
| 14-Jan-1997 |
Jordan K. Hubbard <jkh@FreeBSD.org> |
Make the long-awaited change from $Id$ to $FreeBSD$
This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so
Make the long-awaited change from $Id$ to $FreeBSD$
This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
show more ...
|
Revision tags: release/2.1.5_cvs |
|
#
e08ac58b |
| 23-Jan-1996 |
Paul Traina <pst@FreeBSD.org> |
Import bootpd-2.4.3 from ftp.mc.com
|
Revision tags: release/2.1.0_cvs, release/2.0.5_cvs, release/2.0 |
|
#
44099b7b |
| 30-Sep-1994 |
Paul Traina <pst@FreeBSD.org> |
Rearrange bootpd
|