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

    r4930 - Fedora 21, Unable to "Ignore MAC for imaging"

    Scheduled Pinned Locked Moved Solved
    Bug Reports
    4
    7
    2.8k
    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.
    • Wayne WorkmanW
      Wayne Workman
      last edited by

      I click the checkbox on that second MAC below, hit update, it says updated, but the checkbox becomes unchecked.

      Screenshot 2015-10-12 at 8.10.20 PM.png

      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
      • Tom ElliottT
        Tom Elliott
        last edited by

        This should now be fixed. Thanks for reporting.

        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
        • Wayne WorkmanW
          Wayne Workman
          last edited by Wayne Workman

          I’m not sure I can call this fixed… it’s probably an edge case and quite silly but…

          The two NICs in this machine - they are on two different networks. This machine literally serves as a router in my house.

          One interface gets DHCP, the other gives DHCP (when the server is operational).

          It seems like even though I enable the “Ignore MAC”, it still tries to startup that NIC when it starts the imaging process. This happens when the other NIC is connected to a live switch or access point. When I disconnect the line from the second NIC, FOG briefly tries to start the interface and then moves on (detecting that it’s unplugged).

          See the attached screen shot:

          IMG_20151015_220121.jpg

          I suppose what I’m asking for is… doing more than simply checking the MAC of the device that is network booting for a matching MAC, but actually ignoring the interface for the “Ignored MAC”, and not attempting to start that interface. Because right now, while I can image (and it took me a while to figure it out), it’s not hands free. and that’s kinda a large selling point of FOG is the hands free aspect.

          If even the “Sending Discover” could be limited to… idk… 5, that would solve this problem. and I think that would be a simple fix. The more complex but clean solution is obviously to never even try to start the interface of the “ignored MAC”.

          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
          • Wayne WorkmanW
            Wayne Workman
            last edited by

            I believe I have the same problem described here: https://forums.fogproject.org/topic/5159/2-nic-in-host-problem-loops-at-sending-discovery

            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
            • Tom ElliottT
              Tom Elliott
              last edited by

              The ignore Mac for imaging does not remove the ip definitions for a specific interface, at least not yet. All nics that are valid and have a link up indicator will attempt to receive an IP. It should fail out at some point though. What ignore for imaging does is make sure that nic does not get used as the method for checkin and progress.

              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
              • Joseph HalesJ
                Joseph Hales Testers
                last edited by

                I think what you need to do is see if you can disable pxe boot for the individual NIC in bios.

                RTFM

                1 Reply Last reply Reply Quote 0
                • P
                  patc15
                  last edited by

                  Has this been fixed in the latest svn revision? Because I’m having this problem as well (2 NICS and a forever sending discover loop).

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

                  266

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project