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

    No DHCP response (Multiple VLAN setup)

    Scheduled Pinned Locked Moved Unsolved
    FOG Problems
    3
    30
    8.3k
    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.
    • Tom ElliottT
      Tom Elliott
      last edited by Tom Elliott

      Useful for all I suppose:

      Curl Error List is found here.

      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
        mhanna @Tom Elliott
        last edited by

        @Tom-Elliott

        Based on what I see that would appear to be the case… except I know its not the case. When the system is pxe booting I am able to ping from the fog server to the client. While at the main fog menu I am able to ping from fog server to client. The moment I select full host registration I am no longer able to ping from fog server to client.

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

          @mhanna said in No DHCP response (Multiple VLAN setup):

          When the system is pxe booting I am able to ping from the fog server to the client. While at the main fog menu I am able to ping from fog server to client.

          This is because the iPXE (fog menu kernel is running at this point in the booting process)

          The moment I select full host registration I am no longer able to ping from fog server to client.

          At this point, the FOS engine is running and not able to pick up (or think’s it can’t pick up) a dhcp address.

          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!

          M 1 Reply Last reply Reply Quote 0
          • M
            mhanna @george1421
            last edited by

            @george1421

            Understood. I was trying to illustrate that there did not appear to be a communication issue between devices on the vlan in question by stateing that they communicate just fine up to a certain point.

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

              The question here, is more about if the client can ping the FOG Server.

              When you are at the FOG PXE Menu, IP Helpers within the route help direct the traffic on where to get an IP Address. This will typically work, but requires the route be accessible by the FOG Server. The Same, however, path must be setup in reverse.

              So it’s fully possible to enable a DHCP server to receive dhcp, but the client side receiving that IP still needs a way to communicate to the fog server.

              You’re certain the iPXE IP Address issued is the same scope the FOS Engine is receiving?

              I ask the questions because, you state the FOG Server can ping the host machine when it’s in PXE mode, but in the FOS System, it’s unable to communicate to the Client Machine anymore. This leads me to think it’s getting an IP Address that can’t route anywhere.

              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

              M 1 Reply Last reply Reply Quote 0
              • M
                mhanna @Tom Elliott
                last edited by

                @Tom-Elliott said in No DHCP response (Multiple VLAN setup):

                the host machine when it’s in PXE mode, but in the FOS System, it’s unable to communicate to the Client Machine anymore. This leads me to think it’s getting an IP Address that can’t route anywhere.

                Its getting the same IP in PXE mode as it is when I select the option to register host. They exact same IP. Which is in the same vlan as the fog server… they are actually only 1 IP apart. I can have a continuous ping going and from the FOG server I can get replies up to the point there I select the register host option. At that point the replies stop. I can then reboot the client and once it start the PXE boot process the pings start replying again… from the same IP. Its really odd… while in PXE it gets DHCP with all the correct information… but once we go anywhere in the Fog menu we lose all connectivity. When running the route command on the client once in debug I see the following:

                Destination Gateway Genmask
                default 192.168.91.193 0.0.0.0
                192.168.91.192 * 255.255.255.192

                192.168.91.193 is the correct gateway for this vlan but is unpingable from the client at this point.

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

                  @mhanna Is the subnet mask supposed to be 255.255.255.192 or 255.255.255.128? (Is the subnet mask setup properly in more direct fashion).

                  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

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    mhanna @Tom Elliott
                    last edited by

                    @Tom-Elliott said in No DHCP response (Multiple VLAN setup):

                    55.255.255.192

                    It is supposed to be .192. This is also reflected on the fog server as well as all DHCP clients on that vlan.

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

                      So doing a quick calculation.

                      Gateway IP address shoudl be 192.168.91.193, the broadcast address for the network should be 192.168.91.255. The network address would be 192.168.91.192.

                      This leaves a network range applicable to:
                      192.168.91.194 through 192.168.91.254.

                      The IP Address the machine is getting is within this scope?

                      This almost seems like the nic goes down and fails to come back up. Is the NIC on the machine a USB NIC?

                      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

                      M 1 Reply Last reply Reply Quote 0
                      • M
                        mhanna @Tom Elliott
                        last edited by

                        @Tom-Elliott

                        The IP the machine is getting both in PXE and when selecting any menu option is 192.168.91.242… within the specified range for that vlan. FOG server is on 192.168.91.243. No, the nic is an onboard broadcom nic on a dell optiplex 580

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

                        148

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project