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

    TFTP only working with certain VLANs.

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    4
    18
    2.2k
    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.
    • george1421G
      george1421 Moderator @zpoling
      last edited by george1421

      @zpoling said in TFTP only working with certain VLANs.:

      “Please enter tftp server:”

      This is telling me that your dhcp server is not sending out the dhcp option 66 correctly -OR- you have 2 dhcp servers responding to the target computer (like in a primary and secondary configuration) where the second dhcp server doesn’t have the options set correctly.

      FWIW: This issue is a networking infrastructure one and not specifically related to FOG.

      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!

      Z 1 Reply Last reply Reply Quote 0
      • Z
        zpoling @george1421
        last edited by

        @george1421 I don’t know how it couldn’t be sending the option out properly. If I have them set globally and every subnet works besides one of them, I don’t know what it could be. Unless someone happened to plug in a DHCP server enabled device to that subnet, but there doesn’t appear to be any evidence of that anywhere.

        I’m sure this isn’t fog, but I’m still at a loss.

        9am-5pm Eastern | Monday-Friday

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

          @zpoling First understand I’m only suggesting based on past experience. The system prompting for a tftp server in your screen shot is at an interesting point.

          Initially the boot server needs to have been originally detected correctly because at the point its asking for the tftp server address that is INSIDE iPXE. So it worked the first time and now the second time the dhcp address is discovered its not detecting option 66 correctly. That (based on past experience) tells me there are more than 1 dhcp server responding.

          Using wireshark to grab the pcap connected to the vlan that is in error, then pxe boot a target computer. That will tell us what is flying down the wire. Since its only one vlan I would focus on that vlan because there is something going on that is not expected.

          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!

          Z 1 Reply Last reply Reply Quote 0
          • Z
            zpoling @george1421
            last edited by

            @george1421 I would love to send you a pcap of the issue, but it’s no longer happening. I’ve tested several work stations a couple dozen times. They’ve all been fine.

            So the VLAN 3 pcap was not enough to see what was going wrong?

            9am-5pm Eastern | Monday-Friday

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

              @zpoling said in TFTP only working with certain VLANs.:

              So the VLAN 3 pcap was not enough to see what was going wrong?

              Was the pcap taken from a computer connected to vlan 3 while it was doing the asking for tftp server question? It looks like it was taken from the fog server.

              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!

              Z 1 Reply Last reply Reply Quote 0
              • Z
                zpoling @george1421
                last edited by

                @george1421 No, it was a TCPdump from the fog server.

                9am-5pm Eastern | Monday-Friday

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

                  @zpoling That is what I thought.

                  Without going to deep into this. DHCP uses broadcast messages to communicate. If there is a router between the system doing the pcap collection and the pxe booting computer we will not see the dhcp communications. This is the bits that are missing, what the client computer was being told.

                  With a pcap from vlan 3 we should have seen the complete dhcp sequence of discover, offer, request, ack.

                  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!

                  Z 2 Replies Last reply Reply Quote 0
                  • Z
                    zpoling @george1421
                    last edited by zpoling

                    @george1421 Here you go. Taken from my computer on VLAN 3, attempting a pxe boot on the computer that was having an issue. Though like I said, it seems to be working fine now.

                    0_1541174066153_vlan3computer.pcap

                    The computer in question is 10.32.10.118, DHCP server is 10.32.0.224, and the fog server is 10.32.0.31.

                    9am-5pm Eastern | Monday-Friday

                    1 Reply Last reply Reply Quote 0
                    • Z
                      zpoling @george1421
                      last edited by

                      @george1421 Don’t spend too much time on it if at all since it’s working now. I’d love to know why it wasn’t working, but I assume those packet captures aren’t going to show jack since they weren’t captured during the issue’s occurrence.

                      9am-5pm Eastern | Monday-Friday

                      1 Reply Last reply Reply Quote 0
                      • S
                        Sebastian Roth Moderator
                        last edited by Sebastian Roth

                        @zpoling DHCP handshake looks good in the latest PCAP but as you said we won’t find out what was going on when it failed. More often than not those kinds of issues keep coming back until you really find and fix them. Make sure to capture the traffic when you see it happening next time.

                        Marking this as solved for now.

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

                        139

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project