Okay, this is weird...
I just moved the DHCP server from one box to another (the old one lags
on DHCP requests badly when under load, and so a lot of the thin clients
time out waiting for an address). The only difference between the two
is the first was not running a firewall -- all incoming and outgoing
connections allowed, and the second one is -- setup mostly for to block
OUTGOING ports, since its the LTSP server as well, dont really care
about incoming.
The interesting thing is this. I have incoming port 69 (UDP) opened on
the server, and running the TFTP daemon, but the *client* is just
randomly picking a port (it looks like) and then trying to get a
connection that way. So, the thin client boots up, gets a DHCP address
just fine, but times out on TFTP because the client is not listening on
those ports.
Here's what the syslog looks like on the server:
Dec 5 13:47:19 localhost kernel: Outbound IN= OUT=eth0
SRC=192.168.1.198 DST=192.168.1.253 LEN=42 TOS=0x00 PREC=0x00 TTL=64
ID=43275 DF PROTO=UDP SPT=32856 DPT=2070 LEN=22
Dec 5 13:47:27 localhost kernel: Outbound IN= OUT=eth0
SRC=192.168.1.198 DST=192.168.1.253 LEN=42 TOS=0x00 PREC=0x00 TTL=64
ID=51156 DF PROTO=UDP SPT=32856 DPT=2071 LEN=22
Dec 5 13:47:43 localhost kernel: Outbound IN= OUT=eth0
SRC=192.168.1.198 DST=192.168.1.253 LEN=42 TOS=0x00 PREC=0x00 TTL=64
ID=1442 DF PROTO=UDP SPT=32856 DPT=2072 LEN=22
Dec 5 13:48:06 localhost kernel: Outbound IN= OUT=eth0
SRC=192.168.1.198 DST=192.168.1.253 LEN=42 TOS=0x00 PREC=0x00 TTL=64
ID=25175 DF PROTO=UDP SPT=32856 DPT=2073 LEN=22
Dec 5 13:48:38 localhost kernel: Outbound IN= OUT=eth0
SRC=192.168.1.198 DST=192.168.1.253 LEN=42 TOS=0x00 PREC=0x00 TTL=64
ID=56819 DF PROTO=UDP SPT=32856 DPT=2074 LEN=22
Dec 5 13:49:17 localhost kernel: Outbound IN= OUT=eth0
SRC=192.168.1.198 DST=192.168.1.253 LEN=43 TOS=0x00 PREC=0x00 TTL=64
ID=30844 DF PROTO=UDP SPT=32856 DPT=2075 LEN=23
Dec 5 13:49:25 localhost kernel: Outbound IN= OUT=eth0
SRC=192.168.1.198 DST=192.168.1.253 LEN=43 TOS=0x00 PREC=0x00 TTL=64
ID=38749 DF PROTO=UDP SPT=32856 DPT=2076 LEN=23
Dec 5 13:49:41 localhost kernel: Outbound IN= OUT=eth0
SRC=192.168.1.198 DST=192.168.1.253 LEN=43 TOS=0x00 PREC=0x00 TTL=64
ID=54571 DF PROTO=UDP SPT=32856 DPT=2077 LEN=23
Actually, now that I look a little closer -- maybe its not random at
all. I can see another instance earlier in the log where it's also
doing the same thing: starting on port 2070, going up to port 2079 and
then times out. I guess I can just open up those ports too, but why is
it trying on those? And at the same time, are there other TFTP ports
that I should have open that I dont know about?
Steve
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_____________________________________________________________________
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
