[EMAIL PROTECTED] wrote:
> my problem is thaht i receive the No IP Address error on the client's
> screens, but the solution i found on the FAQ (next-server entry in the
> dhcp conf file) doesn't work...
> my firewall is off
> i use LTSP 5 with Etherboot 5.4.2 with zhd files (that i wrote to disk using
> tomsrtbt, "The most GNU/Linux on one floppy disk").
>
> syslog file doesn't log any error from client:
> ----------------------------
> Sep 13 11:43:23 continuity dhcpd: DHCPDISCOVER from 00:50:ba:bf:66:29
> via eth2
> Sep 13 11:43:28 continuity dhcpd: DHCPOFFER on 192.168.11.106 to
> 00:50:ba:bf:66:29 via eth2
> Sep 13 11:43:49 continuity dhcpd: DHCPDISCOVER from 00:50:ba:bf:66:29
> via eth2
> Sep 13 11:43:54 continuity dhcpd: DHCPOFFER on 192.168.11.106 to
> 00:50:ba:bf:66:29 via eth2
> ----------------------------
> and so on...
> the same is for /var/log/messages file
>
>
> my dhcp.conf file assigns MAC based IPs:
> ---------------------------------------------------------
> option domain-name "linuxlab";
> #option domain-name-servers 192.168.11.254;
> option routers 192.168.11.254;
> option root-path "/opt/ltsp/i386";
> option option-128 code 128 = string;
> option option-129 code 129 = text;
> option broadcast-address 192.168.11.255;
> #get-lease-hostnames true;
> option subnet-mask 255.255.255.0;
> default-lease-time 604800;
> next-server 192.168.11.254;
>
> option option-129 "acpi=force";
>
> subnet 192.168.11.0 netmask 255.255.255.0 {
> range 192.168.11.1 192.168.11.99;
> next-server 192.168.11.254;
>
> if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
> filename "/ltsp/i386/pxelinux.0";
> next-server 192.168.11.254;
> } else {
>
> next-server 192.168.11.254;
> }
> }
>
> host studente1 {
> hardware ethernet 00:1d:0f:ff:d1:07;
> fixed-address 192.168.11.101;
> }
>
> host studente2 {
> hardware ethernet 00:1d:0f:ff:db:03;
> fixed-address 192.168.11.102;
> }
>
> host studente3 {
> hardware ethernet 00:1d:0f:ff:db:08;
> fixed-address 192.168.11.103;
> }
>
> host studente4 {
> hardware ethernet 00:50:ba:bf:66:20;
> fixed-address 192.168.11.104;
> }
>
> host studente5 {
> hardware ethernet 00:80:c8:e6:92:cc;
> fixed-address 192.168.11.105;
> }
>
> host studente6 {
> hardware ethernet 00:c0:26:ed:4d:58;
> fixed-address 192.168.11.106;
> }
> ---------------------------------------------------------
>
Do you realize that you're not handing out kernels to the
statically-assigned IP addresses? If they are thin clients, you'll need
to specify a kernel for them each individually, or as part of a group.
You can do this:
group MyStaticThinclients-PXE {
filename "/ltsp/i386/pxelinux.0";
host studente1 {
hardware ethernet 00:1d:0f:ff:d1:07;
fixed-address 192.168.11.101;
}
host studente2 {
hardware ethernet 00:1d:0f:ff:db:03;
fixed-address 192.168.11.102;
}
}
You can do the same for group MyStaticThinclients-Etherboot, but specify
filename "/ltsp/i386/nbi.img";
You might also be able to use the "if, then" logic that is used in your
dynamic range, in order to combine all of your etherboot and pxe static
workstations into one group.
I believe the PXE and etherboot processes hit your DHCP server twice.
Once to get their IP address, and once to get "further instructions". I
wonder if you're actually getting hung up on the 2nd request due to the
fact that you haven't specified a kernel in your static stanzas.
I also noticed your root-path statement doesn't contain in IP address.
I'm not sure if it's required or not, but mine has one. It looks like this:
option root-path "10.112.0.254:/opt/ltsp/i386";
(in your case, change it to the IP address of your server).
-Rob
********************************************************
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. If you are not the addressee, any disclosure, reproduction,
copying, distribution, or other dissemination or use of this transmission in
error please notify the sender immediately and then delete this e-mail.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted lost, destroyed, arrive late or
incomplete, or contain viruses.
The sender therefore does not accept liability for any errors or omissions
in the contents of this message which arise as a result of e-mail
transmission. If verification is required please request a hard copy
version.
********************************************************
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_____________________________________________________________________
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
