Am Freitag, den 24.03.2006, 00:48 -0700 schrieb Dormition Skete:
> I have a very perplexing problem with dhcp. I had to rebuild my server due
> to a hard disk failure, and I decided to try SuSE 10.0 for a change. I have
> installed LTSP several times on Redhat and Slackware without any significant
> problems.
>
> With SuSE 10.0, however, my dhcpd daemon receives the request, and offers
> the correct IP Address response for the workstation. The workstation never
> gets it, though. It just hangs on "Searching for server (DHCP)...". A
> second LTSP workstation does the same thing, but it gives a message saying
> "No IP address".
>
> Now for the really perplexing part. I gave up on SuSE because I didn't want
> to fight with this, or bother any of you with it. But now that I've put
> Fedora 5 on it, it does the exact same thing! I just had Red Hat Enterprise
> Linux 4 on it, and it worked fine, so something must have changed since it
> came out, that both FC5 and SuSE 10 now have.
>
> I have the firewall turned off, so it should not be getting in the way. The
> "# iptables -L -v" command gives a response like what the LTSP
> troubleshooting section says means that it is not getting in the way.
>
> Does anyone have any idea what could be going wrong, and how I can get this
> to work?
You seem to be missing the "next-server" statement in dhcpd.conf.
Technical explanation:
In between two dhcp daemon releases (3.0.2 and 3.0.3) the ISC people
decided to change default values. Older dhcpd versions would, if not
specifically configured to do else, send a "next-server" field with the
IP of the DHCP server. This field defaults to be empty now.
Of course, Etherboot cannot work correctly if there is no information
which server the boot files shall be fetched from, so DHCP offers
without the next-server information are discarded.
Fix:
Add a line
next-server 192.168.0.2;
with the ip address of your tftp server (probably the same machine as
dhcpd server, isn't it?)
> I would *greatly* appreciate some help here.
>
> Below is my dhcpd.conf file, which has previously worked fine for the past
> three years, I think.
>
>
> # Sample configuration file for ISCD dhcpd
> #
> # Make changes to this file and copy it to /etc/dhcpd.conf
> #
> ddns-update-style none;
>
> default-lease-time 21600;
> max-lease-time 21600;
>
> option subnet-mask 255.255.255.0;
> option broadcast-address 192.168.0.255;
> option routers 192.168.0.2;
> option domain-name-servers 192.168.0.2;
> option domain-name "ds";
> option root-path "192.168.0.2:/opt/ltsp/i386";
****** somewhere like here.
>
> option option-128 code 128 = string;
> option option-129 code 129 = text;
>
> log-facility local7;
>
> shared-network WORKSTATIONS {
> subnet 192.168.0.0 netmask 255.255.255.0 {
> range 192.168.0.100 192.168.0.254;
> }
> }
>
> group {
> use-host-decl-names on;
> option log-servers 192.168.0.2;
>
> host ws101 {
> # Sony
> hardware ethernet 00:04:5a:7e:75:10;
> fixed-address 192.168.0.101;
> filename "/lts/vmlinuz-2.6.9-ltsp-3";
> ## option option-128 e4:45:74:68:00:00; #This is NOT a MAC
> address
> ## option option-129 "NIC=ne IO=0x300";
HTH
Anselm
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_____________________________________________________________________
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
