Uwe Thiem wrote:
Right. Somewhat besides your question: Are you really using hubs? I also seem
to remember from your original post that the terminals are connected by
10Mb/s which makes sense if you are using hubs. From my experience with
server / thin client configurations, I would suggest to replace the hubs by
switches and use 100Mb/s full duplex connections. That should boost the
performance of your terminals by far. Anyway, this has nothing to do with
your current problem.
We originally used hubs and later moved to switches - my mistake. But
it hasn't made much difference in performance. Our performance bottleneck
is elsewhere. But that's another discussion.
Please post your ifconfig output on the server and also the routing table.
--> ifconfig
eth0 Link encap:Ethernet HWaddr 00:02:A5:ED:2B:AD
inet addr:10.88.1.5 Bcast:10.88.1.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:382228 errors:0 dropped:0 overruns:0 frame:0
TX packets:33183 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:40956294 (39.0 Mb) TX bytes:9529879 (9.0 Mb)
--> route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
10.88.0.0 * 255.255.0.0 U 0 0 0 eth0
default ws510.ltsp 0.0.0.0 UG 0 0 0 eth0
Are you sure your server sees the dhcp requests at all?
Yes. The system logs are full of requests. The ltsp server is also a
dhcp server
for the entire campus, and all of the non-ltsp-terminal boxes are
functioning
properly on the network.
Run tcpdump on the
appropriate interface on the server and boot just one terminal. Does the
request come through?
Can't do that right now - don't have physical access to the machines on
the weekend
and can't boot a terminal now.
Is dhcpd listening on the right interface? You mentioned a power outage. So
some configuration could be messed up.
There's only one interface, eth0. Here's the command that started dhcpd
- looks like it
should be listening to eth0.
--> ps aux | grep dhcp
dhcp 9009 0.0 0.0 2680 1656 ? Ss May04 0:01
/usr/sbin/dhcpd -q -pf /var/run/dhcp/dhcpd.pid -user dhcp -group dhcp -q
eth0
A power outage can also be accompanied by some power surges. That could fry
the ethernet card in your server. Can you connect to it with a fat client?
With dhcp? With a static IP configuration?
It's not fried. I can ssh from a remote location into the server, and
the server has only one
ethernet card in it.
So, the hardware is working, and dhcpd is filling the system logs with
stuff like
May 6 14:55:29 [dhcpd] DHCPDISCOVER from 00:a0:24:98:14:55 via eth0
May 6 14:55:30 [dhcpd] DHCPOFFER on 10.88.3.122 to 00:a0:24:98:14:55
via eth0
which means that dhcpd is running, listening on eth0 and talking to ltsp
terminals.
But, judging from the ltsp-terminal error messages I posted originally,
the terminals
don't seem to think that they've made a satisfactory contact with dhcpd
on the server.
John Blinka
--
gentoo-user@gentoo.org mailing list
