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

    DHCP client unable to get lease from cable provider [solved]

    Scheduled Pinned Locked Moved
    DHCP and DNS
    6
    36
    5.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.
    • I
      itpp21 @itpp21
      last edited by

      3 successful updates now using supersede hardcoded.
      Restored interfaces.inc and entered the hardcoded values+supersede in the advanced settings WAN interface, restart WAN.
      Give it 3 more days, if this also works we have a winner.

      I 1 Reply Last reply Reply Quote 0
      • I
        itpp21 @itpp21
        last edited by

        So far 2 renewals without issues, all respecting supersede (and other) setting via GUI config, Ymmv. but I will consider this a solution to a broken pfsense dhclient.

        1 Reply Last reply Reply Quote 0
        • P
          pablot
          last edited by

          So it seems that dhclient from OPNSense fixes the problem, so, can someone give a little receipe of what had to be done to solve this issue?

          Is it just coping the binary provided here, dhclient_opnsense_19.1 over /sbin/dhclient?

          bmeeksB I 2 Replies Last reply Reply Quote 0
          • bmeeksB
            bmeeks @pablot
            last edited by bmeeks

            @pablot said in DHCP client unable to get lease from cable provider [solved]:

            So it seems that dhclient from OPNSense fixes the problem, so, can someone give a little receipe of what had to be done to solve this issue?

            Is it just coping the binary provided here, dhclient_opnsense_19.1 over /sbin/dhclient?

            You can find the list of changes they made to dhclient here on GitHub: https://github.com/opnsense/src/commits/master/sbin/dhclient. You would need to compile your own copy of the source on a separate FreeBSD 12.2-STABLE machine.

            These guys, like the Netgate team, eventually submit fixes back upstream into FreeBSD. From there they trickle out to the various projects that are based on FreeBSD. But that can sometimes take a bit of time, and also it may be that a particular fix makes it into one FreeBSD version and not another. For example, it may go into 13-CURRENT but not into 12.2-STABLE.

            1 Reply Last reply Reply Quote 0
            • I
              itpp21 @pablot
              last edited by

              @pablot said in DHCP client unable to get lease from cable provider [solved]:

              So it seems that dhclient from OPNSense fixes the problem, so, can someone give a little receipe of what had to be done to solve this issue?

              Is it just coping the binary provided here, dhclient_opnsense_19.1 over /sbin/dhclient?

              Yep, thats all it took. Still running it and still zero problems.

              P 1 Reply Last reply Reply Quote 1
              • P
                pablot @itpp21
                last edited by

                @itpp21 unfortunately it's not working for me. Perhaps I have another problem...

                I 1 Reply Last reply Reply Quote 0
                • I
                  itpp21 @pablot
                  last edited by

                  This is for 2.4.5-p1 and also requires this additional GUI setting "supersede dhcp-server-identifier 255.255.255.255" which the original binary ignores.

                  P 1 Reply Last reply Reply Quote 1
                  • P
                    pablot @itpp21
                    last edited by

                    @itpp21 said in DHCP client unable to get lease from cable provider [solved]:

                    supersede dhcp-server-identifier 255.255.255.255

                    Where should I put that in the GUI?

                    GertjanG 1 Reply Last reply Reply Quote 0
                    • GertjanG
                      Gertjan @pablot
                      last edited by

                      @pablot said in DHCP client unable to get lease from cable provider [solved]:

                      Where should I put that in the GUI?

                      As said implicitly, above :

                      @itpp21 said in DHCP client unable to get lease from cable provider [solved]:

                      When you set for example "supersede dhcp-server-identifier 255.255.255.255" either in the config or hardcoded, the running version of dhclient does no ....

                      Typically, you seleclt :

                      d99d6d65-efe7-4086-9ba1-13d4443f900c-image.png

                      and you enter the path to the file, a file that is created by you with all the options you want.
                      It has to be syntax correct of course.
                      And, as you already understood, should use the options that the binary 'dhclient' understands - is aware of.

                      No "help me" PM's please. Use the forum, the community will thank you.
                      Edit : and where are the logs ??

                      I 1 Reply Last reply Reply Quote 0
                      • I
                        itpp21 @Gertjan
                        last edited by

                        Step1
                        step1.png

                        Step2
                        step2.png

                        Step3
                        step3.png

                        This only works with the client binary you can find in this thread.

                        P 1 Reply Last reply Reply Quote 1
                        • P
                          pablot @itpp21
                          last edited by

                          @itpp21 Great!!!, thank you very much!!!!

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