From owner-freebsd-net@FreeBSD.ORG Wed Oct 22 00:17:10 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37EE016A4B3 for ; Wed, 22 Oct 2003 00:17:10 -0700 (PDT) Received: from snoopy.pacific.net.au (snoopy.pacific.net.au [61.8.0.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46CC743F75 for ; Wed, 22 Oct 2003 00:17:08 -0700 (PDT) (envelope-from gjb@gbch.net) Received: from mongrel.pacific.net.au (mongrel.pacific.net.au [61.8.0.107]) h9M7H6UC009085 for ; Wed, 22 Oct 2003 17:17:06 +1000 Received: from demon.gbch.net (ppp135.dyn11.pacific.net.au [61.8.11.135]) h9M7Cfst025585 for ; Wed, 22 Oct 2003 17:12:45 +1000 Received: (qmail 2711 invoked by uid 1001); 22 Oct 2003 10:27:19 +1000 Message-ID: Date: Wed, 22 Oct 2003 10:27:18 +1000 From: Greg Black To: "Tobias P. Santos" References: <3F948E80.E81906F6@widesoft.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F948E80.E81906F6@widesoft.com.br> User-Agent: Mutt/1.4.1i; gjb-muttsend.sh 1.4 2003-04-23 X-Uptime: 4:53 X-Operating-System: FreeBSD 4.3-RELEASE i386 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.gbch.net/gjb.html X-Image-URL: http://www.gbch.net/gjb/gjb-auug048.gif X-PGP-Key-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-Request-PGP: http://www.gbch.net/keys/4B04B7D6.asc cc: freebsd-net@FreeBSD.ORG Subject: Re: Remote Boot X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Oct 2003 07:17:10 -0000 On 2003-10-20, Tobias P. Santos wrote: > I am trying to boot a FreeBSD diskless client with no success. > Actually, I can boot the client, the kernel is downloaded and begins > to boot. Then it tries to reach the DHCP/BOOT server, but this never > occurs and the machine repeats the following messages forever: There is a nasty bug in most versions of the ISC DHCP code that gave me a nasty time when attempting just this recently. Upgrading to the current DHCP code is essential.