• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

PXE boot issues during TFTP stage

Scheduled Pinned Locked Moved General pfSense Questions
2 Posts 1 Posters 2.5k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    jonesr
    last edited by Feb 26, 2017, 6:26 PM

    I have a PXE deployment server which works perfectly within its own network. However on a second network the PXE boot stage begins but then fails to proceed.

    • In both networks pfSense is the DCHP server handing out the IPs and PXE config, ie the deployment server IP address and boot file.

    • On the second network UDP 69 is allowed and no other traffic is logged as blocked.

    • Without the TFTP proxy enabled the client times out downloading the PXE boot program

    • With the TFTP proxy enabled, in the screenshot attached the last line is from the PXE boot program so clearly it has managed to connect to the server and communicate, but proceeds no further.

    Is there anything else I can try? Thanks in advance for any suggestions.

    Regards.
    PXE.png
    PXE.png_thumb

    pfSense AMD64 VGA - Assume latest version.
    Suricata, pfBlockerNG, SquidGuard, squid3.

    1 Reply Last reply Reply Quote 0
    • J
      jonesr
      last edited by Mar 3, 2017, 5:36 PM

      I think I may have fixed this. Hope this helps someone else:

      My setup is pfSense as DHCP server, and a WDS server acting as the deployment server but with WDSLinux also in play - http://www.syslinux.org/wiki/index.php?title=WDSLINUX

      Disable TFTP proxy
      Configure pfSense DHCP server for network boot on the client side interface, with next server IP address as the WDS server and for bootfile, for WDSLinux, "boot\x64\pxelinux.com"
      Allow UDP 69 on client side pfSense firewall rules through to the server.
      Allow UDP >1024 on server side pfSense firewall rules through to the client.

      The last comment due to seeing blocked traffic on ports 2070-2079 on one attempt and 49152 on a second. I looked up the ports but the associated services didn't seem relevant so I guess it must be picking a random higher port. I hope to clean this rule down but this is what it took to get it to work.

      pfSense AMD64 VGA - Assume latest version.
      Suricata, pfBlockerNG, SquidGuard, squid3.

      1 Reply Last reply Reply Quote 0
      2 out of 2
      • First post
        2/2
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
        This community forum collects and processes your personal information.
        consent.not_received