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

    Keep loosing WAN IP Address - dhclient does not seem to do update

    Scheduled Pinned Locked Moved DHCP and DNS
    199 Posts 27 Posters 112.4k 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.
    • S
      sullrich
      last edited by

      At this point reinstall.  My dhclient has been rock solid for over 24 hours!

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

        mine to, but only after i pushed the renew button the first time it died, strange

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

          Make that 48 hours.  And Vescovo has been running it for 48 hours on 2 wans with 180 second renewal time.

          This issue is fixed for sure and verified now by 3 different people.

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

            Thats nice to hear =)

            But just one thing, could you reboot your pfsense and monitor it again ?

            My issue always come after a while when pfsense is rebooted, and the issue disappears after i push the renew button.

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

              Yes, it has been rebooted once.

              1 Reply Last reply Reply Quote 0
              • Y
                yoda715
                last edited by

                Mine has been steady for the last 2 days as well.

                1 Reply Last reply Reply Quote 0
                • T
                  ThomasF
                  last edited by

                  I also get the dhcp problem only one time after each boot.
                  I have also been losing functionality of the DNS forwarder since upgrading to 1.0.2-0221 from 1.0.1 but that seems to have vanished since I started out with a fresh config.

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

                    as i said, happens one time after reboot, then press renew and the issue disappears,
                    there is something magic about the renew button that doesn´t happen in the reboot process =)

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

                      I have rebooted countless times and cannot reproduce this.  Sorry.

                      1 Reply Last reply Reply Quote 0
                      • T
                        ThomasF
                        last edited by

                        I don't think I am affected by that bug, It's much worse for me :(
                        After about 12h uptime (this time) the interface went down, when i renewed the ip adress nothing worked correctly, I could not do nslookup. Didnt try anything else. I restarted the DNS forwarder, it made no difference. I'm not sure about this but my hardware could be very incompatible with pfsense 1.0.2/fbsd 5.2.

                        Feb 27 08:43:36 kernel: arplookup  66.249.93.99 failed: could not allocate llinfo
                        Feb 27 08:43:36 kernel: arpresolve: can't allocate route for  66.249.93.99

                        Just wanted to say this, I don't have time to look further into this at the moment.

                        EDIT: SNAPSHOT-02-27-2007 solved my problems

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

                          @ThomasF:

                          I don't think I am affected by that bug, It's much worse for me :(
                          After about 12h uptime (this time) the ip adress went down, when i renewed it nothing worked correctly, I could not do nslookup. Didnt try anything else. I restarted the DNS forwarder, it made no difference. I'm not sure about this but my hardware could be very incompatible with pfsense 1.0.2/fbsd 5.2.

                          Feb 27 08:43:36 kernel: arplookup  66.249.93.99 failed: could not allocate llinfo
                          Feb 27 08:43:36 kernel: arpresolve: can't allocate route for  66.249.93.99

                          This is not the same problem.  Please start a new thread.  And for the record, we do not use FreeBSD 5.2.

                          1 Reply Last reply Reply Quote 0
                          • H
                            hoba
                            last edited by

                            @ThomasF:

                            Feb 27 08:43:36 kernel: arplookup  66.249.93.99 failed: could not allocate llinfo
                            Feb 27 08:43:36 kernel: arpresolve: can't allocate route for  66.249.93.99

                            Any possibility that you try to run PPPoE along with Multiwan like in the following thread?
                            http://forum.pfsense.org/index.php/topic,3554.0.html

                            If this is true please add your comments to this thread. If not please start a new one like Scott asked you to do.

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

                              i don´t know what you guys are using when you are testing the dhclient, but issue still exists:

                              Mar 1 17:38:47 dhclient[322]: exiting.
                              Mar 1 17:38:47 dhclient[322]: exiting.
                              Mar 1 17:38:47 dhclient[322]: short write: wanted 21 got 0 bytes
                              Mar 1 17:38:47 dhclient[322]: short write: wanted 21 got 0 bytes
                              Mar 1 17:38:47 dhclient[322]: DHCPACK from 90.224.168.1
                              Mar 1 17:38:47 dhclient[322]: DHCPREQUEST on rl0 to 255.255.255.255 port 67
                              Mar 1 17:36:26 last message repeated 3 times
                              Mar 1 17:32:37 last message repeated 6 times
                              Mar 1 17:30:36 last message repeated 3 times

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

                                We lowered the lease time to 150 and used a dedicated testing box.

                                At this point we cannot reproduce the error.  Reinstall.

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

                                  i have done so 2 times already =)

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

                                    Well sorry, 4 developers where able to reproduce it prior but under no conditions does it break now.

                                    I don't know what to tell you at this point.

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

                                      oh well, i just lay low for a while, and see if others having problems too,

                                      thanks for all your hard work !

                                      1 Reply Last reply Reply Quote 0
                                      • K
                                        Krakke
                                        last edited by

                                        1.0.1-SNAPSHOT-02-21-2007

                                        Uptime 3 days, 16:21

                                        Still running :)

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

                                          @Krakke:

                                          1.0.1-SNAPSHOT-02-21-2007

                                          Uptime 3 days, 16:21

                                          Still running :)

                                          Great!  Please continue to let us know the progress.  We really think its nailed.

                                          1 Reply Last reply Reply Quote 0
                                          • K
                                            Krakke
                                            last edited by

                                            @sullrich:

                                            @Krakke:

                                            1.0.1-SNAPSHOT-02-21-2007

                                            Uptime 3 days, 16:21

                                            Still running :)

                                            Great!  Please continue to let us know the progress.  We really think its nailed.

                                            Still working, updated to 1.0.1-SNAPSHOT-02-27-2007

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