> > host testltsp5 {
> > hardware ethernet 00:c0:1d:c0:ff:ee;
> > fixed-address 192.168.55.191;
> > root-path "192.168.55.66:/opt/ltsp";
> > next-server 192.168.55.66;
> > filename "/lts/ltsp5-kernel-whatever";
> Well I'm getting somewhere. My client started to boot, but reboots
> itself before I get to X. The messages go by really fast, but the last
> line I saw had the word "initrd" in it. I'll check the server logs
> tonight to see if I can get any clues. It does appear to be booting off
> of my LTSP 5.0 server, because I saw the IP address of that server flash by.
>
> -Rob
I do this with groups in dhcpd.conf so I am not positive on the settings here.
I think
you need to place the following in the hosts section instead of just the single
line
filename callout:
if substring( option vendor-class-identifier , 0 , 9 ) = "PXEClient" {
filename "/ltsp/i386/pxelinux.0";
}
else {
filename "/ltsp/i386/nbi.img";
}
option root-path "/opt/ltsp/i386";
Here is an example of how I have my dhcpd.conf configured:
authoritative;
# Cotter LAN
subnet 10.6.0.0 netmask 255.255.0.0 {
option domain-name "winonacotter.org";
option domain-name-servers 10.6.1.50;
option routers 10.6.0.1;
option subnet-mask 255.255.0.0;
pool {
allow unknown-clients;
range 10.6.253.1 10.6.253.255;
}
}
# CHS Main Lab
group {
use-host-decl-names on;
deny unknown-clients;
if substring( option vendor-class-identifier , 0 , 9 ) = "PXEClient" {
filename "/ltsp/i386/pxelinux.0";
}
else {
filename "/ltsp/i386/nbi.img";
}
option root-path "/opt/ltsp/i386";
host chsmain1 {
hardware ethernet 00:1A:4D:2F:A5:78;
fixed-address 10.6.252.1;
}
# Netbooting Macs
group {
use-host-decl-names on;
deny unknown-clients;
next-server 10.6.1.21;
host ibook1 {
hardware ethernet 00:03:93:09:61:E6;
fixed-address 10.6.252.120;
}
}
If you used this sort of setup you could put your ltsp4.2 boot info in the top
section
and call it "# LTSP 4.2" (what is "# Cotter Lan" for me). This would set all
clients
with an unknown mac address to boot ltsp 4.2. Then you could set the first
group to "#
LTSP 5" (what is "# CHS Main Lab" for me) and include all your ltsp5 boot
options
(should be the same as what I have but add the next-server directive as I have
set in
the last group). The deny unknown-clients; directive will only allow clients
specifically called out with the host option below to boot with these
parameters.
The cool thing about breaking up the booting into the configuration like I have
above is
that I am able to set all clients of which I do not have the mac address
specifically
set in a host callout to boot without any ltsp boot options. Then I have can
have
groups that boot ltsp 4.2, ltsp 5, webkiosk, boot from a mac netboot server,
etc all
from the same dhcp server. This adds ultimate control and I think a little bit
of
security since a user has to spoof the mac address of a known client in order
to network
boot, which isn't all too difficult, but less likely. Also I know that unknown
clients
will always be in a certain IP range, and all clients will have specific ip
addresses,
which gives me better control over content filtering and such.
Hope that helps
Jim
--
This message has been scanned for viruses and
dangerous content by the Cotter Technology
Department, and is believed to be clean.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_____________________________________________________________________
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.freenode.net
