...
>
> Now would my DHCPD.CONF on the firewall shouldbe looking like the following
> ?
>
>
> #------------------------------------------------------------
> subnet 192.168.1.0 netmask 255.255.255.0
> {
> option broadcast-address 192.168.1.255;
> deny bootp;
> option domain-name "digl.dnsalias.com";
> option domain-name-servers 192.168.1.1;
> default-lease-time 86400;
> max-lease-time 604800;
> option netbios-dd-server 192.168.1.1;
> option netbios-name-servers 192.168.1.1;
> option netbios-node-type 8;
> option subnet-mask 255.255.255.0;
> range 192.168.1.65 192.168.1.250;
> option routers 192.168.1.1;
> }
> host icue5 {
> hardware ethernet 00:d0:09:27:67:55; <---- Who's MAC address is
> this? LTSP server or workstation??
> fixed-address 10.171.13.5; <---- Who's IP address is this? LTSP
> server or workstation??
> allow bootp;
> server-name "pc65.digl.dnsalias.com"; <<------ LTSP MAchine?
> next-server 192.168.1.65; <<------
> LTSP MAchine?
> filename "/tftpboot/lts/vmlinuz-2.4.9-ltsp";
> }
>
>
The only difference between running the dhcp server on the LTSP server vs running it
on a separate server is the 'next-server' option. Without that option, dhcp assumes to
tftp boot from the dhcp server.
You are on the right track here...but this may not yield the desired results. Since
your option settings are all in your subnet declaration, your workstation (icue5)
won't know anything about them. Try using the dhcpd.conf example supplied with ltsp or
try this link and modify the example as required.
http://sourceforge.net/mailarchive/message.php?msg_id=1468998
Everything between the 'host icue5 {' and the next '}' applies to the workstation
settings. So, the hardware ethernet is the workstation's mac address, the fixed
address is the workstation's address, and the next-server is the LTSP server that you
want the workstation to get the tftp boot from.
Oh yes, and make sure that your workstation fixed IP is not within the range of your
subnet declaration...you don't want those overlapping.
You might want to make a copy of your existing dhcpd.conf file and then hack away.
Remember that you need to restart the dhcp daemon after changes to the conf file.
If you still run into problems, then re-send a current version of your dhcpd.conf file
and we can try to help further.
cheers,
rob
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Caffeinated soap. No kidding.
http://thinkgeek.com/sf
_____________________________________________________________________
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
