Hi everybody!  I have a thin-client-booting-brainteaser for you all:

Tue Hellstern is having a problem booting a Jammin 125 thin client.  It
has a Realtek 8139 NIC, and gets stuck at the point where it should be
TFTPing the kernel from the server.  ("Loading
192.168.0.4:/lts/vmlinuz-2.4.19-ltsp-1...")

He very graciously let me have a poke at his server to help him find the
cause.  Running "tail /var/log/messages" showed me that DHCP was
working, but TFTP never even got started.  (xinetd is running "in.tftpd
-v -v -s /tftpboot".)  So as a matter of troubleshooting, I ran
"tethereal &> capture", and this is what I saw:

---cut-->
 37.418674      0.0.0.0 -> 255.255.255.255 DHCP DHCP Discover -
Transaction ID 0x410e2793
 37.419571  192.168.0.4 -> 192.168.0.150 DHCP DHCP Offer    -
Transaction ID 0x410e2793
 37.419969 192.168.0.150 -> 255.255.255.255 DHCP DHCP Request  -
Transaction ID 0x410e2793
 37.420233  192.168.0.4 -> 192.168.0.150 DHCP DHCP ACK      -
Transaction ID 0x410e2793
 37.426012 Ctx_Opto_01:83:ab -> Broadcast    ARP Who has 192.168.0.4?
Tell 192.168.0.150
 37.426028 Hewlett__37:24:77 -> Ctx_Opto_01:83:ab ARP 192.168.0.4 is at
00:30:6e:37:24:77
 37.426095 192.168.0.150 -> 192.168.0.4  TFTP Read Request, File:
/lts/vmlinuz-2.4.19-ltsp-1, Transfer type: octet
 37.426119  192.168.0.4 -> 192.168.0.150 ICMP Destination unreachable
<--cut---

So, the address 192.168.0.150 gets assigned to the client, but when the
client tries to request the file, the server responds that... it is
unreachable?

netstat shows me that xinetd is listening on UDP port 69.  Here is
dhcpd.conf:

---cut-->
ddns-update-style interim;
subnet 192.168.0.0 netmask 255.255.255.0 {
        range dynamic-bootp 192.168.0.200 192.168.0.250;
        option routers 192.168.0.1;
        option root-path "192.168.0.4:/opt/ltsp/i386";
        option domain-name "f1-support.dk";
        option domain-name-servers 192.168.0.1;
        default-lease-time 36000;
        max-lease-time 86400;
        allow unknown-clients;
        group {
          use-host-decl-names       on;
          option log-servers        192.168.1.4;
          host ws001 {
            hardware ethernet     00:50:41:01:83:AB;
            fixed-address         192.168.0.150;
            filename              "/lts/vmlinuz-2.4.19-ltsp-1";
          }
        }
}
<--cut---

Any ideas?  This is an amazing hair-puller of a problem so far :-)

Thanks much,
- Jake



-- 


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.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

Reply via email to