Date: Thu, 6 Nov 2003 22:16:56 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: current@freebsd.org Subject: BOOTP endless loop if no root path given Message-ID: <Pine.BSF.4.53.0311062201590.653@e0-0.zab2.int.zabbadoz.net>
next in thread | raw e-mail | index | archive | help
Hi,
when pxe-booting a kernel compiled with following options
[ for the following log this had been a kernel from 20031030-1748 UTC
including PR 57328 if it hadn't already been commited at that time ]
options MD_ROOT #MD is a potential root device
options NFSCLIENT #Network Filesystem Client
options NFS_ROOT #NFS usable as /, requires NFSCLIENT
options BOOTP # Use BOOTP to obtain IP address/hostname
# Requires NFSCLIENT and NFS_ROOT
options BOOTP_NFSROOT # NFS mount root filesystem using BOOTP info
options BOOTP_NFSV3 # Use NFS v3 to NFS mount root
options BOOTP_COMPAT # Workaround for broken bootp daemons.
options BOOTP_WIRED_TO=fxp0 # Use interface fxp0 for BOOTP
and a badly configured bootp(dhcp) server will result in endless(?) loop
to get root path from bootp server:
Sending DHCP Discover packet from interface fxp0 (xx:xx:xx:xx:xx:xx)
Received DHCP Offer packet on fxp0 from aa.bbb.cc.ddd (accepted) (no root path)
Sending DHCP Request packet from interface fxp0 (xx:xx:xx:xx:xx:xx)
Received DHCP Ack packet on fxp0 from aa.bbb.cc.ddd (accepted) (no root path)
Received DHCP Ack packet on fxp0 from aa.bbb.cc.ddd (accepted) (no root path)
Received DHCP Ack packet on fxp0 from aa.bbb.cc.ddd (accepted) (no root path)
Received DHCP Ack packet on fxp0 from aa.bbb.cc.ddd (accepted) (no root path)
DHCP/BOOTP timeout for server 255.255.255.255
Received DHCP Ack packet on fxp0 from aa.bbb.cc.ddd (accepted) (no root path)
DHCP/BOOTP timeout for server 255.255.255.255
Received DHCP Ack packet on fxp0 from aa.bbb.cc.ddd (accepted) (no root path)
DHCP/BOOTP timeout for server 255.255.255.255
Received DHCP Ack packet on fxp0 from aa.bbb.cc.ddd (accepted) (no root path)
DHCP/BOOTP timeout for server 255.255.255.255
Received DHCP Ack packet on fxp0 from aa.bbb.cc.ddd (accepted) (no root path)
DHCP/BOOTP timeout for server 255.255.255.255
Received DHCP Ack packet on fxp0 from aa.bbb.cc.ddd (accepted) (no root path)
DHCP/BOOTP timeout for server 255.255.255.255
Received DHCP Ack packet on fxp0 from aa.bbb.cc.ddd (accepted) (no root path)
DHCP/BOOTP timeout for server 255.255.255.255
Received DHCP Ack packet on fxp0 from aa.bbb.cc.ddd (accepted) (no root path)
DHCP/BOOTP timeout for server 255.255.255.255
DHCP/BOOTP timeout for server 255.255.255.255
DHCP/BOOTP timeout for server 255.255.255.255
DHCP/BOOTP timeout for server 255.255.255.255
DHCP/BOOTP timeout for server 255.255.255.255
DHCP/BOOTP timeout for server 255.255.255.255
DHCP/BOOTP timeout for server 255.255.255.255
DHCP/BOOTP timeout for server 255.255.255.255
DHCP/BOOTP timeout for server 255.255.255.255
DHCP/BOOTP timeout for server 255.255.255.255
... <another nn times> ...
DHCP/BOOTP timeout for server 255.255.255.255
DHCP/BOOTP timeout for server 255.255.255.255
DHCP/BOOTP timeout for server 255.255.255.255
Received DHCP Ack packet on fxp0 from aa.bbb.cc.ddd (accepted) (got root path)
fxp0 at aa.bb.ccc.dda server aa.bbb.cc.ddd server name aa.bbb.cc.ddd boot file path/boot/pxeboot
subnet mask 255.255.255.224 router aa.bb.ccc.dda rootfs aa.bbb.cc.ddd:/path/tftp/pxetest hostname pxetest
Questions:
a) with such a setup would it be possible to tell the kernel to get
rootfs from a local filesystem ?
giving option root-path "ufs:ad0s1a" or s.th. like that will
not work from what I have seen.
b) shouldn't the above timeout somewhen and try to fall back to
other possible rootfs'es or as a last escape reboot ?
--
Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
56 69 73 69 74 http://www.zabbadoz.net/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.53.0311062201590.653>