From owner-freebsd-questions@FreeBSD.ORG Mon Mar 17 16:59:35 2008
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C57DE106566C
for <freebsd-questions@freebsd.org>;
Mon, 17 Mar 2008 16:59:35 +0000 (UTC)
(envelope-from new2xen@gmail.com)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.190])
by mx1.freebsd.org (Postfix) with ESMTP id 581908FC27
for <freebsd-questions@freebsd.org>;
Mon, 17 Mar 2008 16:59:34 +0000 (UTC)
(envelope-from new2xen@gmail.com)
Received: by ti-out-0910.google.com with SMTP id j2so1705602tid.3
for <freebsd-questions@freebsd.org>;
Mon, 17 Mar 2008 09:59:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
bh=KwdlZoUsi7lH20bfie4kgGvrXGZdwkPqXG2UqUjOa+A=;
b=MlsnCXSwLQTolTmA5R8lTVsccScAtm365Mj1zlNvSGfbNpzTPB5v0sREdFUtjhtv5ZvXdSCv/xoOo6KEz2pGtp31G7nYwM+BYzgGcDMdptfh3kGYPbCWYJY3oSWjjEKJr3vrj4NPagzYz1EgT26EHdyT4Qz7oBUT2fOw4a/IpQc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
b=vd/66bT4+m+mhfJMjhEhWehCujRTmNm3y3Yhof3PqMV9mFCuEnV0ne932KTSO95g+g4rmB44x22TopRV/RccnzEhHVpjuS09/tb25OiaDXXgn1Mo93+GJ49fU3z1+AgeI3OnZ7XvVAW6vgH31KZF/Uos0AHApgkwp19UDPHg3DI=
Received: by 10.151.150.13 with SMTP id c13mr247394ybo.173.1205773171418;
Mon, 17 Mar 2008 09:59:31 -0700 (PDT)
Received: by 10.150.57.15 with HTTP; Mon, 17 Mar 2008 09:59:30 -0700 (PDT)
Message-ID: <13d67a800803170959x41902894ld2254273004a8232@mail.gmail.com>
Date: Mon, 17 Mar 2008 09:59:30 -0700
From: "vincenzo romero" <new2xen@gmail.com>
To: freebsd-questions@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: FreeBSD pxeboot unable to mount NFSroot
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Mar 2008 16:59:35 -0000
Hello all,
I would like to find out if the following is a known and documented
issue, and if so, can someone please point me to a link where I can
further understand the problem and cause.
I have encountered an issue where in a certain case a diskless client
is unable to mount NFSroot. Here is the explanation:
PXE/DHCP/TFTP and NFS server - CentOS 5.1
- Multiple clients NFSroot mount exported on a per host basis. One of
the clients is an NFS root mount image of FreeBSD 7
Configuration and Summary:
----------------------------------------
PXE/Server ----> 192.168.16.x network; subnet: 255.255.240.0
Clients
--> when clients are configured and defined in /etc/dhcpd.conf with
an assigned address in 192.168.16.x then it is able to boot
successfully - for all types of clients -(ie., FreeBSD and linux
flavors):
eg.:
host testclient1 {
hardware ethernet 00:A0:DD:EF:5B:7E;
fixed-address 192.168.16.39;
filename "pxeboot";
option root-path "192.168.16.5:/export/images/00A0DDEF5B7E/freebsd7_x64";
option host-name "testclient1";
--> when we attempt to assign a FreeBSD client with an IP address
within the 192.168.17.x --- it is unable to mount its NFSroot export:
host testclient2{
hardware ethernet 00:A0:DD:EF:57:CA;
fixed-address 192.168.17.2;
filename "pxeboot";
option root-path "192.168.16.5:/export/images/00A0DDEF57CA/freebsd7_x64";
option host-name "testclient2";
}
The clients' bootup process stops when attempting to mount the NFSroot
and drops into a "mount" prompt, forcing the user to enter a local
device to mount root. Other linux flavor clients are able to boot
successfully, these clients use the pxelinux binary as opposed to
pxeboot that freeBSD clients use.
My question: is there any known issue vis a vis the pxeboot
implementation so that it's unable to figure out that my 192.168.17.x
has a subnet of 255.255.240.0 and should be able to mount and "talk"
to its NFS server that is in 192.168.16.x?
Any advise would be greatly appreciated.
--
best,
Vince