Date: Sun, 15 Feb 2015 17:40:56 +0200 From: Beeblebrox <zaphod@berentweb.com> To: freebsd-net@freebsd.org Subject: NFS and diskless: some questions re nfs_diskless.c Message-ID: <20150215174056.34912959@rsbsd.rsb> In-Reply-To: <20150214145309.38238df2@rsbsd.rsb> References: <20150213142516.569ecc44@rsbsd.rsb> <1957238464.3335859.1423879252335.JavaMail.root@uoguelph.ca> <20150214145309.38238df2@rsbsd.rsb>
next in thread | previous in thread | raw e-mail | index | archive | help
I have several questions on implementing the features in nfs_diskless.c. Un=
derstanding these parameters are necessary to get a decent menu-driven (gru=
b2) boot process working for clients.
1. <root> for diskless clients get mounted as V2 instead of V3. I have defi=
ned { boot.nfsroot.options=3D"nfsv3" }, but has no effect. Does the kernel =
need (options BOOTP_NFSV3)? Considering that nfs_diskless.c routine checks =
"get handle size. If this succeeds, it's an NFSv3 setup" and {nd3->root_fhs=
ize =3D len; is_nfsv3 =3D 1;} might there be easier solution?
2. My DHCP server has {option root-path} defined and correctly mounts the N=
FS root. However, I would like to offer amd64/i386 choice from menu, which =
requires different root-path. I therefore plan to remove {option root-path}=
from dhcp.conf and pass nfsroot parameter in the boot menu using params ( =
boot.nfsroot.server=3D"192.168.2.1" \ boot.nfsroot.path=3D"/data/amd64" )
Yet when I do that, the kernel is booted, NIC goes up but:
re0 link state changed to UP
Received DHCP Ack packet on re0 from 192.168.2.1 (accepted)
DHCP/BOOTP timeout for server 255.255.255.255
The client is on 192.168.2.0/26 (broadcast is 192.168.2.63), Kernel has (op=
tions BOOTP/ options BOOTP_NFSROOT). Is there a solution to this?
Regards.
--=20
FreeBSD_amd64_11-Current_RadeonKMS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150215174056.34912959>