Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Dhcp lease client hostname missing (with 2.3)

    Scheduled Pinned Locked Moved DHCP and DNS
    35 Posts 11 Posters 12.6k Views
    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.
    • C
      cmb
      last edited by

      Thanks Vynce. Once it's fixed, please start a new ticket at redmine.pfsense.org to revert that change, as it would be preferable to go back to the default there once it doesn't break other things.

      1 Reply Last reply Reply Quote 0
      • V
        vynce
        last edited by

        Sounds good, will do.

        1 Reply Last reply Reply Quote 0
        • V
          vynce
          last edited by

          Just a heads up that a patch for this issue has been committed to master in the isc-dhcp project and will be included in the isc-dhcp 4.3.5 beta. I will create a pfSense ticket to pull in isc-dhcp 4.3.5 final once it is released and revert Chris's workaround. I might try to build a pfSense-compatible dhcpd that includes this patch to verify the fix.

          1 Reply Last reply Reply Quote 0
          • D
            driiper
            last edited by

            I upgraded to 2.3.2 but are still having this issue with some of my boxes. I run a proxmox (KVM / LXC ) hypervisor. While the KVM boxes keeps their hostname in the dhcp records. The LXC boxes loses it after a while.

            Do i have to do anything to apply this fix to a upgraded system (2.3.2)?

            1 Reply Last reply Reply Quote 0
            • V
              vynce
              last edited by

              You shouldn't have to do anything AFAIK. You can verify that the workaround is in place:

              • Diagnostics -> Edit File.

              • Paste "/var/dhcpd/etc/dhcpd.conf" in the box and click Load.

              • Verify that dhcp-cache-threshold 0; is listed in the file.

              1 Reply Last reply Reply Quote 0
              • V
                vynce
                last edited by

                isc-dhcp 4.3.5 was released today and includes the fix for this issue. I've opened a new bug ticket to track upgrading to 4.3.5 and revert the workaround that Chris added.

                1 Reply Last reply Reply Quote 0
                • R
                  rsq
                  last edited by

                  The workaround does not seem to be working for DHCPv6.

                  I verified that the workaround is in place in /etc/inc/services.inc . It appeared in 2 locations in the file.

                  Clients are ubuntu 14.04.3 LTS and 16.04 LTS.

                  On this version:
                  2.3.2-RELEASE-p1 (amd64)
                  built on Tue Sep 27 12:13:07 CDT 2016
                  FreeBSD 10.3-RELEASE-p9

                  1 Reply Last reply Reply Quote 0
                  • MikeV7896M
                    MikeV7896
                    last edited by

                    @rsq:

                    The workaround does not seem to be working for DHCPv6.

                    In DHCPv6, the client does not provide its hostname to the DHCP server. The only form of identification is the DUID, a unique identifier that is generated by the operating system when the computer is set up. The only way a hostname is present under DHCPv6 is if it's a static entry, where you can enter a hostname yourself.

                    The S in IOT stands for Security

                    1 Reply Last reply Reply Quote 0
                    • A
                      anschmid Banned
                      last edited by

                      I am on 2.3.3-p1 and have issues with missing hostnames.

                      Found this threat and checked if dhcp.conf has the "dhcp-cache-threshold 0;" and it doesn't.

                      Is this still needed or should this be fixed without the workaround?

                      1 Reply Last reply Reply Quote 0
                      • V
                        vynce
                        last edited by

                        The workaround is no longer needed since the root issue was fixed in isc-dhcp 4.3.5, which is included in pfSense 2.3.3. That's not to say there isn't some other issue causing missing hostnames, but I haven't seen a regression of this specific issue in pfSense 2.3.3.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.