From owner-freebsd-doc@FreeBSD.ORG Thu Sep 7 14:48:41 2006 Return-Path: X-Original-To: doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 211C916A4E0; Thu, 7 Sep 2006 14:48:41 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from mx02.pub.collaborativefusion.com (mx02.pub.collaborativefusion.com [206.210.72.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50BEA43D72; Thu, 7 Sep 2006 14:48:40 +0000 (GMT) (envelope-from bseklecki@collaborativefusion.com) Received: from soundwave.pgh.priv.collaborativefusion.com (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) (Authenticated sender: seklecki) by mx02.pub.collaborativefusion.com (Postfix) with ESMTP id 74EA8AC81F; Thu, 7 Sep 2006 10:48:18 -0400 (EDT) From: "Brian A. Seklecki" To: Erik Norgaard In-Reply-To: <44FE8B9D.5080707@locolomo.org> References: <1157495592.83171.49.camel@soundwave.pgh.priv.collaborativefusion.com> <44FE8B9D.5080707@locolomo.org> Content-Type: text/plain Organization: Collaborative Fusion, Inc. Date: Thu, 07 Sep 2006 10:48:39 -0400 Message-Id: <1157640519.83171.129.camel@soundwave.pgh.priv.collaborativefusion.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: alfred@FreeBSD.org, doc@FreeBSD.org Subject: Re: FreeBSD Jumpstart Guide / PXE Docs (TFTP ONLY) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2006 14:48:41 -0000 > The problem with NFS/TFTP you mention have existed for years, I reported > it in 2004: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/74352 > > The workaround/solution is documented in the guide I wrote: > > a) Compile kernel w/o NFS support and load these as modules after boot Actually, now that I'm working it more closely (took a day to hack the Dell PE 1950 problems), it would seem that your problem has to do with a post-kernel load issue of finding the NFS root. My problem is that even when you compile the pxeboot(8) binary w/o NFS support, it still tries to do NFS (depending on DHCP variables, it seems). The other problem is that the NFS code sets the destination UDP port of the NFS Mount request to port "0", which causes my PIX Firewall to, well, you know... ~BAS > b) Specify in loader.conf that the root device is mfs > > I cleaned up the guide I wrote and I posted here some months ago if > anyone would take a look at it: > > http://www.daemonsecurity.com/pub/pxeboot/ > > Cheers, Erik -- Brian A. Seklecki Collaborative Fusion, Inc.