DHCP Option 66 ignored

dhcppxe-boottftp

Im trying to setup a PXE boot server to deploy CloneZilla images easily, using pxelinux.0.
I have a tftp-hpa server running on a server, I tested it with a client and it works fine.
We are using a FortiNet router as the DHCP server, so I added that :

set option1 66 '3139322e3136382e302e313533'
set option2 67 '7078656c696e75782e30'

Which would translate to 192.168.0.153 for the option 66, and pxelinux.0 for option 67.
I dumped the DHCP offer packets to check, and that seems to be correct.
When I try to boot an empty VMware workstation VM on PXE to check however, it does receive the options, but it asks the DHCP server (192.168.0.1) for the file pxelinux.0, completely ignoring option 66. Is that somehow normal behavior ? I've seen mention of option 43 and 60, but I understood it's used only for Microsoft environments. Maybe I'm supposed to set those options to something anyway to make the option 66 used ?

Best Answer

Figured out a way to make it work. It looks like the option 66 isn't actually used by anyone, instead the next-server part of the protocol is used. Unfortunately, I can't change it on my version of the Fortinet firmware, it's automatically set to it's own address, so I added a policy to redirect traffic coming to port 69 (tftp) of the fortinet to the actual TFTP server, and it works perfectly. That's not a great solution, but at least it works.

Related Solutions

Ubuntu – pxe boot fails with message: no DEFAULT or UI configuration directive found

for "no default or ui configuration directive found" try change

from  KERNEL vmlinuz-2.6.35-25-generic-pae
      APPEND ....optopns...
to    DEFAULT vmlinuz-2.6.35-25-generic-pae ....options...

or use UI menu. it help me with ubuntu 10.10 pxeboot.0

Linux – LTSP – TFTP, PXE and pxelinux.0 issue

PXE boot goes from parent of tftp directory specified in xinetd or some other super server. Here is mine:

[root@sl6 dhcp]# more /etc/xinetd.d/tftp 
# default: off
# description: The tftp server serves files using the trivial file transfer \
#   protocol.  The tftp protocol is often used to boot diskless \
#   workstations, download configuration files to network-aware printers, \
#   and to start the installation process for some operating systems.
service tftp
{
    disable = no
    socket_type     = dgram
    protocol        = udp
    wait            = yes
    user            = root
    server          = /usr/sbin/in.tftpd
    server_args     = -s /var/lib/tftpboot
    per_source      = 11
    cps         = 100 2
    flags           = IPv4
}

So you either need to change the server arg path so that it is point to the location of your images or you move the image so that they are located here:

/var/lib/tftpboot/ltsp/i386/images/pxelinux.0
/var/lib/tftpboot/ltsp/i386/images/i386.img

Best Answer

Related Solutions

Ubuntu – pxe boot fails with message: no DEFAULT or UI configuration directive found

Linux – LTSP – TFTP, PXE and pxelinux.0 issue

Related Topic