From owner-cvs-all Tue Sep 25 14: 2:15 2001 Delivered-To: cvs-all@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 25E3237B40E; Tue, 25 Sep 2001 14:02:11 -0700 (PDT) Received: (from iedowse@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f8PL2BP15445; Tue, 25 Sep 2001 14:02:11 -0700 (PDT) (envelope-from iedowse) Message-Id: <200109252102.f8PL2BP15445@freefall.freebsd.org> From: Ian Dowse Date: Tue, 25 Sep 2001 14:02:10 -0700 (PDT) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/libexec/bootpd bootp.h bootpd.c X-FreeBSD-CVS-Branch: HEAD Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG iedowse 2001/09/25 14:02:10 PDT Modified files: libexec/bootpd bootp.h bootpd.c Log: 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 Revision Changes Path 1.6 +3 -1 src/libexec/bootpd/bootp.h 1.15 +3 -3 src/libexec/bootpd/bootpd.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message