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

    incorrect IPs in IPXE

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    ipxe dhcp
    2
    7
    1.5k
    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.
    • K
      kaveen
      last edited by

      Server
      • FOG Version: 1.4.4
      • OS: Ubuntu server LTS 16.04
      Client
      • Service Version: hyperV/HP 800 G1
        (Same error on VM and workstation)
      • OS: Windows 7
      Description

      DHCP is served from a separate windows server. Option 066 (ip for fog server) and 067 are (undionly.kpxe) is correctly configured. Initially IP address and option 066 are correctly passed onto the PXE boot process.

      Then when ipxe configures net0 with completely different information with IPs not even in the network scope. (see the below screenshot)
      0_1503661671967_fog ipxe error1.PNG

      I manually configured ipxe ‘config’ command and it worked fine.

      DHCP is configured with a second failover server (windows). I’ve double checked there are no other proxyDHCP or a rouge DHCP server connected to the network. Could someone shed some light into this issue. Is there any thing should I manually configure in FOG server?

      Thanks In advance.
      K

      1 Reply Last reply Reply Quote 0
      • K
        kaveen
        last edited by

        I checked PXE on multiple PCs they all get a unique IP assigned in 192.168.30.xxx range. My DHCP settings are in 172.16.1.xxx range

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

          It really sounds like you have two or more dhcp servers in your broadcast domain .

          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!

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

            If you follow these instructions and capture a pcap of the pxe booting process we can tell what is going down the wire. For this test your dhcp server, fog server, and pxe booting client should be on the same subnet so that we can see the entire pxe booting conversation. Capture the pcap and post to a google drive or dropbox. Either post the link here or send me an IM and I will take a look at it and tell you what is going on.

            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!

            K 1 Reply Last reply Reply Quote 3
            • K
              kaveen @george1421
              last edited by

              @george1421 Thanks. Starting to do that now : )

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

                After reviewing the pcap file we found there IS a second dhcp server on the OP’s network. The OP is currently addressing the second dhcp server 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!

                1 Reply Last reply Reply Quote 1
                • K
                  kaveen
                  last edited by

                  With help From Geroge1421 we discovered that there was a rouge DHCP server connected to the network. It was running from a VM on a regular PC. Network admins were able to locate the port relates to the MAC address of the rouge server.

                  Now PXE is booting to FOG smoothly

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

                  154

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project