K12Linux in a multi homed environment

[Bond, Darryl]

I don't know about non-standard, this is from the upstream ltsp5 documentation:
#
# Default LTSP dhcpd.conf config file.
#

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;
#    next-server 192.168.0.1;
#    get-lease-hostnames true;
    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";
    }
}

Note that the IP address is not in the root path. I have never been able to get this to work in our environment.
I'm not sure why, except that the dhcp server is on Solaris but is the latest ISC dhcpd.

In the past I modified the initrd to make it work:

NFS_IP=` echo ${ROOTPATH} | cut -d : -f 1`
NFS_DIR=`echo ${ROOTPATH} | cut -d : -f 2`

if [ "${NFS_IP}" = "${NFS_DIR}" ]; then
    #
    # Only the root directory is specified, then we have to use the
    # default IP address.  For now, we'll use the DHCP server address
    #
    NFS_IP=${DHCPSID}
fi

The server IP address is extracted from the next-server dhcpd.conf directive. I am very keen to use the default Fedora LTSP kernel from here on so I am not interested in modifying the initrd each time it updates.
I use scripts to generate the dhcpd.conf for our environment so I certainly could put the IP address in the root path for each client. I don't know what that will do to the dhcpd when it is hosting 300+ ltsp clients.

I suppose I could break the groups up differently, at present they are broken up by LTSP version (currently 4.1, 4.2 and now 5.1). I could group them by subnet as well but it just gets even more complex.

Darryl


-----Original Message-----
From: k12linux-devel-list-bounces at redhat.com [mailto:k12linux-devel-list-bounces at redhat.com] On Behalf Of Warren Togami
Sent: Saturday, 14 February 2009 3:07 AM
To: Development discussion of K12Linux
Subject: Re: K12Linux in a multi homed environment


Bond, Darryl wrote:
>
> What is the chance of ascertaining the nfs server IP address
> separately from the root path.
>

Huh?  This sounds totally non-standard, defeating the purpose of DHCP root-path.  The only supported option is for your DHCP server to supply the desired distinct root-path to individual DHCP clients.

Warren

_______________________________________________
K12Linux-devel-list mailing list
K12Linux-devel-list at redhat.com https://www.redhat.com/mailman/listinfo/k12linux-devel-list

The contents of this electronic message and any attachments are intended only for the addressee and may contain legally privileged, personal, sensitive or confidential information. If you are not the intended addressee, and have received this email, any transmission, distribution, downloading, printing or photocopying of the contents of this message or attachments is strictly prohibited. Any legal privilege or confidentiality attached to this message and attachments is not waived, lost or destroyed by reason of delivery to any person other than intended addressee. If you have received this message and are not the intended addressee you should notify the sender by return email and destroy all copies of the message and any attachments. Unless expressly attributed, the views expressed in this email do not necessarily represent the views of the company.