Remote boot configuration -- and "authoritative" question.

[Bill Moseley]

I have an existing LAN with a dhcpd server.  I  added a second
server that has two NICs and dhcpd running.

eth1 will be on the existing LAN and get its IP from the LAN's dhcpd server.

I want to also run a dhcpd server on this new server to serve
addresses for the subnet on this new machine's eth0.

I'm only defining a subnet for the subnet on eth0:


    # should this be inside the "subnet" section?
    authoritative;

    subnet 192.168.0.0 netmask 255.255.255.0 {
        range 192.168.0.20 192.168.0.250;
        option domain-name "example.com";
        option domain-name-servers 192.168.0.1;
        option broadcast-address 192.168.0.255;
        option routers 192.168.0.1;
        option subnet-mask 255.255.255.0;

        option root-path "/opt/ltsp/i386";
        if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
            filename "/ltsp/i386/pxelinux.0";
        } else {
            filename "/ltsp/i386/nbi.img";
        }
    }

Now, this works to boot my i386 clients and I see in my logs:

Nov  3 18:11:52 ltsps0 dhcpd: DHCPACK on 192.168.0.250 to 00:0f:1f:7a:53:3c via eth0
Nov  3 18:11:52 ltsps0 in.tftpd[6242]: tftp: client does not accept options 
...y
Nov  3 18:12:01 ltsps0 nbdrootd[6256]: connect from 192.168.0.250 (192.168.0.250)
Nov  3 18:12:01 ltsps0 nbd_server[6257]: connect from 192.168.0.250, assigned file is /opt/ltsp/images/i386.img
Nov  3 18:12:01 ltsps0 nbd_server[6257]: Size of exported file/device is 143855616
Nov  3 18:12:06 ltsps0 ldminfod[6259]: connect from 192.168.0.250 (192.168.0.250)


I want to also boot a few powerpc clients, so I added these to dhcpd.conf:

group {
    option root-path "/opt/ltsp/powerpc";

    filename "/ltsp/powerpc/yaboot";
    #filename "yaboot";  # Tried this, too

    host ibook  { hardware ethernet 00:14:51:32:BA:44; }
    host mac1   { hardware ethernet 00:30:65:f3:50:58; }
}

Booting the powerpc's (holding down "N" on a iBook) I only see the
iBook get a lease, but nothing about network booting.

Before I start looking elsewhere, is this a correct configuration for
doing this?  That is, by default machines will boot from the i386
filename, and the hosts defined should get the yaboot filename?



BTW - I'm not clear about setting "authoritative" on this new dhcpd server,
though.

    man dhcpd.conf

    For every subnet which will be served, and for every subnet to
    which the  dhcp  server  is *connected*,  there  must be one subnet
    declaration, which tells dhcpd how to recognize that an address is
    on that subnet.  A subnet declaration is required for each subnet
    even if no addresses will be dynamically allocated on that subnet.

*connected* is my emphasis.  From the docs it seems like this new
dhcpd server would responsd with DHCPNAK, but that's not happening.  I
assume that's because there's not subnet defined for the eth1 subnet.

Should I add an empty subnet for the eth1 network?

Should "authoritative" be config-wide, or should it be within the
subnet?

i.e.

    #empty -- another server handles this subnet
    subnet  192.168.1.0 netmask 255.255.255.0 {}

    subnet  192.168.0.0 netmask 255.255.255.0 {
        authoritative;
        ...
    }

Thanks,






-- 
Bill Moseley
moseley at hank.org