[SATLUG] problems with dhcp/tftp/ltsp ofter suse 9.3 upgrage to suse 10

[gandor]

mybe i shouldnt have done this but i did it any way i
upgraded dron suse 9.3 to suse 10.
most everything went very well except i cant get LTSP
working now.

dhcpd is sending the PXE clients an ip address and the
client is exceping the address but when it gets to the tftp
i run into problems here is the log out put

Dec  2 20:18:30 linux dhcpd: DHCPDISCOVER from
00:06:5b:31:65:f6 via eth0
Dec  2 20:18:31 linux dhcpd: DHCPOFFER on 10.160.1.250 to
00:06:5b:31:65:f6 via eth0
Dec  2 20:18:32 linux dhcpd: DHCPREQUEST for 10.160.1.250
(10.160.1.5) from 00:06:5b:31:65:f6 via eth0
Dec  2 20:18:32 linux dhcpd: DHCPACK on 10.160.1.250 to
00:06:5b:31:65:f6 via eth0
Dec  3 02:18:32 linux in.tftpd[7644]: RRQ from 10.160.1.250
filename /lts/2.6.9-ltsp-3/pxelinux.0
Dec  3 02:18:32 linux in.tftpd[7644]: tftp: client does not
accept options
Dec  3 02:18:32 linux in.tftpd[7645]: RRQ from 10.160.1.250
filename /lts/2.6.9-ltsp-3/pxelinux.0
Dec  2 20:18:32 linux kernel: martian destination 0.0.0.0
from 10.160.1.250, dev eth0
Dec  2 20:18:32 linux kernel: martian destination 0.0.0.0
from 10.160.1.250, dev eth0
Dec  2 20:18:34 linux kernel: martian destination 0.0.0.0
from 10.160.1.250, dev eth0
Dec  2 20:18:36 linux kernel: martian destination 0.0.0.0
from 10.160.1.250, dev eth0
Dec  2 20:18:42 linux kernel: martian destination 0.0.0.0
from 10.160.1.250, dev eth0
Dec  2 20:18:52 linux kernel: martian destination 0.0.0.0
from 10.160.1.250, dev eth0


not thats not the really weard part athought to wont boot
the PXE client the part that really gets me is when i try to
boot an etherboot client.
dhcp sees the client and sends a DHCPOFFER but the client
never gets the ip


Dec  2 20:23:58 linux dhcpd: DHCPDISCOVER from
00:04:e2:1c:86:0b via eth0
Dec  2 20:23:58 linux dhcpd: DHCPOFFER on 10.160.1.6 to
00:04:e2:1c:86:0b via eth0
Dec  2 20:24:32 linux dhcpd: DHCPDISCOVER from
00:04:e2:1c:86:0b via eth0
Dec  2 20:24:32 linux dhcpd: DHCPOFFER on 10.160.1.6 to
00:04:e2:1c:86:0b via eth0
Dec  2 20:24:34 linux dhcpd: DHCPDISCOVER from
00:04:e2:1c:86:0b via eth0
Dec  2 20:24:34 linux dhcpd: DHCPOFFER on 10.160.1.6 to
00:04:e2:1c:86:0b via eth0
Dec  2 20:24:38 linux dhcpd: DHCPDISCOVER from
00:04:e2:1c:86:0b via eth0
Dec  2 20:24:38 linux dhcpd: DHCPOFFER on 10.160.1.6 to
00:04:e2:1c:86:0b via eth0
Dec  2 20:24:47 linux dhcpd: DHCPDISCOVER from
00:04:e2:1c:86:0b via eth0
Dec  2 20:24:47 linux dhcpd: DHCPOFFER on 10.160.1.6 to
00:04:e2:1c:86:0b via eth0

does anyone know where the problem could be?