PfSense 2.x and ATT ADSL with short lease



  • Hello, I'm new to the forum but I've been lurking for some time. I'm a relative pfSense novice - I've had a vanilla 1.2.3 supporting a low traffic home network. It's been running 1.2.3 for 4+ years and recently decided I should upgrade and get current. Prior to the upgrade my AT&T ADSL connection ran fine, but post migration I have been unable to maintain a DHCP based WAN connection. 1.2.3 seems to handle the short lease time, but 2.x has struggled. I've maintained my 1.2.3 USB key so I can flip back and forth between 1.x and 2.x while testing. I have also tried out 2.x on two different hosts (I have a spare micro ITX system for debugging) to rule out a hardware issue, though they are the same board so I have not ruled out a compatibility issue (Supermicro X7SPA-H), but 1.2.3 has been running on this board for years. I've tried the following releases, all yielding the same issue:

    • pfSense-LiveCD-2.1.5-RELEASE-amd64-20140825-0744 (both live CD and SSD install)

    • pfSense-2.1.5-RELEASE-4g-i386-nanobsd-vga-20140825-0744

    • pfSense-2.1.5-RELEASE-4g-amd64-nanobsd-vga-20140825-0744

    • pfSense-2.1.4-RELEASE-4g-amd64-nanobsd-vga-20140620-1259

    • pfSense-2.0.3-RELEASE-4g-amd64-nanobsd_vga

    When I run 1.2.3 I see the following log entries:

    Dec 22 18:33:29 dhclient[61152]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 22 18:33:29 dhclient[61152]: SENDING DIRECT
    Dec 22 18:33:29 dhclient[61152]: DHCPACK from 192.168.1.1
    Dec 22 18:33:29 dhclient[61152]: bound to 75.44.28.241 – renewal in 30 seconds.
    Dec 22 18:33:59 dhclient[61152]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 22 18:33:59 dhclient[61152]: SENDING DIRECT
    Dec 22 18:33:59 dhclient[61152]: DHCPACK from 192.168.1.1
    Dec 22 18:33:59 dhclient[61152]: bound to 75.44.28.241 – renewal in 30 seconds.
    Dec 22 18:34:29 dhclient[61152]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 22 18:34:29 dhclient[61152]: SENDING DIRECT
    Dec 22 18:34:29 dhclient[61152]: DHCPACK from 192.168.1.1
    Dec 22 18:34:29 dhclient[61152]: bound to 75.44.28.241 – renewal in 30 seconds.
    Dec 22 18:34:59 dhclient[61152]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 22 18:34:59 dhclient[61152]: SENDING DIRECT
    Dec 22 18:34:59 dhclient[61152]: DHCPACK from 192.168.1.1
    Dec 22 18:34:59 dhclient[61152]: bound to 75.44.28.241 – renewal in 30 seconds.
    Dec 22 18:35:29 dhclient[61152]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 22 18:35:29 dhclient[61152]: SENDING DIRECT
    Dec 22 18:35:29 dhclient[61152]: DHCPACK from 192.168.1.1
    Dec 22 18:35:29 dhclient[61152]: bound to 75.44.28.241 – renewal in 30 seconds.
    Dec 22 18:36:00 dhclient[61152]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 22 18:36:00 dhclient[61152]: SENDING DIRECT
    Dec 22 18:36:00 dhclient[61152]: DHCPACK from 192.168.1.1
    Dec 22 18:36:00 dhclient[61152]: bound to 75.44.28.241 – renewal in 30 seconds.
    Dec 22 18:36:30 dhclient[61152]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 22 18:36:30 dhclient[61152]: SENDING DIRECT
    Dec 22 18:36:30 dhclient[61152]: DHCPACK from 192.168.1.1
    Dec 22 18:36:30 dhclient[61152]: bound to 75.44.28.241 – renewal in 30 seconds.
    Dec 22 18:37:00 dhclient[61152]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 22 18:37:00 dhclient[61152]: SENDING DIRECT
    Dec 22 18:37:00 dhclient[61152]: DHCPACK from 192.168.1.1
    Dec 22 18:37:01 dhclient[61152]: bound to 75.44.28.241 – renewal in 30 seconds.

    But the General log in 2.1.5 captures more entries - the "restarting" and "reloading" messages were what made me focus on the lease times and trying a static IP:

    Dec 24 04:17:45 check_reload_status: rc.newwanip starting em1
    Dec 24 04:17:47 php: rc.newwanip: rc.newwanip: Informational is starting em1.
    Dec 24 04:17:47 php: rc.newwanip: rc.newwanip: on (IP address: 75.44.28.241) (interface: WAN[wan]) (real interface: em1).
    Dec 24 04:17:47 php: rc.newwanip: ROUTING: setting default route to 75.44.28.1
    Dec 24 04:17:52 php: rc.newwanip: Resyncing OpenVPN instances for interface WAN.
    Dec 24 04:17:52 php: rc.newwanip: Creating rrd update script
    Dec 24 04:17:54 php: rc.newwanip: pfSense package system has detected an ip change 75.44.28.241 -> 75.44.28.241 … Restarting packages.
    Dec 24 04:17:54 check_reload_status: Starting packages
    Dec 24 04:17:54 check_reload_status: Reloading filter
    Dec 24 04:17:57 php: rc.start_packages: Restarting/Starting all packages.
    Dec 24 04:21:40 check_reload_status: rc.newwanip starting em1
    Dec 24 04:21:43 php: rc.newwanip: rc.newwanip: Informational is starting em1.
    Dec 24 04:21:43 php: rc.newwanip: rc.newwanip: on (IP address: 75.44.28.241) (interface: WAN[wan]) (real interface: em1).
    Dec 24 04:21:43 php: rc.newwanip: ROUTING: setting default route to 75.44.28.1
    Dec 24 04:21:48 php: rc.newwanip: Resyncing OpenVPN instances for interface WAN.
    Dec 24 04:21:48 php: rc.newwanip: Creating rrd update script
    Dec 24 04:21:50 php: rc.newwanip: pfSense package system has detected an ip change 75.44.28.241 -> 75.44.28.241 … Restarting packages.
    Dec 24 04:21:50 check_reload_status: Starting packages
    Dec 24 04:21:50 check_reload_status: Reloading filter
    Dec 24 04:21:53 php: rc.start_packages: Restarting/Starting all packages.
    Dec 24 04:22:43 check_reload_status: rc.newwanip starting em1
    Dec 24 04:22:45 php: rc.newwanip: rc.newwanip: Informational is starting em1.
    Dec 24 04:22:45 php: rc.newwanip: rc.newwanip: on (IP address: 75.44.28.241) (interface: WAN[wan]) (real interface: em1).
    Dec 24 04:22:45 php: rc.newwanip: ROUTING: setting default route to 75.44.28.1
    Dec 24 04:22:50 php: rc.newwanip: Resyncing OpenVPN instances for interface WAN.
    Dec 24 04:22:50 php: rc.newwanip: Creating rrd update script
    Dec 24 04:22:52 php: rc.newwanip: pfSense package system has detected an ip change 75.44.28.241 -> 75.44.28.241 … Restarting packages.
    Dec 24 04:22:52 check_reload_status: Starting packages
    Dec 24 04:22:52 check_reload_status: Reloading filter
    Dec 24 04:22:55 php: rc.start_packages: Restarting/Starting all packages.
    Dec 24 04:23:46 check_reload_status: rc.newwanip starting em1
    Dec 24 04:23:49 php: rc.newwanip: rc.newwanip: Informational is starting em1.
    Dec 24 04:23:49 php: rc.newwanip: rc.newwanip: on (IP address: 75.44.28.241) (interface: WAN[wan]) (real interface: em1).
    Dec 24 04:23:49 php: rc.newwanip: ROUTING: setting default route to 75.44.28.1
    Dec 24 04:23:54 php: rc.newwanip: Resyncing OpenVPN instances for interface WAN.
    Dec 24 04:23:54 php: rc.newwanip: Creating rrd update script
    Dec 24 04:23:56 php: rc.newwanip: pfSense package system has detected an ip change 75.44.28.241 -> 75.44.28.241 … Restarting packages.
    Dec 24 04:23:56 check_reload_status: Starting packages
    Dec 24 04:23:56 check_reload_status: Reloading filter
    Dec 24 04:23:58 php: rc.start_packages: Restarting/Starting all packages.
    Dec 24 04:28:34 check_reload_status: rc.newwanip starting em1
    Dec 24 04:28:37 php: rc.newwanip: rc.newwanip: Informational is starting em1.
    Dec 24 04:28:37 php: rc.newwanip: rc.newwanip: on (IP address: 75.44.28.241) (interface: WAN[wan]) (real interface: em1).
    Dec 24 04:28:37 php: rc.newwanip: ROUTING: setting default route to 75.44.28.1
    Dec 24 04:28:42 php: rc.newwanip: Resyncing OpenVPN instances for interface WAN.
    Dec 24 04:28:42 php: rc.newwanip: Creating rrd update script
    Dec 24 04:28:44 php: rc.newwanip: pfSense package system has detected an ip change 75.44.28.241 -> 75.44.28.241 … Restarting packages.
    Dec 24 04:28:44 check_reload_status: Starting packages
    Dec 24 04:28:44 check_reload_status: Reloading filter
    Dec 24 04:28:47 php: rc.start_packages: Restarting/Starting all packages.

    The chatter in the DHCP logs:

    Dec 24 04:23:46 dhclient: Creating resolv.conf
    Dec 24 04:23:46 dhclient[88203]: bound to 75.44.28.241 – renewal in 30 seconds.
    Dec 24 04:24:16 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:24:18 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:24:22 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:24:26 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:24:30 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:24:39 dhclient[88203]: DHCPREQUEST on em1 to 255.255.255.255 port 67
    Dec 24 04:24:39 dhclient[88203]: DHCPACK from 192.168.1.1
    Dec 24 04:24:39 dhclient: RENEW
    Dec 24 04:24:39 dhclient: Creating resolv.conf
    Dec 24 04:24:39 dhclient[88203]: bound to 75.44.28.241 – renewal in 30 seconds.
    Dec 24 04:24:59 dhcpd: DHCPREQUEST for 10.12.4.93 from 50:e5:49:e7:d2:5d (FELIX) via em0
    Dec 24 04:24:59 dhcpd: DHCPACK on 10.12.4.93 to 50:e5:49:e7:d2:5d (FELIX) via em0
    Dec 24 04:25:09 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:25:11 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:25:14 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:25:20 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:25:29 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:25:38 dhclient[88203]: DHCPREQUEST on em1 to 255.255.255.255 port 67
    Dec 24 04:25:38 dhclient[88203]: DHCPACK from 192.168.1.1
    Dec 24 04:25:38 dhclient: RENEW
    Dec 24 04:25:38 dhclient: Creating resolv.conf
    Dec 24 04:25:38 dhclient[88203]: bound to 75.44.28.241 – renewal in 30 seconds.
    Dec 24 04:26:08 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:26:09 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:26:10 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:26:11 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:26:13 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:26:15 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:26:20 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:26:26 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:26:34 dhclient[88203]: DHCPREQUEST on em1 to 255.255.255.255 port 67
    Dec 24 04:26:34 dhclient[88203]: DHCPACK from 192.168.1.1
    Dec 24 04:26:34 dhclient: RENEW
    Dec 24 04:26:34 dhclient: Creating resolv.conf
    Dec 24 04:26:34 dhclient[88203]: bound to 75.44.28.241 – renewal in 30 seconds.
    Dec 24 04:27:04 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:27:05 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:27:06 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:27:07 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:27:09 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:27:12 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:27:15 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:27:24 dhclient[88203]: DHCPREQUEST on em1 to 192.168.1.1 port 67
    Dec 24 04:27:31 dhclient[88203]: DHCPREQUEST on em1 to 255.255.255.255 port 67
    Dec 24 04:27:31 dhclient[88203]: DHCPACK from 192.168.1.1
    Dec 24 04:27:31 dhclient: RENEW
    Dec 24 04:27:31 dhclient: Creating resolv.conf
    Dec 24 04:27:31 dhclient[88203]: bound to 75.44.28.241 – renewal in 30 seconds.

    If I take the DHCP address (75.44.28.241 / 24 in this case) and the gateway (75.44.28.1 in this case) and set the WAN to static then the connection runs fine until I get out of sync when the modem pulls a new address. I've been trying to avoid moving my modem from bridge mode to NAT which would stabilize the crazy short lease, but force me to use a private address on the WAN. I did find this forum post which seemed to describe my problem as well (though I am not using Uverse):
    https://forum.pfsense.org/index.php?topic=42777.0

    Hardware:

    Supermicro X7SPA-H
    http://www.supermicro.com/products/motherboard/ATOM/ICH9/X7SPA.cfm?typ=H
    Intel(R) Atom(TM) CPU D510 @ 1.66GHz
    4 CPUs: 1 package(s) x 2 core(s) x 2 HTT threads
    2x Intel 82574L Gigabit Ethernet
    Supports 10BASE-T, 100/1000BASE-TX, RJ45 output
    4 GB RAM
    4 GB USB key, 120 GB SSD used as storage

    Dlink DSL-2320B in bridge mode

    I hope I'm just missing something silly, but I've been poking on this for a week and I'm at wits end … hopefully someone with more experience has some advice for me :)



  • I purchased a TP-Link TD-8616 ADSL2+ Modem and setup my WAN with PPPoE instead of DHCP through the bridged modem. This seems to be working find, so it looks like I'll retire the Dlink DSL-2320B and call it done.


Log in to reply