Re: BOOT/BSDP failed: no FILENAME specifiedopen /netbsd

Hi,

Here is my dhcp config, I tried to put everything back to
the way it was
when I netbooted 1.6 kernel on a G3 blue & white.
Everything seemed to
work then. Not sure why this is not working now.

ddns-update-style none;
                # Do not use any dynamic DNS features
                #
allow bootp;    # Allow bootp requests, thus the dhcp
server
                # will act as a bootp server.
                #
ddns-update-style none;
ddns-update-style none;
                # Do not use any dynamic DNS features
                #
allow bootp;    # Allow bootp requests, thus the dhcp
server
                # will act as a bootp server.
                #
authoritative;  # master DHCP server for this subnet
                #
subnet 192.168.1.0 netmask 255.255.255.0 {
                # Which network interface to listen on.
                # The zeros indicate the range of addresses
                # that are allowed to connect.
}
group {
                # Set of parameters common to all clients
                # in this "group".
                #
        option broadcast-address        192.168.1.255;
        option domain-name             
"test.net";
        option domain-name-servers      dns.test.net;
        option routers                  router.test.net;
        option subnet-mask              255.255.255.0;
                #
                # An individual client.
                #
        host client.test.net {
                hardware ethernet       00:0a:95:6d:c7:48;
                fixed-address           192.168.1.10;
                #
                # Name of the host (if the fixed address
                # doesn't resolve to a simple name).
                #
                option host-name        "client";


                #
                # Name of the bootloader or kernel
                # to download via tftp.
                #
                filename               
"ofwboot.xcf";
                #
                # The path on the NFS server.
                #
                option root-path
"/usr/client/root";
        }
 #you may paste another "host" entry here for
additional
 #clients on this network
}


Thanks,
Al

On Fri, 15 Jun 2007, Patrick Welche wrote:

> Date: Fri, 15 Jun 2007 18:42:46 +0100
> From: Patrick Welche <prlw1newn.cam.ac.uk>
> To: DataZap <azdatazap.net>
> Cc: port-macppcnetbsd.org
> Subject: Re: BOOT/BSDP failed: no FILENAME
specifiedopen /netbsd
>
> On Fri, Jun 15, 2007 at 08:33:38AM -0700, DataZap
wrote:
> > I did some googling about this. I was able to find
someone else with this
> > problem trying to install NetBSD4 BETA2 on a mini,
but not a solution.
> >
> > I can see from the logs on the the server that it
does a dhcp request,
> > gets ofwboot.xcf via tftp. It then looks like it
does another dhcp request
> > (or at least there is another line in my messages
log on the server), but
> > even if I run mountd -d, I don't even see an
attempt to connect to the nfs
> > server. Although, I can mount the nfs partition. I
think that it is ether
> > a problem with ofwboot.xcf, my dhcpd.conf (I am
using 10.10.2.0 instead of
> > 192.168.0.0)
>
> Could you show us the relevant entry from you
dhcpd.conf file? (That would
> eliminate your 2nd option..)
>
> Cheers,
>
> Patrick
>

On Fri, Jun 15, 2007 at 08:28:18PM -0700, DataZap wrote:
> Hi,
> 
> Here is my dhcp config, I tried to put everything back
to the way it was
> when I netbooted 1.6 kernel on a G3 blue & white.
Everything seemed to
> work then. Not sure why this is not working now.

Perhaps you need a next-server directive?  I did not see one
in your
config.

In older versions of the ISC DHCP server, versions that
NetBSD did use,
I believe the server "inferred" the next-server
address if your dhcpd.conf
did not supply one.  Today, the next server defaults to
0.0.0.0.

Dave

-- 
David Young             OJC Technologies
dyoungojctech.com      Urbana, IL * (217) 278-3933 ext 24