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

PXE Boot error (TFTP IP in IPXE)

Scheduled Pinned Locked Moved Solved
FOG Problems
2
6
696
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.
  • G
    guilux
    last edited by Apr 26, 2019, 8:57 AM

    Hi all,

    I’m having an error connecting a PXE client. DHCP gives me the good ip in good range (10.171.27.xxx), but after TFTP in IPXE is 192.168.1.xxxx.
    Sometimes it’s works randomly and TFTP Ip is good.
    Fog server is 10.171.27.241

    My error
    1.jpg

    My /tftpboot/default.ipxe
    2.png

    Thanks for your help.

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by george1421 Apr 26, 2019, 11:57 AM Apr 26, 2019, 9:32 AM

      I’m going to say you have 2 dhcp servers on your network. Also since you are getting 192.168.1.1, I’m also going to predict you have a soho router/access point on your network.

      If the fog server and the target computer are on the same subnet (vlan) we can use the fog server to find out for sure if this is the case. You will have to do a little (not much) setup: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

      You can either load the pcap into wireshark and look to see if you have 2 dhcp offers. If so you do have 2 dhcp servers on your network one will be your official dhcp server and the other will be your rogue dhcp server. If you can’t figure it out upload the pcap to a file share site and post the link here so we can review it for you.

      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
      • G
        guilux
        last edited by Apr 26, 2019, 9:59 AM

        Hi George,
        Thank you for your answer. This is my Output Pcap

        2019-04-26 11_56_40-output.pcap.png

        1 Reply Last reply Reply Quote 0
        • G
          guilux
          last edited by Apr 26, 2019, 10:08 AM

          The output pcap
          output.pcap

          1 Reply Last reply Reply Quote 0
          • G
            guilux
            last edited by Apr 26, 2019, 11:46 AM

            I found the culprit
            2019-04-26 13_44_44-output.pcap.png

            Thank you so much George !!!

            G 1 Reply Last reply Apr 26, 2019, 11:52 AM Reply Quote 0
            • G
              george1421 Moderator @guilux
              last edited by george1421 Apr 26, 2019, 5:54 AM Apr 26, 2019, 11:52 AM

              @guilux Sorry I’m late to get back to this thread, but I’m glad you found the troublemaker!!

              I was going to tell you that now you have the mac address you can go to your network team and have them look at the mac tables to find out what port that device is connected to. That is the way to track it down. But you find it, so great!

              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 0
              • 1 / 1
              1 / 1
              • First post
                2/6
                Last post

              117

              Online

              12.1k

              Users

              17.3k

              Topics

              155.3k

              Posts
              Copyright © 2012-2024 FOG Project