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

    Dhclient question

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    20 Posts 6 Posters 7.0k 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.
    • johnpozJ
      johnpoz LAYER 8 Global Moderator
      last edited by

      Im on 32bit version, don't see a need for pfsense to be 64bit?  Seems to have less issues as well ;)

      But don't they have a newer snap - I show one dated
      New version: Sat Oct 20 19:31:24 EDT 2012

      Is that the one your running?  Im on
      Built On: Fri Oct 19 15:19:38 EDT 2012

      I would either move forward or drop back on the snap.

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 24.11 | Lab VMs 2.8, 24.11

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

        I think you're right about the 64bit. Thanks for the assistance though. I guess I'll have to wait it out and see what happens.

        1 Reply Last reply Reply Quote 0
        • M
          MrT0ad
          last edited by

          @splmachine:

          I think you're right about the 64bit. Thanks for the assistance though. I guess I'll have to wait it out and see what happens.

          Personally I'd delete the default WAN and re-create it, just for the sake of completeness.

          Reason why I say this is because once I changed the default WAN to PPPoE and rebooted those entries were no longer appearing in the box, and after setting up the 2nd WAN (which is also DHCP and requires dhclient) they didn't reappear.

          Something odd in the dhclient.cof on the first setup? just an educated guess…

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

            Just to not leave anyone hanging, I deleted the WAN interface, rebooted but still every 2 minutes I'm getting those messages. I'm going to disable logging for a bit until I can figure it out.

            1 Reply Last reply Reply Quote 0
            • I
              inflamer
              last edited by

              I'm also seing this on a freshly built Intel D2500CCE (HDD install), em1 is my WAN interface which is configured for DHCP:

              Oct 27 13:14:16 dhclient: XMT: Solicit on em1, interval 108120ms.
              Oct 27 13:16:05 dhclient: XMT: Solicit on em1, interval 111070ms.
              Oct 27 13:17:29 check_reload_status: Syncing firewall
              Oct 27 13:17:56 dhclient: XMT: Solicit on em1, interval 110970ms.
              Oct 27 13:17:57 check_reload_status: Syncing firewall
              Oct 27 13:18:43 check_reload_status: Syncing firewall
              Oct 27 13:19:04 check_reload_status: Syncing firewall
              Oct 27 13:19:24 check_reload_status: Syncing firewall
              Oct 27 13:19:24 check_reload_status: Reloading filter
              Oct 27 13:19:48 dhclient: XMT: Solicit on em1, interval 125310ms.

              My build is:

              2.1-BETA0 (amd64)
              built on Thu Oct 25 18:52:59 EDT 2012
              FreeBSD 8.3-RELEASE-p4

              1 Reply Last reply Reply Quote 0
              • C
                cmb
                last edited by

                Those seeing this, you have DHCP6 set on WAN by chance? Guessing this is related to no DHCPv6 being available and recent changes with the DHCPv6 client.

                1 Reply Last reply Reply Quote 0
                • I
                  inflamer
                  last edited by

                  @cmb:

                  Those seeing this, you have DHCP6 set on WAN by chance? Guessing this is related to no DHCPv6 being available and recent changes with the DHCPv6 client.

                  I already disabled IPv6 DHCP on the WAN interface some time ago, but I am still seeing these messages in the system log.

                  1 Reply Last reply Reply Quote 0
                  • P
                    phil.davis
                    last edited by

                    I had DHCPv6 on (default setting) on WAN. There is no IPv6 service on my WAN, so I turned it off today, but the messages keep coming.

                    WAN.png
                    WAN.png_thumb
                    syslog-dhclient.png
                    syslog-dhclient.png_thumb

                    As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                    If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                    1 Reply Last reply Reply Quote 0
                    • P
                      phil.davis
                      last edited by

                      I rebooted and the messages are gone. So I guess the DHCPv6 Client running on WAN does not get stopped when DHCPv6 is turned off in the GUI. But at boot time the scripts know not to bother starting it.

                      As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                      If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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

                        Under WAN interfaces, turning IPv6 Configuration Type to none and rebooting solved it for me. I don't see those messages any longer. Thanks!

                        1 Reply Last reply Reply Quote 0
                        • I
                          inflamer
                          last edited by

                          I can also confirm that the reboot (After disabling DHCP for IPv6) has stopped these log entries from appearing.

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