Navigation

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

    Dhclient:FAIL

    DHCP and DNS
    3
    6
    6976
    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.
    • S
      Sup3rior last edited by

      Seeing this error: dhclient:FAIL in the log files of both our pfSense boxes (running CARP). It is logged 6 times in a row and then nothing for a minutes or so, then again 6 times and so on…
      None of the interfaces (WAN, LAN or PFSYNC) is running DHCP, and there is another DHCP server on the internal network providing addresses. The 2 pfSense's are used as core router/NAT router and firewall, as well as running a bunch of ipsec tunnels...

      When I look in Status\Services it doesn't show dhclient as running (nor listed there at all) so I'm a bit confused as why this error is popping up. pfSense version is 2.0-RELEASE (AMD64).

      Any suggestions?

      Regards,
      Anders

      1 Reply Last reply Reply Quote 0
      • W
        wallabybob last edited by

        @Sup3rior:

        None of the interfaces (WAN, LAN or PFSYNC) is running DHCP,

        That would be DHCP server.

        @Sup3rior:

        Seeing this error: dhclient:FAIL in the log files of both our pfSense boxes

        That suggests you have (or had) at least one interface that requested configuration information (including IP address) from a DHCP server.

        @Sup3rior:

        When I look in Status\Services it doesn't show dhclient as running (nor listed there at all)

        Services are offered by servers. dhclient is not considered a service (it issues requests to a server) so it won't be listed as a service.

        @Sup3rior:

        Any suggestions?

        Post the output of pfSense shell command ps ax | grep dhclient (since dhclient apparently exits and restarts about a minute later you might have to repeat this command a number of times to see anything other than the grep process). This should identify the interface(s) on which dhclient is running.

        1 Reply Last reply Reply Quote 0
        • S
          Sup3rior last edited by

          Hi,

          the output of ps ax command is the following:

          9266  ??  INs    0:54.56 dhclient: bge0 [priv] (dhclient)
          37162  ??  SNs    4:30.68 dhclient: bge0 (dhclient)
          37507  0  S+    0:00.00 grep dhclient

          Which I assume tells me that it's the interface named BGE0 that is running the dhclient. The odd thing is that this interface has never had a DHCP address nor is a DHCP server available on that interface.

          Regards,
          Anders

          1 Reply Last reply Reply Quote 0
          • W
            wallabybob last edited by

            @Sup3rior:

            Which I assume tells me that it's the interface named BGE0 that is running the dhclient.

            dhclient is running to issue DHCP requests on interface bge0.

            @Sup3rior:

            The odd thing is that this interface has never had a DHCP address nor is a DHCP server available on that interface.

            It would appear that interface bge0 is (or was?) configured in pfSense with Type=DHCP. If the current configuration doesn't have Type=DHCP then try rebooting and see if dhclient starts again.

            1 Reply Last reply Reply Quote 0
            • S
              Sup3rior last edited by

              @wallabybob:

              It would appear that interface bge0 is (or was?) configured in pfSense with Type=DHCP. If the current configuration doesn't have Type=DHCP then try rebooting and see if dhclient starts again.

              I had the backup node in the CARP cluster offline yesterday for another reason, and after it came online again the DHCLIENT errors went away on that. When I have a chance to do this with the master node it would seem that it would make the error go away here as well.

              Regards,
              Anders

              1 Reply Last reply Reply Quote 0
              • jimp
                jimp Rebel Alliance Developer Netgate last edited by

                It's probably just this:

                http://redmine.pfsense.org/issues/2212

                Safe to ignore, but if you don't have any interfaces that get their IP from DHCP, you can just: killall -9 dhclient

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

                Products

                • Platform Overview
                • TNSR
                • pfSense
                • Appliances

                Services

                • Training
                • Professional Services

                Support

                • Subscription Plans
                • Contact Support
                • Product Lifecycle
                • Documentation

                News

                • Media Coverage
                • Press
                • Events

                Resources

                • Blog
                • FAQ
                • Find a Partner
                • Resource Library
                • Security Information

                Company

                • About Us
                • Careers
                • Partners
                • Contact Us
                • Legal
                Our Mission

                We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

                Subscribe to our Newsletter

                Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

                © 2021 Rubicon Communications, LLC | Privacy Policy