Re: srm netboot

["Dave Musser" <dmusser@donet.com>]

David,

I check the tftp .. I am using tcpd instead but I wasn't setting the secure
directory so I added that.  I checked my firewall.. I am getting through
there.
What now seems to be happening (I used the -d4 flag for bootpd) is that the
request is coming in and is then being ignored - exact message - :
Apr  1 09:54:26 starwolf in.bootpd[130]: version 2.4.3
Apr  1 09:54:26 starwolf in.bootpd[130]: bootptab mtime: Sat Apr  1 00:58:59
2000
Apr  1 09:54:26 starwolf in.bootpd[130]: reading "/etc/bootptab"
Apr  1 09:54:26 starwolf in.bootpd[130]: read 2 entries (1 hosts) from
"/etc/bootptab
Apr  1 09:54:26 starwolf in.bootpd[130]: recvd pkt from IP addr 0.0.0.0
Apr  1 09:54:26 starwolf in.bootpd[130]: bootptab mtime: Sat Apr  1 00:58:59
2000
Apr  1 09:54:26 starwolf in.bootpd[130]: ignoring request for server
starwolf.wolfentech.com from client at Ethernet address 08:00:2B:E4:49:D0

Not sure why it's being ignored.  I have checked every bit of documentation
I can find .. I think I will try a new search soon .. something like -
bootpd tftpd "ignoring request"

Dave M

----- Original Message -----
From: David Huggins-Daines <dhd@linuxcare.com>
To: Dave Musser <dmusser@donet.com>
Cc: <debian-alpha@lists.debian.org>
Sent: Thursday, March 30, 2000 9:15 PM
Subject: Re: srm netboot


> "Dave Musser" <dmusser@donet.com> writes:
>
> > 3. enabled bootpd and tcpd in the inetd.conf
>
> Did you enable tftpd?  Also, did you make sure tftpd is set up to
> serve files from /tftpboot?  I have:
>
> tftp    dgram   udp     wait    root    /usr/sbin/in.tftpd /tftpboot
>
> in my /etc/inetd.conf.
>
> > 7. typed the following at the SRM prompt on the multia
> > >>>boot -proto bootp ewa0 -flags "root=/dev/nfs nfsroot=192.168.0.130"
> >
> > and I get :
> > (boot ewa0.0.0.8.0 -flags root=/dev/nfs nfsroot=192.168.0.130)
> >
> > tyring BOOTP boot.
> >
> > Broadcasting BOOTP request...
> > .file open failed for bootp/ewa0.0.0.8.0
> > bootstrap failure
> > retrying...
>
> What does 'show ewa0*' say at this point?  If BOOTP succeeded, then
> you should see your IP configuration in the console environment
> variables.
>
> I suspect it may be a problem with TFTP...
>
> > on the nfs server .. a tail of /var/log/messages tells me that in.bootpd
has been called and is running
> >
> > a ps -ax tells me that in.bootpd is running
>
> You may also want to try ISC dhcpd, I find it works a lot better than
> the old bootpd.  Just add "allow bootp;" to your subnet block in
> dhcpd.conf.
>
> --
> David Huggins-Daines, Senior Linux Consultant, Linuxcare, Inc.
> 613.562.1239 desk, 613.223.0225 mobile
> dhd@linuxcare.com, http://www.linuxcare.com/
> Linuxcare. Support for the revolution.
>
>
> --
> To UNSUBSCRIBE, email to debian-alpha-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
>
>