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

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

DHCP and DNS
27
199
112.3k
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
    Selective
    last edited by Feb 26, 2007, 7:32 PM

    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 Feb 26, 2007, 8:13 PM

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

      1 Reply Last reply Reply Quote 0
      • T
        ThomasF
        last edited by Mar 8, 2007, 5:25 PM Feb 27, 2007, 8:57 AM

        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 Feb 27, 2007, 3:34 PM

          @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 Feb 27, 2007, 4:22 PM

            @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 Mar 1, 2007, 5:59 PM

              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 Mar 1, 2007, 6:14 PM

                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 Mar 1, 2007, 10:03 PM

                  i have done so 2 times already =)

                  1 Reply Last reply Reply Quote 0
                  • S
                    sullrich
                    last edited by Mar 1, 2007, 10:04 PM

                    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 Mar 1, 2007, 10:22 PM

                      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 Mar 2, 2007, 4:01 PM

                        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 Mar 2, 2007, 5:46 PM

                          @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 Mar 4, 2007, 2:29 PM

                            @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
                            • T
                              ThomasF
                              last edited by Mar 8, 2007, 9:23 PM

                              It seems to be working just fine now, thanks!

                              1 Reply Last reply Reply Quote 0
                              • F
                                freax
                                last edited by Mar 9, 2007, 6:17 PM

                                I've done a clean install with the latest official update from 08/03/2007 but my logs registeres the following rc.linkup message:

                                Last 50 system log entries
                                Mar 9 18:13:30 php: : Incorrect number of arguments passed rc.linkup…exiting.
                                Mar 9 18:13:30 php: : Arguments passed rc.linkup. ''
                                Mar 9 18:13:28 check_reload_status: rc.linkup starting
                                Mar 9 18:13:23 php: : phpDynDNS: No Change In My IP Address and/or 25 Days Has Not Past. Not Updating Dynamic DNS Entry.

                                It's normal ?

                                []'s

                                1 Reply Last reply Reply Quote 0
                                • S
                                  sullrich
                                  last edited by Mar 9, 2007, 6:29 PM

                                  Yes, those are debugging statements and looks fine.

                                  1 Reply Last reply Reply Quote 0
                                  • K
                                    Krakke
                                    last edited by Mar 12, 2007, 7:32 AM

                                    1.0.1-SNAPSHOT-02-27-2007
                                    Uptime 7 days, 16:51

                                    Still running, updating to pfSense-Full-Update-1.0.1-SNAPSHOT-03-08-2007

                                    1 Reply Last reply Reply Quote 0
                                    • S
                                      sullrich
                                      last edited by Mar 12, 2007, 6:37 PM

                                      @Krakke:

                                      1.0.1-SNAPSHOT-02-27-2007
                                      Uptime 7 days, 16:51

                                      Still running, updating to pfSense-Full-Update-1.0.1-SNAPSHOT-03-08-2007

                                      Great!  Thanks for the update.

                                      1 Reply Last reply Reply Quote 0
                                      • V
                                        Veni
                                        last edited by Mar 13, 2007, 1:27 PM

                                        Don't know if this is the same issue, but i noticed this yesterday.
                                        Running 1.0.1-SNAPSHOT-03-18-2007 built on Thu Mar 8 22:14:44 EST 2007.

                                        For some unknown reason, my pfSense box lost it's WAN dhcp ipaddress, but my
                                        WatchGuard box connected to the same ISP outlet(i use a switch to get several ports)
                                        did not have any problems recorded, and it to runs on a WAN dhcp. The WatchGuard box
                                        uses something called udhcpc. I don't know if it's better, worse or the same as dhclient.

                                        Pressing the Renew button in Status–>Interfaces had no problem of getting a ipaddress.
                                        I pressed the button around 20:15.

                                        Got this from the syslog(if was not at home when this happened):

                                        | Mar 12 17:35:24 dhclient[261]: DHCPREQUEST on xl1 to 81.228.3.186 port 67                                                                                                                                    |
                                        | Mar 12 17:41:13 last message repeated 3 times                                                                                                                                                                |
                                        | Mar 12 17:44:02 dhclient[261]: DHCPDISCOVER on xl1 to 255.255.255.255 port 67 interval 6                                                                                                                    |
                                        | Mar 12 17:44:02 dhclient[261]: DHCPOFFER from 81.236.128.1                                                                                                                                                  |
                                        | Mar 12 17:44:04 dhclient[261]: DHCPREQUEST on xl1 to 255.255.255.255 port 67                                                                                                                                |
                                        | Mar 12 17:44:04 dhclient[261]: DHCPACK from 81.236.128.1                                                                                                                                                    |
                                        | Mar 12 17:44:04 dhclient[261]: bound to 81.236.134.30 – renewal in 600 seconds.                                                                                                                            |
                                        | Mar 12 17:44:34 SnortStartup[55432]: Ram free BEFORE starting Snort: 108M – Ram free AFTER starting Snort: 107M -- Mode ac-sparsebands -- Snort memory usage:                                              |
                                        | Mar 12 17:44:51 SnortStartup[55465]: Ram free BEFORE starting Snort: 107M – Ram free AFTER starting Snort: 108M -- Mode ac-sparsebands -- Snort memory usage:                                              |
                                        | Mar 12 17:54:04 dhclient[261]: DHCPREQUEST on xl1 to 81.228.3.186 port 67                                                                                                                                    |
                                        | Mar 12 17:54:43 last message repeated 3 times                                                                                                                                                                |
                                        | Mar 12 17:56:45 last message repeated 7 times                                                                                                                                                                |
                                        | Mar 12 18:00:44 last message repeated 9 times                                                                                                                                                                |
                                        | Mar 12 18:01:39 dnsmasq[572]: reading /etc/resolv.conf                                                                                                                                                      |
                                        | Mar 12 18:01:39 dnsmasq[572]: using nameserver 195.67.199.41#53                                                                                                                                              |
                                        | Mar 12 18:01:39 dnsmasq[572]: using nameserver 195.67.199.40#53                                                                                                                                              |
                                        | Mar 12 18:01:39 dnsmasq[572]: using nameserver 195.67.199.39#53                                                                                                                                              |
                                        | Mar 12 18:02:17 dhclient[261]: DHCPREQUEST on xl1 to 255.255.255.255 port 67                                                                                                                                |
                                        | Mar 12 18:02:17 dhclient[261]: DHCPACK from 81.236.128.1                                                                                                                                                    |
                                        | Mar 12 18:02:17 dhclient[261]: short write: wanted 21 got 0 bytes                                                                                                                                            |
                                        | Mar 12 18:02:17 dhclient[261]: exiting.                                                                                                                                                                      |

                                        | Mar 12 20:13:17 login: login on ttyv0 as root                                                                                                                                                                |
                                        | Mar 12 20:15:57 dhclient[81132]: DHCPDISCOVER on xl1 to 255.255.255.255 port 67 interval 5                                                                                                                  |
                                        | Mar 12 20:16:02 dhclient[81132]: DHCPDISCOVER on xl1 to 255.255.255.255 port 67 interval 6                                                                                                                  |
                                        | Mar 12 20:16:08 dhclient[81132]: DHCPDISCOVER on xl1 to 255.255.255.255 port 67 interval 7                                                                                                                  |
                                        | Mar 12 20:16:08 dhclient[81132]: DHCPOFFER from 81.236.128.1                                                                                                                                                |
                                        | Mar 12 20:16:10 dhclient[81132]: DHCPREQUEST on xl1 to 255.255.255.255 port 67                                                                                                                              |
                                        | Mar 12 20:16:10 dhclient[81132]: DHCPACK from 81.236.128.1                                                                                                                                                  |
                                        | Mar 12 20:16:10 dhclient[81132]: bound to 81.236.134.30 – renewal in 600 seconds.                                                                                                                          |

                                        1 Reply Last reply Reply Quote 0
                                        • S
                                          sullrich
                                          last edited by Mar 13, 2007, 7:53 PM

                                          Remove snort and see if the problem persists.

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