Default Interet connection stops getting DHCP after several days



  • I have an issue where the default internet connection stops getting a DHCP connection after a few days.  No matter if I use WAN, OPT1 or OPT2, my internet connection randomly stops getting a DHCP address after a few days.  I've tried different laptops and different modems, and the issue still persists.  I did not have this issue in 1.2.3.

    I have multiple WAN connections and the only one that stops receiving the DHCP addresses is the default one.  If I switch the default connection to a different interface, it stays up for a while, but eventually that interface will stop renewing it's DHCP address as well.  If I reboot the firewall, everything comes up fine and it's good for another 3-7 days.  It's totally random when it goes down.  PFSense is running on a Lenovo Thinkpad T43 with 3 USB LAN Adapters.  I then switched to a Lenovo Thinkpad T61.  I've tried multiple snapshots and they all have the same issue.  I am currently running 2.0-BETA5 (amd64) built on Sat Jan 29 12:48:57 EST 2011.

    Here is a portion log from the system logs:
    Feb 11 06:52:52 dhclient: FAIL
    Feb 11 06:52:52 dhclient: FAIL
    Feb 11 06:52:52 dhclient[24748]: No working leases in persistent database - sleeping.
    Feb 11 06:52:52 dhclient[33264]: No working leases in persistent database - sleeping.
    Feb 11 06:52:52 dhclient[24748]: No DHCPOFFERS received.
    Feb 11 06:52:52 dhclient[33264]: No DHCPOFFERS received.
    Feb 11 06:52:48 dhclient[24748]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 4
    Feb 11 06:52:47 dhclient[33264]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 5
    Feb 11 06:52:39 dhclient[24748]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 9
    Feb 11 06:52:39 dhclient[33264]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 8
    Feb 11 06:52:32 dhclient[33264]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 7
    Feb 11 06:52:25 dhclient[33264]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 7
    Feb 11 06:52:24 dhclient[24748]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 15
    Feb 11 06:52:12 dhclient[24748]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 12
    Feb 11 06:52:11 dhclient[33264]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 14
    Feb 11 06:52:01 dhclient[24748]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 11
    Feb 11 06:52:01 dhclient[33264]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 10
    Feb 11 06:52:00 kernel: arpresolve: can't allocate llinfo for xxx.xxx.xxx.xxx
    Feb 11 06:51:57 dhclient[24748]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 4
    Feb 11 06:51:56 kernel: arpresolve: can't allocate llinfo for xxx.xxx.xxx.xxx
    Feb 11 06:51:56 dhclient[33264]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 5
    Feb 11 06:51:54 kernel: arpresolve: can't allocate llinfo for xxx.xxx.xxx.xxx
    Feb 11 06:51:54 kernel: arpresolve: can't allocate llinfo for xxx.xxx.xxx.xxx
    Feb 11 06:51:53 dhclient[24748]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 4
    Feb 11 06:51:53 dhclient[33264]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 3
    Feb 11 06:51:52 dhclient[33264]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 2
    Feb 11 06:51:52 dhclient[24748]: send_packet: Network is down
    Feb 11 06:51:52 dhclient[24748]: send_packet: Network is down
    Feb 11 06:51:52 dhclient[24748]: DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 2
    Feb 11 06:51:52 dhclient: PREINIT
    Feb 11 06:51:52 dhclient: PREINIT
    Feb 11 06:51:51 dhclient: Deleting old routes
    Feb 11 06:51:51 dhclient: Deleting old routes
    Feb 11 06:51:51 dhclient: EXPIRE
    Feb 11 06:51:51 dhclient: EXPIRE
    Feb 11 06:50:31 dhclient[24748]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:50:26 dhclient[33264]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:49:03 dhclient[33264]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:48:50 dhclient[24748]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:48:32 dhclient[33264]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:48:18 dhclient[33264]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:48:05 dhclient[24748]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:48:04 dhclient[33264]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:47:49 dhclient[33264]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:47:42 dhclient[24748]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:47:33 dhclient[24748]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:47:26 dhclient[33264]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:47:19 dhclient[24748]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:47:13 dhclient[24748]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:47:12 dhclient[33264]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:47:08 dhclient[24748]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:47:06 dhclient[33264]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:47:03 dhclient[24748]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:47:00 dhclient[33264]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:46:59 dhclient[24748]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:46:55 dhclient[24748]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:46:55 dhclient[33264]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:46:53 dhclient[33264]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:46:52 dhclient[24748]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:46:52 dhclient[33264]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:46:51 dhclient[33264]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:46:50 dhclient[24748]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:46:50 dhclient[33264]: DHCPREQUEST on ue0 to 192.168.100.1 port 67
    Feb 11 06:46:25 check_reload_status: reloading filter
    Feb 11 06:46:25 check_reload_status: reloading filter
    Feb 11 06:46:15 apinger: ALARM: WAN(xxx.xxx.xxx.xxx) *** down ***
    Feb 11 06:46:15 apinger: ALARM: WAN(xxx.xxx.xxx.xxx) *** down ***


Log in to reply