WAN side auto renew IP address



  • Hi guys!  How do I perform auto renew of my WAN IP?

    I am asking because a few weeks ago, I noticed a strange behavior: Suddenly my internet connection goes down for no reasons and having a very stable cable connection, I doubted the ISP was faulty.

    I finally found that for some reasons pfsense dropped or lost the IP from the ISP and to fix this issue I only had to do a "release" and then "renew" of the IP of my WAN connection and all was fine.

    This happened again today.  It seems to be every week or so…  SO maybe this is not a good solution, but how do I implement a auto renew feature to automatically renew my IP ?

    Calling the networking experts here, maybe this is not the way to go.. It might be symptom of a deeper problem?

    thanks!



  • If I recall correctly, some people have reported that in pfSense 1.2.3 dhclient (the dhcp client program which manages configuration by dhcp)  dies and doesn't restart. I suggest you look in the system logs for signs of dhclient dying and check that it is still running (pfSense shell command # ps ax | grep dhclient).

    On my system I see```

    ps ax | grep dhclient

    62355  ??  IN    0:00.00 dhclient: udav0 [priv] (dhclient)
    62406  ??  INs    0:00.00 dhclient: udav0 (dhclient)
    9976  p0  R+    0:00.01 grep dhclient

    
    (udav0 is the only interface on my system which gets its IP address from DHCP.)
    
    If dhclient dies there is nothing to request renewal of the IP address when the previous lease expires.


  • This is what I see when issuing the command :

    $ ps ax | grep dhclient
    13441  ??  I      0:00.00 dhclient: fxp0 [priv] (dhclient)
    13492  ??  Is    0:00.17 dhclient: fxp0 (dhclient)
    14346  ??  S     0:00.00 sh -c ps ax | grep dhclient
    14348  ??  S     0:00.00 grep dhclient
    
    

    how do you interpret this??



  • @lpallard:

    how do you interpret this??

    dhclient is running when you issue the command (but is fxp0 your WAN interface?).

    Of more interest would be whether it is running on your WAN interface when your pfSense fails to renew its WAN IP address.



  • Yes fxp0 is my WAN interface.  I agree, lets see what happens when it dies again… I guess I will repost when that happens. Probably in a few days...



  • When its lease renewal time it would also be worth looking for dhclient messages or any other seemingly related notifications in your system log  ( Status -> System Logs, System tab).



  • FYI this has been happening to me also.  It appears you are correct… the dhclient is dying.

    [2.0-BETA5][admin@pfsense.frostweb]/root(1): ps ax | grep dhclient
    [2.0-BETA5][admin@pfsense.frostweb]/root(2): ps | grep dhclient
    [2.0-BETA5][admin@pfsense.frostweb]/root(3): ps
      PID  TT  STAT      TIME COMMAND
    17750  v0- S      3:46.97 /usr/sbin/tcpdump -s 256 -v -l -n -e -ttt -i pflog0
    18079  v0- S      4:27.91 logger -t pf -p local0.info
    38127  v0  Is     0:00.03 login [pam] (login)
    44869  v0  I      0:00.01 -sh (sh)
    46642  v0  I+     0:00.01 /bin/sh /etc/rc.initial
    63666  v0- SN     9:45.20 /bin/sh /var/db/rrd/updaterrd.sh
      214   0  R      0:00.04 /bin/tcsh
     1743   0  R+     0:00.00 ps
    53250   0  Is     0:00.02 /bin/sh /etc/rc.initial
    
    

    and….

    Last 50 system log entries
    Jan 17 21:16:13	dhclient[49939]: exiting.
    Jan 17 21:16:13	dhclient[49939]: exiting.
    Jan 17 21:16:14	dhclient: PREINIT
    Jan 17 21:16:14	dhclient[54245]: DHCPREQUEST on xl0 to 255.255.255.255 port 67
    Jan 17 21:16:14	dhclient[54245]: DHCPNAK from 192.168.100.1
    Jan 17 21:16:14	dhclient[54245]: DHCPDISCOVER on xl0 to 255.255.255.255 port 67 interval 1
    Jan 17 21:16:14	dhclient[54245]: DHCPOFFER from 192.168.100.1
    Jan 17 21:16:14	dhclient: ARPSEND
    Jan 17 21:16:16	dhclient: ARPCHECK
    Jan 17 21:16:16	dhclient[54245]: DHCPREQUEST on xl0 to 255.255.255.255 port 67
    Jan 17 21:16:16	dhclient[54245]: DHCPACK from 192.168.100.1
    Jan 17 21:16:16	dhclient: BOUND
    Jan 17 21:16:16	dhclient: Starting add_new_address()
    Jan 17 21:16:16	dhclient: ifconfig xl0 inet 192.168.100.10 netmask 255.255.255.0 broadcast 192.168.100.255
    Jan 17 21:16:16	dhclient: New IP Address (xl0): 192.168.100.10
    Jan 17 21:16:16	dhclient: New Subnet Mask (xl0): 255.255.255.0
    Jan 17 21:16:16	dhclient: New Broadcast Address (xl0): 192.168.100.255
    Jan 17 21:16:16	dhclient: New Routers (xl0):
    Jan 17 21:16:16	dhclient: Adding new routes to interface: xl0
    Jan 17 21:16:16	dhclient: Creating resolv.conf
    Jan 17 21:16:16	check_reload_status: rc.newwanip starting xl0
    Jan 17 21:16:16	dhclient[54245]: bound to 192.168.100.10 -- renewal in 30 seconds.
    Jan 17 21:16:17	php: : rc.newwanip: Informational is starting xl0.
    Jan 17 21:16:17	php: : rc.newwanip: on (IP address: 192.168.100.10) (interface: wan) (real interface: xl0).
    Jan 17 21:16:17	apinger: Exiting on signal 15.
    Jan 17 21:16:18	check_reload_status: reloading filter
    Jan 17 21:16:18	apinger: Starting Alarm Pinger, apinger(2241)
    Jan 17 21:16:18	php: : DynDns: Running updatedns()
    Jan 17 21:16:18	apinger: No usable targets found, exiting
    Jan 17 21:16:18	php: : DynDns: updatedns() starting
    Jan 17 21:16:18	php: : DynDns: _detectChange() starting.
    Jan 17 21:16:18	php: : DynDns: _checkIP() starting.
    Jan 17 21:16:19	php: : Dyndns debug information: Could not resolve checkip.dyndns.org to ip using interface ip 192.168.100.10.
    Jan 17 21:16:19	php: : DynDns: Current WAN IP: 192.168.100.10
    Jan 17 21:16:19	php: : DynDns: Cached IP: [lies]
    Jan 17 21:16:19	php: : DynDns debug information: DynDns: cacheIP != wan_ip. Updating. Cached IP: [LIES] WAN IP: 192.168.100.10
    Jan 17 21:16:19	php: : DynDns: DynDns _update() starting.
    Jan 17 21:16:19	php: : Curl error occurred: Couldn't resolve host 'members.dyndns.org'
    Jan 17 21:16:19	php: : DynDns: DynDns _checkStatus() starting.
    Jan 17 21:16:19	php: : DynDns: Current Service: dyndns-custom
    Jan 17 21:16:19	php: : phpDynDNS: PAYLOAD:
    Jan 17 21:16:19	php: : phpDynDNS: (Unknown Response)
    Jan 17 21:16:19	dnsmasq[46051]: reading /etc/resolv.conf
    Jan 17 21:16:19	dnsmasq[46051]: using nameserver 8.8.4.4#53
    Jan 17 21:16:19	dnsmasq[46051]: using nameserver 8.8.8.8#53
    Jan 17 21:16:19	dnsmasq[46051]: using nameserver 131.193.68.142#53
    Jan 17 21:16:19	dnsmasq[46051]: using nameserver 131.193.68.141#53
    Jan 17 21:16:20	php: : Could not find gateway for interface(wan).
    Jan 17 21:16:20	php: : Could not find gateway for interface(wan).
    Jan 17 21:16:25	php: : Resyncing OpenVPN instances for interface WAN.
    

    Any ideas for a fix?

    I can try upgrading if you think it will help.
    Current version: 2.0-BETA5
          Built On: Wed Dec 29 05:36:23 EST 2010
        New version: Sun Jan 16 22:00:36 EST 2011

    This is running off of a Motorola docsis 3.0 - 70Mbit connection to comcast.



  • From observation I would guess that dhclient is supposed to exit when the interface goes down (e.g. carrier lost because cable is removed) and get restarted by something when the interface comes up again (e.g. cable restored). On a couple of different software system it seems the restart of dhclient doesn't happen reliably.

    But that doesn't seem to be what is happening here. From the log:

    Jan 17 21:16:13 dhclient[49939]: exiting.
    Jan 17 21:16:14 dhclient: PREINIT
    Jan 17 21:16:14 dhclient[54245]: DHCPREQUEST on xl0 to 255.255.255.255 port 67

    dhclient starts with a new process id.

    I think the real problem is seen further down in the log:

    Jan 17 21:16:19 dnsmasq[46051]: using nameserver 131.193.68.141#53
    Jan 17 21:16:20 php: : Could not find gateway for interface(wan).

    It looks to me as if your system has been left without a default route hence it doesn't (generally) know where to send packets with public IP addresses as the destination.
    Check:  post the output of the shell command netstat -rn

    I had this happen to me after an upgrade from pfSense 1.2.3 to 2.0 BETA something. Have you upgraded recently or added new interfaces recently or enabled VPNs recently?

    Take a look at http://forum.pfsense.org/index.php/topic,27636.0.html Do you get a similar gateway display?



  • @wallabybob:

    From observation I would guess that dhclient is supposed to exit when the interface goes down (e.g. carrier lost because cable is removed) and get restarted by something when the interface comes up again (e.g. cable restored). On a couple of different software system it seems the restart of dhclient doesn't happen reliably.

    But that doesn't seem to be what is happening here. From the log:

    Jan 17 21:16:13 dhclient[49939]: exiting.
    Jan 17 21:16:14 dhclient: PREINIT
    Jan 17 21:16:14 dhclient[54245]: DHCPREQUEST on xl0 to 255.255.255.255 port 67

    dhclient starts with a new process id.

    I think the real problem is seen further down in the log:

    Jan 17 21:16:19 dnsmasq[46051]: using nameserver 131.193.68.141#53
    Jan 17 21:16:20 php: : Could not find gateway for interface(wan).

    It looks to me as if your system has been left without a default route hence it doesn't (generally) know where to send packets with public IP addresses as the destination.
    Check:  post the output of the shell command netstat -rn

    I had this happen to me after an upgrade from pfSense 1.2.3 to 2.0 BETA something. Have you upgraded recently or added new interfaces recently or enabled VPNs recently?

    Take a look at http://forum.pfsense.org/index.php/topic,27636.0.html Do you get a similar gateway display?

    I am showing one entry and it is marked as default in the routing -> gateway tab:

    Name	Interface	Gateway	Monitor IP	Description	
    
    WAN (default)	 WAN	 [i][dhcp external gateway][/i]	 [i][dhcp external gateway][/i]	 Interface WAN Dynamic Gateway 
    

    It is the only one there and was marked as default.  I tried to un-mark it, and save so I could re-mark it, but it remained checked (probably because its the only one).

    [2.0-BETA5][admin@pfsense.frostweb]/root(2): netstat -rn
    Routing tables
    
    Internet:
    Destination        Gateway            Flags    Refs      Use  Netif Expire
    default            [i][dhcp external gateway][/i]        UGS         0  2687994    xl0
    [i][dhcp external gateway][/i].0/23     link#1             U           0    68647    xl0
    [my_ip]      link#1             UHS         0        0    lo0
    75.75.75.75        00:60:08:05:47:bc  UHS         0        0    xl0
    75.75.76.76        00:60:08:05:47:bc  UHS         0        0    xl0
    127.0.0.1          link#5             UH          0      281    lo0
    192.168.1.0/24     link#2             U           0 148305636    xl1
    192.168.1.1        link#2             UHS         0        0    lo0
    
    Internet6:
    Destination                       Gateway                       Flags      Netif Expire
    ::1                               ::1                           UH          lo0
    fe80::%xl0/64                     link#1                        U           xl0
    fe80::260:8ff:fe05:47bc%xl0       link#1                        UHS         lo0
    fe80::%xl1/64                     link#2                        U           xl1
    fe80::260:97ff:fe58:e9ca%xl1      link#2                        UHS         lo0
    fe80::%lo0/64                     link#5                        U           lo0
    fe80::1%lo0                       link#5                        UHS         lo0
    ff01:1::/32                       fe80::260:8ff:fe05:47bc%xl0   U           xl0
    ff01:2::/32                       fe80::260:97ff:fe58:e9ca%xl1  U           xl1
    ff01:5::/32                       ::1                           U           lo0
    ff02::%xl0/32                     fe80::260:8ff:fe05:47bc%xl0   U           xl0
    ff02::%xl1/32                     fe80::260:97ff:fe58:e9ca%xl1  U           xl1
    ff02::%lo0/32                     ::1                           U           lo0
    
    

    I did a fresh install to 2.0b after running into some strange connection drop issues that I thought were with 1.2.3 (wound up being the cable to the house) and re-entered any pertinent entries… but maybe it was during the time that these problems were occurring in the builds.  This specific error might have been my roommate trying to reset the modem (they never listen!  :-\ ).  It is unclear from the other post, but was his fix to simply set the proper default and then the problem did not reappear?  If I run into the issue again, would you recommend creating a bogus gateway, setting it as the default, and then switching back?

    Thanks for your help!

    EDIT:  I also noticed when checking the system log today... there are a large amount of these entries:
    dnsmasq[46051]: possible DNS-rebind attack detected: nsm-2-bgrc.farm.cc.uic.edu

    I'm using the UIC DNS servers.  I'm not sure if these are related.

    Also, I have not enabled any VPNs recently, however my roommate sends quite a bit of traffic into one of our servers via VNC / ARD.



  • @fostytou:

    I did a fresh install to 2.0b after running into some strange connection drop issues that I thought were with 1.2.3 (wound up being the cable to the house) and re-entered any pertinent entries… but maybe it was during the time that these problems were occurring in the builds.  This specific error might have been my roommate trying to reset the modem (they never listen!  :-\ ).  It is unclear from the other post, but was his fix to simply set the proper default and then the problem did not reappear?  If I run into the issue again, would you recommend creating a bogus gateway, setting it as the default, and then switching back?

    You have a default route set so what you are seeing is different from the problem in the linked thread so that suggestion doesn't seem to apply.
    Here's what the log on my pfSense 2.0 BETA looks like after I removed the WAN cable and restored it.

    Jan 19 09:22:43 dhclient[5411]: bound to 192.168.211.217 – renewal in 3600 seconds.
    Jan 19 09:29:38 check_reload_status: Linkup starting vr0
    Jan 19 09:29:38 kernel: vr0: link state changed to DOWN
    Jan 19 09:29:39 php: : DEVD Ethernet detached event for wan
    Jan 19 09:29:39 dhclient[43895]: connection closed
    Jan 19 09:29:39 dhclient[43895]: connection closed
    Jan 19 09:29:39 dhclient[43895]: exiting.
    Jan 19 09:29:39 dhclient[43895]: exiting.
    Jan 19 09:29:46 check_reload_status: Linkup starting vr0
    Jan 19 09:29:46 kernel: vr0: link state changed to UP
    Jan 19 09:29:47 php: : DEVD Ethernet attached event for wan
    Jan 19 09:29:47 php: : HOTPLUG: Configuring interface wan
    Jan 19 09:29:48 apinger: ALARM: GW_WAN(192.168.211.173) *** down ***
    Jan 19 09:29:49 dhclient: PREINIT
    Jan 19 09:29:49 dhclient[5371]: DHCPREQUEST on vr0 to 255.255.255.255 port 67
    Jan 19 09:29:49 dhclient[5371]: DHCPACK from 192.168.211.173
    Jan 19 09:29:49 dhclient: REBOOT
    Jan 19 09:29:49 dhclient: Starting add_new_address()
    Jan 19 09:29:49 dhclient: ifconfig vr0 inet 192.168.211.217 netmask 255.255.255.128 broadcast 192.168.211.255
    Jan 19 09:29:49 dhclient: New IP Address (vr0): 192.168.211.217
    Jan 19 09:29:49 dhclient: New Subnet Mask (vr0): 255.255.255.128
    Jan 19 09:29:49 dhclient: New Broadcast Address (vr0): 192.168.211.255
    Jan 19 09:29:49 dhclient: New Routers (vr0): 192.168.211.173
    Jan 19 09:29:49 dhclient: Adding new routes to interface: vr0
    Jan 19 09:29:49 dhclient: /sbin/route add default 192.168.211.173
    Jan 19 09:29:49 dhclient: Creating resolv.conf
    Jan 19 09:29:50 check_reload_status: rc.newwanip starting vr0
    Jan 19 09:29:50 apinger: alarm canceled: GW_WAN(192.168.211.173) *** down ***
    Jan 19 09:29:50 dhclient[5371]: bound to 192.168.211.217 – renewal in 3600 seconds.
    Jan 19 09:29:51 php: : rc.newwanip: Informational is starting vr0.
    Jan 19 09:29:51 php: : rc.newwanip: on (IP address: 192.168.211.217) (interface: wan) (real interface: vr0).
    Jan 19 09:29:51 php: : ROUTING: change default route to 192.168.211.173
    Jan 19 09:29:52 check_reload_status: reloading filter
    Jan 19 09:29:52 check_reload_status: reloading filter
    Jan 19 09:29:52 apinger: Exiting on signal 15.
    Jan 19 09:29:54 check_reload_status: reloading filter
    Jan 19 09:29:54 apinger: Starting Alarm Pinger, apinger(16744)

    Your dhclient log reports:

    Jan 17 21:16:16 dhclient: New Routers (xl0):

    and your log later reports

    Jan 17 21:16:20 php: : Could not find gateway for interface(wan).

    In contrast, my dhclient log reports

    Jan 19 09:29:49 dhclient: New Routers (vr0): 192.168.211.173

    and

    Jan 19 09:29:51 php: : ROUTING: change default route to 192.168.211.173

    In the particular event recorded in the log extract you posted the dhcp information appears to have not included a default route. But there was a default route in the output you posted. There was an update in between?



  • @wallabybob:

    You have a default route set so what you are seeing is different from the problem in the linked thread so that suggestion doesn't seem to apply.
    Here's what the log on my pfSense 2.0 BETA looks like after I removed the WAN cable and restored it.

    Your dhclient log reports:

    Jan 17 21:16:16 dhclient: New Routers (xl0):

    and your log later reports

    Jan 17 21:16:20 php: : Could not find gateway for interface(wan).

    In contrast, my dhclient log reports

    Jan 19 09:29:49 dhclient: New Routers (vr0): 192.168.211.173

    and

    Jan 19 09:29:51 php: : ROUTING: change default route to 192.168.211.173

    In the particular event recorded in the log extract you posted the dhcp information appears to have not included a default route. But there was a default route in the output you posted. There was an update in between?

    There was no update in between the event last night and the log I posted today.  I visited the gateway tab after taking the netstat information.  I just performed a removal/restore of the WAN cable from my router and show this:

    Jan 18 19:51:14	check_reload_status: syncing firewall
    Jan 18 19:51:17	dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1
    Jan 18 19:51:17	dhcpd: Copyright 2004-2010 Internet Systems Consortium.
    Jan 18 19:51:17	dhcpd: All rights reserved.
    Jan 18 19:51:17	dhcpd: For info, please visit https://www.isc.org/software/dhcp/
    Jan 18 19:51:17	dnsmasq[46051]: reading /etc/resolv.conf
    Jan 18 19:51:17	dnsmasq[46051]: using nameserver 75.75.76.76#53
    Jan 18 19:51:17	dnsmasq[46051]: using nameserver 75.75.75.75#53
    Jan 18 19:51:17	dnsmasq[46051]: exiting on receipt of SIGTERM
    Jan 18 19:51:18	dnsmasq[22157]: started, version 2.55 cachesize 10000
    Jan 18 19:51:18	dnsmasq[22157]: compile time options: no-IPv6 GNU-getopt no-DBus I18N DHCP TFTP
    Jan 18 19:51:18	dnsmasq[22157]: reading /etc/resolv.conf
    Jan 18 19:51:18	dnsmasq[22157]: using nameserver 75.75.76.76#53
    Jan 18 19:51:18	dnsmasq[22157]: using nameserver 75.75.75.75#53
    Jan 18 19:51:18	dnsmasq[22157]: read /etc/hosts - 2 addresses
    Jan 18 19:51:20	dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1
    Jan 18 19:51:20	dhcpd: Copyright 2004-2010 Internet Systems Consortium.
    Jan 18 19:51:20	dhcpd: All rights reserved.
    Jan 18 19:51:20	dhcpd: For info, please visit https://www.isc.org/software/dhcp/
    Jan 18 19:51:20	php: /system.php: The command '/usr/bin/killall 'ntpd'' returned exit code '1', the output was 'killall: warning: kill -TERM 59154: No such process'
    Jan 18 19:51:21	check_reload_status: reloading filter
    ----
    Jan 18 20:03:06	php: : DEVD Ethernet detached event for wan
    Jan 18 20:03:06	dhclient[8559]: connection closed
    Jan 18 20:03:06	dhclient[8559]: connection closed
    Jan 18 20:03:06	dhclient[8559]: exiting.
    Jan 18 20:03:06	dhclient[8559]: exiting.
    Jan 18 20:03:08	kernel: arpresolve: can't allocate llinfo for [my_subnet].1
    Jan 18 20:03:08	kernel: arpresolve: can't allocate llinfo for [my_subnet].1
    Jan 18 20:03:08	kernel: arpresolve: can't allocate llinfo for [my_subnet].1
    Jan 18 20:03:11	kernel: arpresolve: can't allocate llinfo for [my_subnet].1
    Jan 18 20:03:12	kernel: arpresolve: can't allocate llinfo for [my_subnet].1
    Jan 18 20:03:12	check_reload_status: Linkup starting xl0
    Jan 18 20:03:12	kernel: xl0: link state changed to UP
    Jan 18 20:03:13	kernel: arpresolve: can't allocate llinfo for [my_subnet].1
    Jan 18 20:03:13	kernel: arpresolve: can't allocate llinfo for [my_subnet].1
    Jan 18 20:03:13	kernel: arpresolve: can't allocate llinfo for [my_subnet].1
    Jan 18 20:03:13	php: : DEVD Ethernet attached event for wan
    Jan 18 20:03:13	php: : HOTPLUG: Configuring interface wan
    Jan 18 20:03:13	kernel: arpresolve: can't allocate llinfo for [my_subnet].1
    Jan 18 20:03:13	kernel: arpresolve: can't allocate llinfo for [my_subnet].1
    Jan 18 20:03:13	kernel: arpresolve: can't allocate llinfo for [my_subnet].1
    Jan 18 20:03:13	kernel: arpresolve: can't allocate llinfo for [my_subnet].1
    Jan 18 20:03:13	kernel: arpresolve: can't allocate llinfo for [my_subnet].1
    Jan 18 20:03:14	kernel: arpresolve: can't allocate llinfo for [my_subnet].1
    Jan 18 20:03:14	kernel: arpresolve: can't allocate llinfo for [my_subnet].1
    Jan 18 20:03:14	kernel: arpresolve: can't allocate llinfo for [my_subnet].1
    Jan 18 20:03:14	dhclient: PREINIT
    Jan 18 20:03:14	dhclient[20596]: DHCPREQUEST on xl0 to 255.255.255.255 port 67
    Jan 18 20:03:14	dhclient[20596]: DHCPACK from 73.117.224.1
    Jan 18 20:03:14	dhclient: REBOOT
    Jan 18 20:03:14	dhclient: Starting add_new_address()
    Jan 18 20:03:14	dhclient: ifconfig xl0 inet [my_subnet].155 netmask 255.255.254.0 broadcast 255.255.255.255
    Jan 18 20:03:14	dhclient: New IP Address (xl0): [my_subnet].155
    Jan 18 20:03:14	dhclient: New Subnet Mask (xl0): 255.255.254.0
    Jan 18 20:03:14	dhclient: New Broadcast Address (xl0): 255.255.255.255
    Jan 18 20:03:14	dhclient: New Routers (xl0): [my_subnet].1
    Jan 18 20:03:14	dhclient: Adding new routes to interface: xl0
    Jan 18 20:03:14	dhclient: /sbin/route add default [my_subnet].1
    Jan 18 20:03:14	dhclient: Creating resolv.conf
    Jan 18 20:03:14	apinger: ALARM: WAN([my_subnet].1) *** down ***
    Jan 18 20:03:14	apinger: alarm canceled: WAN([my_subnet].1) *** down ***
    Jan 18 20:03:14	check_reload_status: rc.newwanip starting xl0
    Jan 18 20:03:14	dhclient[20596]: bound to [my_subnet].155 -- renewal in 172800 seconds.
    Jan 18 20:03:15	php: : rc.newwanip: Informational is starting xl0.
    Jan 18 20:03:15	php: : rc.newwanip: on (IP address: [my_subnet].155) (interface: wan) (real interface: xl0).
    Jan 18 20:03:15	php: : ROUTING: change default route to [my_subnet].1
    Jan 18 20:03:15	check_reload_status: reloading filter
    Jan 18 20:03:15	check_reload_status: reloading filter
    Jan 18 20:03:15	apinger: Exiting on signal 15.
    Jan 18 20:03:16	check_reload_status: reloading filter
    Jan 18 20:03:17	apinger: Starting Alarm Pinger, apinger(32075)
    Jan 18 20:03:31	dnsmasq[22157]: reading /etc/resolv.conf
    Jan 18 20:03:31	dnsmasq[22157]: using nameserver 75.75.76.76#53
    Jan 18 20:03:31	dnsmasq[22157]: using nameserver 75.75.75.75#53
    

    Notably, it reports that it has the correct default route:

    Jan 18 20:03:15	php: : rc.newwanip: on (IP address: [my_subnet].155) (interface: wan) (real interface: xl0).
    

    Is it possible that the NTPD error above just before I unplugged has something to do with it?  I'd assume no, but I'm not sure if the general error has a bigger tell.


Locked