Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 5 replies
  • Subscribers 28 subscribers
  • Views 24140 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DHCP Option (66) Not working

Allan Pumphrey

Hi, I'm trying to config PXE booting but DHCP Option (66) is missing when I inspect the boot sequence via TCPDump. I have had a look thru the forums but have not found a solution. Has anyone been able to get PXE boot working on a XG appliance?

 

 

UPDATE: I spoke to Sophos support and they suggest a Business Application DNAT rule to forward traffic that comes to the XG's LAN IP on port UDP 69 (TFTP) to the "TFTP Server" which did the trick!

 



This thread was automatically locked due to age.
  • 0

    You will need to search for adding dhcp option, there was a post about using cli to add options.

  • 0 in reply to rfcat_vk

    Thanks for the prompt reply. We are using XG v16.x. We have also added the extra options via the CLI. These are shown at the bottom of the screen shot.

  • 0 in reply to Allan Pumphrey

    Sorry, black on black on a small screen without glasses on.

    You will need to look at the various logs or capture a packet to see if the request is being answered by the DHCP server on the XG.

  • 0

    I am also having issues with this.  The DNAT trick didn't work for me.

    Looking on the XG @ /cfs/system/dhcp/dhcpd.conf you can see the options set, but not sure they are the correct ones.  For ISC DHCP the value of "next-server" and "filename" are required for some device types.  Those values are not set in the configuration file and is likely causing the issue.  I tested with ISC DHCP on a Linux server and it worked correctly with configuration below.

    # XG - /cfs/system/dhcp/dhcpd.conf (Not Working)

    option tftp-server-name "10.10.10.10";
    option bootfile-name "pxelinux.0";

    # Linux Server - /etc/dhcpd.conf (Working)

    next-server 10.10.10.10; #  DHCP server ip
    filename "pxelinux.0";

    For now the XG is not usable as a DHCP server for our environment, which is quite disappointing.

  • 0 in reply to Bracey Summers

    We ended up using the XG DHCP for assigning an IP Addresses only. Then we used Matchbox (Coreos/Kubernetes) to manage our PXE / iPXE requirements (via the Kubernetes Master Node(s)) which works really well for us. But agreed, it was disappointing that XG DHCP does not work as expected.