• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Upgraded to Fog 1.5.3 from 1.4.4. Cannot PXE boot anymore get PXE-55

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    4
    8
    1.2k
    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.
    • B
      buercky
      last edited by

      Upgraded to Fog 1.5.3 from 1.4.4. Cannot PXE boot anymore get PXE-55 ProxyDHCP service did not reply to request on port 4011.
      I didn’t change anything on the dhcp server Option 66 is the IP address of the Fog server and 67 is undionly.kpxe. I’m booting clients as legacy boot as i did before the upgrade.

      Wayne WorkmanW 1 Reply Last reply Reply Quote 0
      • Wayne WorkmanW
        Wayne Workman @buercky
        last edited by

        @buercky Read through this: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
        Daily Clean Installation Results:
        https://fogtesting.fogproject.us/
        FOG Reporting:
        https://fog-external-reporting-results.fogproject.us/

        1 Reply Last reply Reply Quote 0
        • george1421G
          george1421 Moderator
          last edited by

          @buercky said in Upgraded to Fog 1.5.3 from 1.4.4. Cannot PXE boot anymore get PXE-55:

          PXE-55 ProxyDHCP service did not reply to request on port 4011

          Are you running dnsmasq on your fog server? If not check to make sure you are not setting dhcp option 60 on your dhcp server. If neither of these are true then Wayne is on the right track, grabbing a pcap of the dhcp process will tell us what is going down the wire.

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

          B 1 Reply Last reply Reply Quote 0
          • B
            buercky @george1421
            last edited by buercky

            @george1421 I am not running dnsmasq I’ve commented out the dnsmasq in Network Manager. I do not have option 60 on the DHCP server either.
            0_1527780345677_Network Manager.jpg

            Here is the pcap of the dhcp process.
            0_1527780159818_issue1.pcap

            The error i get:
            0_1527780367488_DHCPBoot.jpg

            The Fogserver IP is 89.0.192.40

            Q george1421G 2 Replies Last reply Reply Quote 0
            • Q
              Quazz Moderator @buercky
              last edited by

              @buercky dnsmasq being commented out in networkmanager only means it’s not being used for DNS requests, which is fine.

              Check if dnsmasq is running. service dnsmasq status

              B 1 Reply Last reply Reply Quote 0
              • george1421G
                george1421 Moderator @buercky
                last edited by george1421

                @buercky ok I see something (and its not dead people…)

                For the above system you have 2 dhcp servers responding with offers.
                89.0.0.92 which is giving a next server of 98.0.192.40 with a boot file of undionly.kpxe (you might want to update your dhcp server since you have Undionly.kpxe define and not all lower case undionly.kpxe)

                Then you have the troubling one: 98.0.192.75 (which appears to be a dell computer) is also responding with a next server of itself with no boot file name, but it does have dhcp option 60 set indicating its a proxy dhcp server (where your error message on port 4011 is coming from).

                To fix shoot 98.0.192.75 and pxe booting will start working better. Understand this is not a FOG problem but a networking infrastructure issue.

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                B 1 Reply Last reply Reply Quote 1
                • B
                  buercky @Quazz
                  last edited by

                  @quazz comes up
                  Loaded: not found (Reason: No such file or directory)
                  Active: Inactive (dead)

                  1 Reply Last reply Reply Quote 0
                  • B
                    buercky @george1421
                    last edited by

                    @george1421 Wow! That was it PXE is now working! Thank You Thank you Thank You

                    1 Reply Last reply Reply Quote 1
                    • 1 / 1
                    • First post
                      Last post

                    150

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project