[syslinux] PXE/TFTP Transfer time out problems

[Geert Stappers]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Sep 08, 2005 at 01:25:04PM -0600, Jason Gerfen wrote:
> I am having a problem while trying to download anything from a recently 
> configured tftp boot server.
> 
> Here are the configuration for the dhcpd.conf
> 
   <snip/>
> 
> subnet 155.97.17.160
         ^^^^^^^^^^^^^

>        netmask 255.255.255.224 {
>                option domain-name-servers ns.domain.com, ns1.domain.com;
>                option routers routerIP;
>        }
> 
> group {
>        next-server tftp_server;

Don't put underscores in hostnames, they are not allow by RFC 1035
 ( http://www.ietf.org/rfc/rfc1035.txt )

>        filename "pxelinux.0";
>        host PXE-Client {
>                hardware ethernet 00:02:B3:EF:75:39;
>                fixed-address 192.168.0.1;
                               ^^^^^^^^^^^^

Doesn't match the previous address (range)

>        }
> }
> 
> Here are is the tcpdump data being recieved when getting a pxelinux.0
> 
> 13:52:42.837342 IP (tos 0x0, ttl  62, id 0, offset 0, flags [DF], 
> length: 50) 192.168.0.2.1027 > tftp.server.com.tftp: [udp sum ok]  22 
                       ^^^
Previous was about address .1

> RRQ "pxelinux.0" netascii
> 13:52:47.834011 IP (tos 0x0, ttl  62, id 0, offset 0, flags [DF], 
> length: 50) 192.168.02.1027 > tftp.server.com.tftp: [udp sum ok]  22 RRQ 
> "pxelinux.0" netascii
> 
> And here is the output of a tftp request for the same file
> 
> tftp> get pxelinux.0
> getting from 155.97.16.163:pxelinux.0 to pxelinux.0 [netascii]
> sent RRQ <file=pxelinux.0, mode=netascii>
> sent RRQ <file=pxelinux.0, mode=netascii>
> sent RRQ <file=pxelinux.0, mode=netascii>
> sent RRQ <file=pxelinux.0, mode=netascii>
> sent RRQ <file=pxelinux.0, mode=netascii>
> Transfer timed out.
> 
> The transfer times out and I am left with a file "pxelinux.0" with a 
Because server and client are on different IP networks

> filesize of 0 bytes.
File was created, but no data recieved.

> 
> I am not able to find any information regarding this problem using 
> google or searching the syslinux mailing list.  Any help is appreciated.


Connect the administrator of the network 155.97.17.160/255.255.255.224
and ask for an address for the client ( so that it will be an other then
192.168.0.* )
 
> 
> -- 
> Jason Gerfen
> 
> "In the absence of justice, what is sovereignty but organized robbery?"
> ~ Saint Augustine


Cheers
Geert Stappers

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFDIa5LOSINbgwa/7sRAtJ1AKCdxo1BJz9WmQ8xTFWtyoShp7O6/gCgxsMX
yEpzGlrIeDDSKQQyDGG/RvA=
=NXKZ
-----END PGP SIGNATURE-----