...
>Mounting root filesystem: /opt/ltsp/i386 from: 10.66.3.12 (the correct
>IP of the server)
>(null)mount: nfsmount failed: Bad file number
>NFS: mount program didn't pass remote address!
>mount: Mounting 10.66.3.12:/opt/ltsp/i386 on /mnt failed: Invalid
>argument
...
This tells me that for some reason, the workstation is not being passed the filename
by the dhcp server...only the root path. see below
...
> Here are all the appropriate files I can think of, let me know if you
> need to see another one:
>
> /etc/dhcpd.conf:
>
> default-lease-time 21600;
> max-lease-time 21600;
>
> option subnet-mask 255.255.255.0;
>
> subnet 10.0.0.0 netmask 255.0.0.0
> {
> not authoritative;
> }
>
> shared-network WORKSTATIONS
> {
> option routers 10.10.10.10;
> option domain-name-servers 10.10.10.1;
> option root-path "10.66.3.12:/opt/ltsp/i386";
>
> subnet 10.66.6.24 netmask 255.255.255.248
> {
> option broadcast-address 10.66.6.255;
> }
>
> subnet 10.66.6.32 netmask 255.255.255.248
> {
> option broadcast-address 10.66.6.255;
> }
> }
>
> group
> {
> use-host-decl-names on;
> option log-servers 10.66.3.12;
>
> host ws001
> {
> hardware ethernet 00:A0:24:1D:DD:2D;
> fixed-address 10.66.6.24;
> filename
> "/tftpboot/lts/vmlinuz-2.4.9-ltsp-5";
> option option-128 e4:45:74:68:00:00;
> option option-129 "NIC=3c509 IO=0x210";
> }
> }
>
>
> This brings up my DHCP issue, the above config warns me about the
> obvious conflict between the 10.0.0.0/255.0.0.0 and
> 10.66.6.24/255.255.255.248 subnets, but it seems to work and do what I
> want DHCP wise (only respond to DHCPREQUEST's for the IP's in the range
> I've been granted control over).
...
I am suspicious of your 'subnet 10.66.6.24 netmask 255.255.255.248' and 'subnet
10.66.6.24 netmask 255.255.255.248' and 'subnet 10.0.0.0 netmask 255.0.0.0'. I think
that these are why your server is not passing the filename to the workstation. Why are
there three? And, should not the subnet be something like '10.66.6.0' (from your
exports file)? Also, if I am not mistaken, you should not need a shared-network
section at all if you are only serving ltsp clients. You could try removing all of the
shared-network sections from dhcpd.conf. Also, move all of your options which would be
global to all workstations out of any blocks (this saves time and hassle when adding
workstations).
The option 128 and 129 won't work without being defined before use.
One other thing, if you are using redhat or mandrake, you have to specifiy the
filename as "/lts/vmlinuz-2.4.9-ltsp-5" - note without the preceeding /tftpboot.
So, your ending dhcp.conf file might look something like:
default-lease-time 21600;
max-lease-time 21600;
option subnet-mask 255.255.255.0;
option routers 10.10.10.10;
option domain-name-servers 10.10.10.1;
option root-path "10.66.3.12:/opt/ltsp/i386";
option option-128 code 128 = string;
option option-129 code 129 = text;
group
{
use-host-decl-names on;
option log-servers 10.66.3.12;
host ws001
{
hardware ethernet 00:A0:24:1D:DD:2D;
fixed-address 10.66.6.24;
filename "/lts/vmlinuz-2.4.9-ltsp-5";
option option-128 e4:45:74:68:00:00;
option option-129 "NIC=3c509 IO=0x210";
}
}
good luck,
rob
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.openprojects.net
