Help: SuSE 9.3 Pro; ltsp-4.1.1-1; tftp problem

Aiming to use an old Pentium-100 machine as an X-terminal booted from my
main workstation via "Etherboot" for 3c509, I installed ltsp-4.1.1-1 under
SuSE 9.3 Pro. DHCP issues the required IP address OK and the client
requests the kernel file (</tftpboot>/lts/vmlinuz-2.4.26-ltsp-3, tftpd is
chrooted to /tftpboot). So far so good ... but then - nothing happens.

Investigation using "Ethereal" shows that immediately following receipt of
the tftp RRQ, the server reports an ICMP destination port unreachable.
After timeout,the client then increments the port number and issues a
further RRQ, which is immediately followed by an ICMP destination port
unreachable again. This continues with longer delays each time.

The network was stripped down to just the two machines and retested, but the
behaviour remains as described. The firewall on the SuSE machine is
inactive.

Here is an extract from the (textualised) Etherreal log:

> --------------------- Log ----------------------- <

No. Time Source Destination Protocol
Info
29 104.040458 0.0.0.0 255.255.255.255 DHCP
DHCP Discover - Transaction ID 0xaf3593f4

Frame 29 (590 bytes on wire, 590 bytes captured)
Ethernet II, Src: wronski.at.home.net (00:20:af:27:16:f7), Dst: Broadcast
(ff:ff:ff:ff:ff:ff)
Internet Protocol, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255
(255.255.255.255)
User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67)
Bootstrap Protocol

No. Time Source Destination Protocol
Info
30 104.041136 10.10.10.9 255.255.255.255 DHCP
DHCP Offer - Transaction ID 0xaf3593f4

Frame 30 (342 bytes on wire, 342 bytes captured)
Ethernet II, Src: jacobi.at.home.net (00:02:a5:82:5f:8f), Dst: Broadcast
(ff:ff:ff:ff:ff:ff)
Internet Protocol, Src: 10.10.10.9 (10.10.10.9), Dst: 255.255.255.255
(255.255.255.255)
User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68)
Bootstrap Protocol

No. Time Source Destination Protocol
Info
31 106.840039 10.10.10.23 255.255.255.255 DHCP
DHCP Request - Transaction ID 0xaf3593f4

Frame 31 (590 bytes on wire, 590 bytes captured)
Ethernet II, Src: wronski.at.home.net (00:20:af:27:16:f7), Dst: Broadcast
(ff:ff:ff:ff:ff:ff)
Internet Protocol, Src: 10.10.10.23 (10.10.10.23), Dst: 255.255.255.255
(255.255.255.255)
User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67)
Bootstrap Protocol

No. Time Source Destination Protocol
Info
32 106.840742 10.10.10.9 255.255.255.255 DHCP
DHCP ACK - Transaction ID 0xaf3593f4

Frame 32 (346 bytes on wire, 346 bytes captured)
Ethernet II, Src: jacobi.at.home.net (00:02:a5:82:5f:8f), Dst: Broadcast
(ff:ff:ff:ff:ff:ff)
Internet Protocol, Src: 10.10.10.9 (10.10.10.9), Dst: 255.255.255.255
(255.255.255.255)
User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68)
Bootstrap Protocol

No. Time Source Destination Protocol
Info
33 106.847954 wronski.at.home.net Broadcast ARP Who
has 10.10.10.9? Tell 10.10.10.23

Frame 33 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: wronski.at.home.net (00:20:af:27:16:f7), Dst: Broadcast
(ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)

No. Time Source Destination Protocol
Info
34 106.847999 jacobi.at.home.net wronski.at.home.net ARP
10.10.10.9 is at 00:02:a5:82:5f:8f

Frame 34 (42 bytes on wire, 42 bytes captured)
Ethernet II, Src: jacobi.at.home.net (00:02:a5:82:5f:8f), Dst:
wronski.at.home.net (00:20:af:27:16:f7)
Address Resolution Protocol (reply)

No. Time Source Destination Protocol
Info
35 106.848253 10.10.10.23 10.10.10.9 TFTP
Read Request, File: /lts/vmlinuz-2.4.26-ltsp-3, Transf
er type: octet

Frame 35 (90 bytes on wire, 90 bytes captured)
Ethernet II, Src: wronski.at.home.net (00:20:af:27:16:f7), Dst:
jacobi.at.home.net (00:02:a5:82:5f:8f)
Internet Protocol, Src: 10.10.10.23 (10.10.10.23), Dst: 10.10.10.9
(10.10.10.9)
User Datagram Protocol, Src Port: wizard (2001), Dst Port: tftp (69)
Trivial File Transfer Protocol

No. Time Source Destination Protocol
Info
36 106.848306 10.10.10.9 10.10.10.23 ICMP
Destination unreachable (Port unreachable)

Frame 36 (118 bytes on wire, 118 bytes captured)
Ethernet II, Src: jacobi.at.home.net (00:02:a5:82:5f:8f), Dst:
wronski.at.home.net (00:20:af:27:16:f7)
Internet Protocol, Src: 10.10.10.9 (10.10.10.9), Dst: 10.10.10.23
(10.10.10.23)
Internet Control Message Protocol

No. Time Source Destination Protocol
Info
37 111.846773 jacobi.at.home.net wronski.at.home.net ARP Who
has 10.10.10.23? Tell 10.10.10.9

Frame 37 (42 bytes on wire, 42 bytes captured)
Ethernet II, Src: jacobi.at.home.net (00:02:a5:82:5f:8f), Dst:
wronski.at.home.net (00:20:af:27:16:f7)
Address Resolution Protocol (request)

No. Time Source Destination Protocol
Info
38 111.847126 wronski.at.home.net jacobi.at.home.net ARP
10.10.10.23 is at 00:20:af:27:16:f7

Frame 38 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: wronski.at.home.net (00:20:af:27:16:f7), Dst:
jacobi.at.home.net (00:02:a5:82:5f:8f)
Address Resolution Protocol (reply)

No. Time Source Destination Protocol
Info
39 117.385089 10.10.10.23 10.10.10.9 TFTP
Read Request, File: /lts/vmlinuz-2.4.26-ltsp-3, Transf
er type: octet

Frame 39 (90 bytes on wire, 90 bytes captured)
Ethernet II, Src: wronski.at.home.net (00:20:af:27:16:f7), Dst:
jacobi.at.home.net (00:02:a5:82:5f:8f)
Internet Protocol, Src: 10.10.10.23 (10.10.10.23), Dst: 10.10.10.9
(10.10.10.9)
User Datagram Protocol, Src Port: globe (2002), Dst Port: tftp (69)
Trivial File Transfer Protocol

No. Time Source Destination Protocol
Info
40 117.385148 10.10.10.9 10.10.10.23 ICMP
Destination unreachable (Port unreachable)

Frame 40 (118 bytes on wire, 118 bytes captured)
Ethernet II, Src: jacobi.at.home.net (00:02:a5:82:5f:8f), Dst:
wronski.at.home.net (00:20:af:27:16:f7)
Internet Protocol, Src: 10.10.10.9 (10.10.10.9), Dst: 10.10.10.23
(10.10.10.23)
Internet Control Message Protocol

.... etc

> ------------------------ End Extract --------------------- <

Can anyone tell me what is happening at frame 36 and frame 40 ... etc?

The SuSE interface (eth0) is configured with mtu 1500.

Thanks - Barclay Weir

Barclay,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at
http://support.novell.com.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://support.novell.com/forums)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://support.novell.com/forums/