>Number:         8703
>Category:       kern
>Synopsis:       NFS_BOOT_BOOTP doesn't work
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Oct 29 04:54:00 1999
>Last-Modified:
>Originator:     Charles M. Hannum
>Organization:
	Internetwork Hacker
>Release:        1999/10/14
>Environment:
	i386
System: NetBSD quiche-lorraine.mit.edu 1.4L NetBSD 1.4L (GENERIC-) #5: Fri Oct 29 04:53:03 EDT 1999 mycroft@zygorthian-space-raiders.mit.edu:/u2/src/sys/arch/i386/compile/GENERIC- i386


>Description:
	A kernel configured with NFS_BOOT_BOOTP is unable to mount its
	root file system from the network.  I consistently get:

	nfs_boot: getfh - no pathname

	tcpdump shows that the response from dhcpd to the BOOTP request
	does not, in fact, contain the root path name; thus I suspect
	this may actually be a bug in dhcpd (same vintage as kernel).

	A kernel configured with NFS_BOOT_DHCP boots correctly.

	The relevant stanza from dhcpd.conf is:

        host quiche-lorraine.mit.edu {
                hardware ethernet 00:10:4b:62:ae:3c;
                fixed-address quiche-lorraine.mit.edu;
                option root-path "/u2/export/root/quiche-lorraine";
        }

	And the aforementioned tcpdump output is:

	06:09:31.694376 0:10:4b:62:ae:3c ff:ff:ff:ff:ff:ff 0800 534: 0.0.0.0.68 > 255.255.255.255.67:  [udp sum ok] xid:0x7ffffff vend-rfc1048 [ttl 1] (id 6)
	06:09:31.715642 0:0:f4:d4:15:ef 0:10:4b:62:ae:3c 0800 342: 18.187.1.80.67 > 255.255.255.255.68:  [udp sum ok] xid:0x7ffffff Y:18.187.1.71 S:18.187.1.80 vend-rfc1048 dhpc-srvid:18.187.1.80 SM:255.255.0.0 DG:18.187.0.1 NS:18.70.0.160,18.71.0.151 HN:"quiche-lorraine.mit.edu" if-lsubnet:0 [tos 0x10] (ttl 16, id 0)
	06:09:31.718850 0:10:4b:62:ae:3c ff:ff:ff:ff:ff:ff 0806 60: arp who-has 18.187.1.71 tell 18.187.1.71

>How-To-Repeat:
	Try to boot using NFS_BOOT_BOOTP.

>Fix:
	Not known.
>Audit-Trail:
>Unformatted: