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

    FOG 1.2.0 w/ DHCP/BOOTP Reply not for us

    Scheduled Pinned Locked Moved
    FOG Problems
    4
    18
    7.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.
    • JunkhackerJ
      Junkhacker Developer
      last edited by

      do you have portfast enabled? is STP disabled?

      signature:
      Junkhacker
      We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

      1 Reply Last reply Reply Quote 0
      • M
        mbeeler
        last edited by

        I am not sure on portfast, STP is disabled but there is plans to enable extremes version of STP called ELRP.

        1 Reply Last reply Reply Quote 0
        • Tom ElliottT
          Tom Elliott
          last edited by

          Have you tried the undionly.kkpxe supplied?

          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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

          1 Reply Last reply Reply Quote 0
          • M
            mbeeler
            last edited by

            I have a lab of 1600’s that is currently being deployed. Once it is done I will try that one and let you know. Is there a process I need to do to undo the chainloading of pxe to ipxe or will it matter?

            1 Reply Last reply Reply Quote 0
            • JunkhackerJ
              Junkhacker Developer
              last edited by

              if you set the network to boot to one of the ipxe file, like undionly.kpxe, that should be all you need to do. the chainloading is done by pxelinux.0, and if that’s not the network boot file, the chainloading isn’t done

              signature:
              Junkhacker
              We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

              1 Reply Last reply Reply Quote 0
              • M
                mbeeler
                last edited by

                I have tried both undionly.kpxe and undionly.kkpxe from official 3.14.2 kernel as well as the unofficial 3.16.0 kernel. They both still give me the DHCP/BOOTP Reply not for us message on the Optiplex 755 have not tried on the 760 yet.

                1 Reply Last reply Reply Quote 0
                • M
                  mbeeler
                  last edited by

                  After letting them sit for awhile they do go into the registration process then do what is in the picture.[ATTACH=full]1264[/ATTACH]

                  [url=“/_imported_xf_attachments/1/1264_2014-08-07_11-09-35_290.jpg?:”]2014-08-07_11-09-35_290.jpg[/url]

                  1 Reply Last reply Reply Quote 0
                  • M
                    mbeeler
                    last edited by

                    I can now add a third model to my list that will not work. So total that I have on my campus that will not register with fog include Dell optiplex 755, 760, and 780. They all three give the DHCP/BOOTP Reply not for us error.

                    1 Reply Last reply Reply Quote 0
                    • JunkhackerJ
                      Junkhacker Developer
                      last edited by

                      i have tested the 755 and 780 myself, the problem is your network

                      signature:
                      Junkhacker
                      We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                      1 Reply Last reply Reply Quote 0
                      • M
                        mbeeler
                        last edited by

                        So what has changed from version .32 where this worked with no problems on our network to now? We do not have STP enabled on our network. All switches are Extreme Networks brand

                        1 Reply Last reply Reply Quote 0
                        • J
                          Joe Schmitt Senior Developer
                          last edited by

                          That error “No DHCP or proxyDHCP offers were received” sounds like the computers are looking to FOG for an ip address ( I have run into this issue but with a different model), this method should also get your undionly.kpxe working without the need of chainbooting. First undo the changed you have made to chainload PXE to IPXE. Once that is done,install dnsmasq by running [B]sudo apt-get install dnsmasq[/B] Then follow this guide. [url]http://www.fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/url], (ltsp.conf is located in /etc/dnsmasq.d/)

                          If your computers are on the 192.168.x.x subnet, change the line in /etc/dnsmasq.d/ltsp.conf that says
                          [code]dhcp-range=10.0.0.10,proxy[/code]
                          to
                          [code]dhcp-range=192.168.1.10,proxy,255.255.0.0[/code]

                          Afterwards restart the dnsmasq service. If running [B]sudo service dnsmasq restart[/B] fails, use [B]sudo /etc/init.d/dnsmasq restart[/B] instead.

                          Ensure that you did that step where you made a symlink between undionly.kpxe and undionly.0, if you don’t computers won’t find a file to boot to.

                          Once you have completed those steps, test a computer.

                          If this method works, you can disable the 3 second time-out on network boots by changing the line [B]pxe-prompt=“Press F8 for boot menu”, 3[/B] in /etc/dnsmasq.d/ltsp.conf to [B]pxe-prompt=“Press F8 for boot menu”, 0[/B]

                          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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                          1 Reply Last reply Reply Quote 0
                          • M
                            mbeeler
                            last edited by

                            Jbob thank you that seems to be working on the 755, I will be able to test on the 760 and the 780 later this afternoon.

                            1 Reply Last reply Reply Quote 0
                            • M
                              mbeeler
                              last edited by

                              This did work for the 760’s and 780’s as well. Thank you very much for the help Jbob, Junkhacker, and Tom

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

                              153

                              Online

                              12.0k

                              Users

                              17.3k

                              Topics

                              155.2k

                              Posts
                              Copyright © 2012-2024 FOG Project