On Friday 14 December 2007 09:09:46 Fajar Priyanto wrote: > Hi Poul, > So your tftp problem is related to firewall? > I'm still facing it. I can work around it by using a diskboot, but still to > be able to boot from pxe is prefered. > > My case is: > An RTL8139 on board NIC with PXE v.2.1 failed with TFTP timeout. > An RTL8139 on board NIX with PXE v.2.0 succeed booting LTSP5 with Ubuntu > Gutsy.
So, out of curiousity, I install wireshark on the LTSP server and I find
interesting details:
1. The failed client looks for the tftp server at 192.168.0.254 (my gateway),
whereas it should be 192.168.0.237.
So, I change all instances of 192.168.0.254 to 192.168.0.237 in my dhcpd.conf,
and the client now looks for the tftp server in 192.168.0.237. Aha..!
2. But, then, eventhough now the client correctly find the tftp server, but
when asking for the pxeclient.0 file, it stucks. Don't know for sure the
reason.
This is the result of wireshark capture:
The successful client (192.168.0.101):
=============
No. Time Source Destination Protocol Info
72 351.374720 0.0.0.0 255.255.255.255 DHCP DHCP
Request - Transaction ID 0x6716237e
No. Time Source Destination Protocol Info
73 351.375211 127.0.1.1 255.255.255.255 DHCP DHCP
ACK - Transaction ID 0x6716237e
No. Time Source Destination Protocol Info
74 351.377043 Asiarock_16:23:7e Broadcast ARP Who
has 192.168.0.237? Tell 192.168.0.101
====== It will then ask for the tftp server (192.68.0.237):
No. Time Source Destination Protocol Info
74 351.377043 Asiarock_16:23:7e Broadcast ARP Who
has 192.168.0.237? Tell 192.168.0.101
Frame 74 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: Asiarock_16:23:7e (00:19:66:16:23:7e), Dst: Broadcast
(ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)
No. Time Source Destination Protocol Info
75 351.377067 QuantaCo_28:15:65 Asiarock_16:23:7e ARP
192.168.0.237 is at 00:c0:9f:28:15:65
Frame 75 (42 bytes on wire, 42 bytes captured)
Ethernet II, Src: QuantaCo_28:15:65 (00:c0:9f:28:15:65), Dst:
Asiarock_16:23:7e (00:19:66:16:23:7e)
Address Resolution Protocol (reply)
======= It will then start asking for the pxelinux.0 file to boot:
No. Time Source Destination Protocol Info
76 351.377199 192.168.0.101 192.168.0.237 TFTP Read
Request, File: /ltsp/i386/pxelinux.0, Transfer type: octet, tsize=0
Frame 76 (80 bytes on wire, 80 bytes captured)
Ethernet II, Src: Asiarock_16:23:7e (00:19:66:16:23:7e), Dst:
QuantaCo_28:15:65 (00:c0:9f:28:15:65)
Internet Protocol, Src: 192.168.0.101 (192.168.0.101), Dst: 192.168.0.237
(192.168.0.237)
User Datagram Protocol, Src Port: 2070 (2070), Dst Port: tftp (69)
Trivial File Transfer Protocol
No. Time Source Destination Protocol Info
77 351.446605 192.168.0.237 192.168.0.101 TFTP
Option Acknowledgement, tsize=13552
No. Time Source Destination Protocol Info
79 351.447316 192.168.0.101 192.168.0.237 TFTP Read
Request, File: /ltsp/i386/pxelinux.0, Transfer type: octet, blksize=1456
Frame 79 (85 bytes on wire, 85 bytes captured)
Ethernet II, Src: Asiarock_16:23:7e (00:19:66:16:23:7e), Dst:
QuantaCo_28:15:65 (00:c0:9f:28:15:65)
Internet Protocol, Src: 192.168.0.101 (192.168.0.101), Dst: 192.168.0.237
(192.168.0.237)
User Datagram Protocol, Src Port: 2071 (2071), Dst Port: tftp (69)
Trivial File Transfer Protocol
====================
The failed client (192.168.0.101):
No. Time Source Destination Protocol Info
37292 1887.159772 127.0.1.1 255.255.255.255 DHCP DHCP
ACK - Transaction ID 0xd4c63595
No. Time Source Destination Protocol Info
37293 1887.160263 Micro-St_c6:35:95 Broadcast ARP Who
has 192.168.0.237? Tell 192.168.0.100
Frame 37293 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: Micro-St_c6:35:95 (00:13:d3:c6:35:95), Dst: Broadcast
(ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)
No. Time Source Destination Protocol Info
37294 1887.160290 QuantaCo_28:15:65 Micro-St_c6:35:95 ARP
192.168.0.237 is at 00:c0:9f:28:15:65
Frame 37294 (42 bytes on wire, 42 bytes captured)
Ethernet II, Src: QuantaCo_28:15:65 (00:c0:9f:28:15:65), Dst:
Micro-St_c6:35:95 (00:13:d3:c6:35:95)
Address Resolution Protocol (reply)
No. Time Source Destination Protocol Info
37295 1887.160359 192.168.0.100 127.0.1.1 TFTP Read
Request, File: /ltsp/i386/pxelinux.0, Transfer type: octet, tsize=0
Frame 37295 (80 bytes on wire, 80 bytes captured)
Ethernet II, Src: Micro-St_c6:35:95 (00:13:d3:c6:35:95), Dst:
QuantaCo_28:15:65 (00:c0:9f:28:15:65)
Internet Protocol, Src: 192.168.0.100 (192.168.0.100), Dst: 127.0.1.1
(127.0.1.1)
User Datagram Protocol, Src Port: 2070 (2070), Dst Port: tftp (69)
Trivial File Transfer Protocol
=========== it then tries to get the files several times, and then time out:
No. Time Source Destination Protocol Info
37302 1899.174159 192.168.0.100 127.0.1.1 TFTP Read
Request, File: /ltsp/i386/pxelinux.0, Transfer type: octet, tsize=0
Frame 37302 (80 bytes on wire, 80 bytes captured)
Ethernet II, Src: Micro-St_c6:35:95 (00:13:d3:c6:35:95), Dst:
QuantaCo_28:15:65 (00:c0:9f:28:15:65)
Internet Protocol, Src: 192.168.0.100 (192.168.0.100), Dst: 127.0.1.1
(127.0.1.1)
User Datagram Protocol, Src Port: 2073 (2073), Dst Port: tftp (69)
Trivial File Transfer Protocol
No. Time Source Destination Protocol Info
37303 1907.137649 192.168.0.100 127.0.1.1 TFTP Read
Request, File: /ltsp/i386/pxelinux.0, Transfer type: octet, tsize=0
Frame 37303 (80 bytes on wire, 80 bytes captured)
Ethernet II, Src: Micro-St_c6:35:95 (00:13:d3:c6:35:95), Dst:
QuantaCo_28:15:65 (00:c0:9f:28:15:65)
Internet Protocol, Src: 192.168.0.100 (192.168.0.100), Dst: 127.0.1.1
(127.0.1.1)
User Datagram Protocol, Src Port: 2074 (2074), Dst Port: tftp (69)
Trivial File Transfer Protocol
No. Time Source Destination Protocol Info
37304 1917.078502 192.168.0.100 127.0.1.1 TFTP Read
Request, File: /ltsp/i386/pxelinux.0, Transfer type: octet, blksize=1456
Frame 37304 (85 bytes on wire, 85 bytes captured)
Ethernet II, Src: Micro-St_c6:35:95 (00:13:d3:c6:35:95), Dst:
QuantaCo_28:15:65 (00:c0:9f:28:15:65)
Internet Protocol, Src: 192.168.0.100 (192.168.0.100), Dst: 127.0.1.1
(127.0.1.1)
User Datagram Protocol, Src Port: 2075 (2075), Dst Port: tftp (69)
Trivial File Transfer Protocol
I don't know what happens. Is it hopeless or still can be managed by tweaking
some options in tftp-hpa or dhcpd.conf?
Thank you very much.
--
Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial
http://linux2.arinet.org
10:39:50 up 53 min, 2.6.22-14-generic GNU/Linux
Let's use OpenOffice. http://www.openoffice.org
The real challenge of teaching is getting your students motivated to learn.
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_____________________________________________________________________
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
