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

    WAN DHCP up and down

    Scheduled Pinned Locked Moved DHCP and DNS
    2 Posts 1 Posters 1.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.
    • B
      boatman
      last edited by

      I am running pfsense version: 2.3.1-RELEASE-p1 and I've starting experiencing a bizarre issue with DHCP on the WAN interface. I will have internet connection for about an hour and then the pfsense box will not be able to get a DHCP lease for about an hour (if I don't touch anything). So my connection has been going up and down for the last 2 days.

      The modem I have from my ISP is a 2Wire modem/router and I have it setup to have the pfsense box in a DMZ zone and the WAN port gets assigned a public IP. If I connect another computer to the modem, it has internet connectivity. And if I power cycling the modem, the WAN port on pfsense box will get assigned an IP by the modem and work for an hour.

      When the WAN interface loses it's DHCP address, I see the following (the modem's internal IP is 192.168.100.254):

      Jun 1 22:17:55 dhclient 31533 DHCPREQUEST on igb0 to 192.168.100.254 port 67
      Jun 1 22:19:39 dhclient EXPIRE
      Jun 1 22:19:39 dhclient Deleting old routes
      Jun 1 22:19:39 dhclient PREINIT
      Jun 1 22:19:39 dhclient 31533 DHCPDISCOVER on igb0 to 255.255.255.255 port 67 interval 22
      Jun 1 22:19:39 dhclient 31533 DHCPOFFER from 192.168.100.254
      Jun 1 22:19:39 dhclient ARPSEND
      Jun 1 22:19:41 dhclient ARPCHECK
      Jun 1 22:19:41 dhclient 31533 DHCPREQUEST on igb0 to 255.255.255.255 port 67
      Jun 1 22:20:07 dhclient 31533 DHCPDISCOVER on igb0 to 255.255.255.255 port 67 interval 17
      Jun 1 22:20:07 dhclient 31533 DHCPOFFER from 192.168.100.254
      Jun 1 22:20:07 dhclient ARPSEND
      Jun 1 22:20:09 dhclient ARPCHECK
      Jun 1 22:20:09 dhclient 31533 DHCPREQUEST on igb0 to 255.255.255.255 port 67

      After about an hour of trying to obtain an IP, the WAN interface finally gets one (I've removed the public IPs):

      Jun 1 22:58:34 dhclient 16726 DHCPREQUEST on igb0 to 255.255.255.255 port 67
      Jun 1 22:58:35 dhclient 16726 DHCPREQUEST on igb0 to 255.255.255.255 port 67
      Jun 1 22:58:36 dhclient 16726 DHCPREQUEST on igb0 to 255.255.255.255 port 67
      Jun 1 22:58:37 dhclient 16726 DHCPREQUEST on igb0 to 255.255.255.255 port 67
      Jun 1 22:58:39 dhclient 16726 DHCPREQUEST on igb0 to 255.255.255.255 port 67
      Jun 1 22:58:41 dhclient 16726 DHCPREQUEST on igb0 to 255.255.255.255 port 67
      Jun 1 22:58:41 dhclient 16726 DHCPACK from XXX.XXX.XX.X
      Jun 1 22:58:41 dhclient BOUND
      Jun 1 22:58:41 dhclient Starting add_new_address()
      Jun 1 22:58:41 dhclient ifconfig igb0 inet XXX.XXX.XX.XXX netmask 255.255.252.0 broadcast XXX.XXX.XX.255
      Jun 1 22:58:41 dhclient New IP Address (igb0): XXX.XXX.XX.XXX
      Jun 1 22:58:41 dhclient New Subnet Mask (igb0): 255.255.252.0
      Jun 1 22:58:41 dhclient New Broadcast Address (igb0): XXX.XXX.XX.255
      Jun 1 22:58:41 dhclient New Routers (igb0): XXX.XXX.XX.X
      Jun 1 22:58:41 dhclient Adding new routes to interface: igb0
      Jun 1 22:58:41 dhclient /sbin/route add default XXX.XXX.XX.X
      Jun 1 22:58:41 dhclient Creating resolv.conf
      Jun 1 22:58:41 dhclient 16726 bound to XXX.XXX.XX.XX – renewal in 300 seconds
      Jun 1 23:03:41 dhclient 29330 DHCPREQUEST on igb0 to 192.168.100.254 port 67
      Jun 1 23:03:41 dhclient 29330 DHCPACK from XXX.XXX.XX.X
      Jun 1 23:03:41 dhclient RENEW
      Jun 1 23:03:41 dhclient Creating resolv.conf
      Jun 1 23:03:41 dhclient 29330 bound to XXX.XXX.XX.XXX -- renewal in 300 seconds.
      Jun 1 23:08:41 dhclient 29330 DHCPREQUEST on igb0 to 192.168.100.254 port 67
      Jun 1 23:08:41 dhclient 29330 DHCPACK from XXX.XXX.XX.X
      Jun 1 23:08:41 dhclient RENEW
      Jun 1 23:08:41 dhclient Creating resolv.conf
      Jun 1 23:08:41 dhclient 29330 bound to XXX.XXX.XX.XXX -- renewal in 300 seconds.
      Jun 1 23:13:41 dhclient 29330 DHCPREQUEST on igb0 to 192.168.100.254 port 67
      Jun 1 23:13:41 dhclient 29330 DHCPACK from XXX.XXX.XX.X
      Jun 1 23:13:41 dhclient RENEW
      Jun 1 23:13:41 dhclient Creating resolv.conf
      Jun 1 23:13:41 dhclient 29330 bound to XXX.XXX.XX.XXX -- renewal in 300 seconds.
      Jun 1 23:18:42 dhclient 29330 DHCPREQUEST on igb0 to 192.168.100.254 port 67
      Jun 1 23:18:42 dhclient 29330 DHCPACK from XXX.XXX.XX.X
      Jun 1 23:18:42 dhclient RENEW
      Jun 1 23:18:42 dhclient Creating resolv.conf
      Jun 1 23:18:42 dhclient 29330 bound to XXX.XXX.XX.XXX -- renewal in 300 seconds.

      And the cycle repeats itself.

      Can anyone help troubleshoot this further? I'm not sure if this is an issue with the pfsense box, or my ISP?

      Thanks.

      1 Reply Last reply Reply Quote 0
      • B
        boatman
        last edited by

        So I took the pfsense box out of the DMZ zone on the 2Wire router/modem. So now the pfsense WAN interface has a private IP of 192.168.100.254. The WAN interface has remained up so far.

        In addition, I plugged a router's WAN interface into the the 2Wire router/modem and put that into the DMZ zone on the 2Wire. The router was given the public IP from my ISP. After an hour, the WAN connection on the router is down and no longer has an IP.

        So, I think the issue is on my ISP's end.

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