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

    Wrong Network Interface

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    2
    15
    1.6k
    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.
    • imagingmaster21I
      imagingmaster21
      last edited by

      @Wayne-Workman
      Here is what my DHCP looks like.
      https://dl2.pushbulletusercontent.com/sqF0fk0cF5pcqG4a0ZesbQK5ooEeBAet/20180517_120927.jpg

      https://dl2.pushbulletusercontent.com/sqF0fk0cF5pcqG4a0ZesbQK5ooEeBAet/20180517_120927.jpg

      https://dl2.pushbulletusercontent.com/z8gfNItC5aXxVxn92EgdjkEX1BqVVQHX/20180517_120911.jpg

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

        @imagingmaster21 Check to see if dhcp is running like this systemctl status dhcpd -l

        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/

        imagingmaster21I 1 Reply Last reply Reply Quote 0
        • imagingmaster21I
          imagingmaster21 @Wayne Workman
          last edited by

          @wayne-workman
          https://dl2.pushbulletusercontent.com/J08p9FQbsYLXGwN5l8vqu3Z98q9LnLhP/image.png
          Is the status.

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

            @imagingmaster21 Read through this: https://forums.fogproject.org/topic/11870/failed-to-get-an-ip-via-dhcp-only-on-a-certain-switch

            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/

            imagingmaster21I 3 Replies Last reply Reply Quote 0
            • imagingmaster21I
              imagingmaster21 @Wayne Workman
              last edited by

              @wayne-workman This worked before we upgraded from 1.4.4 to 1.5.0. We haven’t changed anything on the switch and all the settings are correct on the switch I verified those before.

              1 Reply Last reply Reply Quote 0
              • imagingmaster21I
                imagingmaster21 @Wayne Workman
                last edited by

                @wayne-workman
                The switch is… Pvst+ It’s basically a unique spanning-tree per vlan, but its running standard spanning-tree over them (not rapid)

                1 Reply Last reply Reply Quote 0
                • imagingmaster21I
                  imagingmaster21 @Wayne Workman
                  last edited by

                  @wayne-workman
                  I just tried this on a switch that another FOG Server running the same version worked on. The FOG Server that I am having issues on still does not work on the known good switch. So it is not the switch.

                  Any idea on what the culprit could be in DHCP?

                  imagingmaster21I 1 Reply Last reply Reply Quote 0
                  • imagingmaster21I
                    imagingmaster21 @imagingmaster21
                    last edited by

                    @Wayne-Workman @Sebastian-Roth
                    I was looking at this here:
                    https://forums.fogproject.org/topic/7256/no-dhcp-response-when-trying-to-inventory-a-host-fog-trunk

                    I seen about trying a standard switch to see if it worked. So I grabbed a 5 port switch and still did not work. 😞 Here are some more screenshots:

                    • https://dl2.pushbulletusercontent.com/TjpLuWB0KKYGzdG41NsrvEeg1JoKErgy/20180517_133337.jpg
                      -https://dl2.pushbulletusercontent.com/t1T9aZUgVR6dnnp23c74YsfDMYaoH9zk/20180517_133341.jpg
                      https://dl2.pushbulletusercontent.com/zmul5sOnbxVi1AsknychwMCzYWxezeuQ/20180517_133343.jpg

                    I did use trunk to do the upgrade fro 1.4.4 to 1.5.0.

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

                      @imagingmaster21 Are you sure you have 1.5.0 installed? The latest stable is 1.5.2 and if you’re not using that, I would recommend you try it.

                      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/

                      imagingmaster21I 3 Replies Last reply Reply Quote 1
                      • imagingmaster21I
                        imagingmaster21 @Wayne Workman
                        last edited by

                        @wayne-workman
                        I am running 1.5.0-RC-9, would upgrading 1.5.2 fix this potentially?

                        1 Reply Last reply Reply Quote 0
                        • imagingmaster21I
                          imagingmaster21 @Wayne Workman
                          last edited by

                          @wayne-workman
                          Upgraded the version to 1.5.2 and capturing and pulling the image seems to be working correctly now. What would have cause this issue, just a bug in 1.5.0 that was fixed in 1.5.2?

                          1 Reply Last reply Reply Quote 0
                          • imagingmaster21I
                            imagingmaster21 @Wayne Workman
                            last edited by

                            @wayne-workman

                            Going from 1.5.0 to 1.5.2 resolved the issue.

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

                            150

                            Online

                            12.1k

                            Users

                            17.3k

                            Topics

                            155.3k

                            Posts
                            Copyright © 2012-2024 FOG Project