Messages in this thread | | | From | Bob Lanning <> | Subject | Re: DHCP HELP! | Date | Wed, 16 Sep 1998 08:58:19 -0700 (PDT) |
| |
You don't have the nfsroot bootp option-field set. Try setting that.
---- As written by Edward Muller: > > > --------------97D8B12077A3C6B5CCDF379F > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > I am trying to setup a linux box (kernel v2.0.35) to boot linux across > the network. I havea boot prom demo disk from incom (www.incom.com). I > have the ICS DHCP Server (it is running) and a TFTP server. The boot > disk runs OK. It issues a BOOTP/DHCP request and gets a response (log > file to follow): > > DHCPDISCOVER from 00:60:08:9d:bf:b8 via eth0 > DHCPOFFER on 192.168.0.10 to 00:60:08:9d:bf:b8 via eth0 > > (it is on a closed private network, so don't worry about addresses) > > It then start downloading my linux image from the tftp demon (log file > to follow): > tftpd: trying to get file /tftproot/bp192.168.0.10.PX > > The image boots...get to this point: > > eth0: 3c509 at 0x300 tag 1, 10baseT port, address 00 60 08 9d bf b8. > IRQ 10. > 3c509.x 1.12 6/4/97 becker@cesdis.gsfc.nasa.gov > Sending BOOTP and RARP requests........... > > and continues to try this until it times out..... > The log file on the server shows the following etries until the client > times out: > dhcpd: BOOTREQUEST from 00:60:08:9d:bf:b8 via eth0 > dhcpd: BOOTREPLY for 192.168.0.10 to sexy (00:60:08:9d:bf:b8) via eth0 > > (Sexy is the name of the PC) > > altas is the name of the server. eamhome.org is the domainname I am > using on the net. > > I think I didn't setup something right in my dhcpd.conf becuase it > doesn't seem to get the reply back from the server. Here is my > dhcpd.conf file... > # dhcpd.conf > # > # Configuration file for ISC dhcpd > # > > server-identifier atlas.eamhome.org; > > option domain-name "eamhome.org"; > > shared-network EAMHOME { > option subnet-mask 255.255.255.0; > default-lease-time 120; > max-lease-time 120; > > subnet 192.168.0.0 netmask 255.255.255.0 { > option routers 192.168.0.1; > option subnet-mask 255.255.255.0; > } > > host sexy { > hardware ethernet 00:60:08:9D:BF:B8; > fixed-address 192.168.0.10; > server-name "192.168.0.1"; > filename "/tftpboot/bp192.168.0.10.PX"; > ## option option-177 > "nfsaddrs=192.168.0.10:192.168.0.1:192.168.0.1:255.255.255.0:sexy:eth0:both"; > > option host-name "sexy"; > } > > } > > > I've tried the above conf file with and without the ## commented > section. When I use the ## section it gets past the above hangup but > can't talk to nfs the server (I now the nfs server is running). I've > alse tried using atlas.eamhome.org in the server-name option and a few > other confis...Can;t remember though... > > Any ideas would be appreciated.... > > Thank You > > --- > Edward Muller > eam@eclipse.net > > ----------------------------------- > Waste Not Computers & Supplies > http://www.wastenotcomputers.com/ > (201) 384-4444 x204 > edwardm@wastenotcomputers.com > > > > --------------97D8B12077A3C6B5CCDF379F > Content-Type: text/html; charset=us-ascii > Content-Transfer-Encoding: 7bit > > <HTML> > I am trying to setup a linux box (kernel v2.0.35) to boot linux across > the network. I havea boot prom demo disk from incom (www.incom.com). > I have the ICS DHCP Server (it is running) and a TFTP server. > The boot disk runs OK. It issues a BOOTP/DHCP request and gets a response > (log file to follow): > > <P>DHCPDISCOVER from 00:60:08:9d:bf:b8 via eth0 > <BR>DHCPOFFER on 192.168.0.10 to 00:60:08:9d:bf:b8 via eth0 > > <P>(it is on a closed private network, so don't worry about addresses) > > <P>It then start downloading my linux image from the tftp demon (log file > to follow): > <BR>tftpd: trying to get file /tftproot/bp192.168.0.10.PX > > <P>The image boots...get to this point: > > <P>eth0: 3c509 at 0x300 tag 1, 10baseT port, address 00 60 08 9d bf b8. > IRQ 10. > <BR>3c509.x 1.12 6/4/97 becker@cesdis.gsfc.nasa.gov > <BR>Sending BOOTP and RARP requests........... > > <P>and continues to try this until it times out..... > <BR>The log file on the server shows the following etries until the client > times out: > <BR>dhcpd: BOOTREQUEST from 00:60:08:9d:bf:b8 via eth0 > <BR>dhcpd: BOOTREPLY for 192.168.0.10 to sexy (00:60:08:9d:bf:b8) via eth0 > > <P>(Sexy is the name of the PC) > > <P>altas is the name of the server. eamhome.org is the domainname I am > using on the net. > > <P>I think I didn't setup something right in my dhcpd.conf becuase > it doesn't seem to get the reply back from the server. Here is my dhcpd.conf > file... > <BR># dhcpd.conf > <BR># > <BR># Configuration file for ISC dhcpd > <BR># > > <P>server-identifier atlas.eamhome.org; > > <P>option domain-name "eamhome.org"; > > <P>shared-network EAMHOME { > <BR> option subnet-mask 255.255.255.0; > <BR> default-lease-time 120; > <BR> max-lease-time 120; > > <P> subnet 192.168.0.0 netmask > 255.255.255.0 { > <BR> > option routers 192.168.0.1; > <BR> > option subnet-mask 255.255.255.0; > <BR> } > <BR> > <BR> host sexy { > <BR> > hardware ethernet 00:60:08:9D:BF:B8; > <BR> > fixed-address 192.168.0.10; > <BR> > server-name "192.168.0.1"; > <BR> > filename "/tftpboot/bp192.168.0.10.PX"; > <BR>## option option-177 "nfsaddrs=192.168.0.10:192.168.0.1:192.168.0.1:255.255.255.0:sexy:eth0:both"; > <BR> > option host-name "sexy"; > <BR> } > > <P>} > <BR> > > <P>I've tried the above conf file with and without the ## commented section. > When I use the ## section it gets past the above hangup but can't > talk to nfs the server (I now the nfs server is running). I've alse tried > using atlas.eamhome.org in the server-name option and a few other confis...Can;t > remember though... > > <P>Any ideas would be appreciated.... > > <P>Thank You > <PRE>--- > Edward Muller > eam@eclipse.net > > ----------------------------------- > Waste Not Computers & Supplies > <A HREF="http://www.wastenotcomputers.com/">http://www.wastenotcomputers.com/</A> > (201) 384-4444 x204 > edwardm@wastenotcomputers.com</PRE> > </HTML> > > --------------97D8B12077A3C6B5CCDF379F-- > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.rutgers.edu > Please read the FAQ at http://www.tux.org/lkml/ >
-- Robert Hajime Lanning Navigation Technologies Unix Systems Administrator 740 E. Arques Ave. (408) 617-5059 Sunnyvale, CA 94086 lanning@fhda.edu USA lanning@kewltech.com lanning@navtech.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |