[syslinux] pxelinux: first contact with tftp is bad

Beber beber at setibzh.com
Wed Jul 7 01:35:36 PDT 2004


Hello !

I'm french, my english is bad :-(

I want to boot a computer by network which have a 3Com network card. So I use
isc-DHCP, TFTP-hpa and PXELinux.
The computer start, make a dhcp request, receive the configuration.
The next step is to contact the tftp server to get pxelinux.0 and the
configuration.

Stop me if I made an error ;)

So, in the network I want to use it, there is a dhcp server, which cannot do
tftp server (his name is packa). And I have another computer which have a tftp
server and that's all on it (his name is srvbck). And there is a last one which
is the client and have the name vmware (not because of the software)

At the boot, dialogs are like that (first are up, last are down):

        SRVBCK                      PACKA                VMWARE
                                                        DHCP REQ
                                   DHCP ACK
                                                        TFTP REQ
                                                       pxelinux.0
                                   TFTP SEND
                                   pxelinux.0
                                                        TFTP REQ
                                                   pxelinux config files
     TFTP SEND
pxelinux config files

And go on....

You can see here that the dhcp dialog is good
but the tftp one is not :
the request for the file pxelinux.0 is to packa and not to srvbck (the problem
is here)
and the config files are ask to srvbck (and that's good)

Here is the /etc/dhcp3/dhcpd.conf important lines :
ddns-update-style none;
option domain-name "isaac.ftrd";
log-facility local7;

subnet  193.252.239.16  netmask                 255.255.255.240 {
        option         broadcast-address        193.252.239.31;
        option         routers                  193.252.239.26;-> IP Adress of
srvbck
        option         subnet-mask              255.255.255.240;
        option         domain-name-servers      193.252.239.27;-> IP Adress of
packa
        allow          bootp;
        allow          booting;
        default-lease-time      600;
        max-lease-time          7200;
        option tftp-server-name "193.252.239.26";
        next-server             193.252.239.26;
        filename                "/pxelinux.0";
        option ntp-servers      193.252.239.27;

        option vendor-class-identifier "PXEClient";
        option vendor-encapsulated-options
09:0f:80:00:0c:4e:65:74:77:6f:72:6b:20:62:6f:6f:74:0a:07:00:50:72:6f:6d:70:74:06:01:02:08:03:80:00:00:47:04:80:00:00:00:ff;

        host vmware {
                hardware        ethernet        00:04:75:7D:8D:80;
                fixed-address   193.252.239.28;-> IP Adress of vmware
                option  host-name       "vmware";
        }
}


You can see that the option next-server is place in the goal that vmware contact
srvbck for the tftp transfert, but srvbck is contact on the second transfert
(after pxelinux.0)

Is it a bug ? Is it a 3Com pxe client bug ?
How can I resolv the problem ?
I really cannot put a tftpserver on the same computer which serv the dhcpd.

Thanks
Beber

--
/* Beber : beber (AT) setibzh (DOT) com
 * https://guybrush.ath.cx
 * Using IMP
 */


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.




More information about the Syslinux mailing list