WAN ***down***
-
Since last week, workers are complaining of sudden blackouts. When I'm not around, this can take up to 30 minutes before WAN link gets restored.
I'm running pfSense 2.1 on Tue Apr 23 build. I've looked into the system logs and found this:….
Apr 29 07:11:46 apinger: Starting Alarm Pinger, apinger(9273)
Apr 29 07:11:56 apinger: ALARM: WAN_DHCP(x.x.x.x) *** down ***
Apr 29 07:25:02 apinger: Starting Alarm Pinger, apinger(26545)
Apr 29 07:25:02 apinger: Exiting on signal 15.
Apr 29 07:25:03 apinger: Starting Alarm Pinger, apinger(36912)
Apr 29 07:25:13 apinger: ALARM: WAN_DHCP(x.x.x.x) *** down ***
Apr 29 07:29:00 apinger: alarm canceled: WAN_DHCP(x.x.x.x) *** down ***
Apr 29 07:29:02 apinger: Exiting on signal 15.
Apr 29 07:29:03 apinger: Starting Alarm Pinger, apinger(30750)
Apr 29 17:08:26 apinger: ALARM: WAN_DHCP(x.x.x.x) *** down ***
Apr 29 17:09:43 apinger: alarm canceled: WAN_DHCP(x.x.x.x) *** down ***
Apr 29 17:09:45 apinger: Exiting on signal 15.
Apr 29 17:09:46 apinger: Starting Alarm Pinger, apinger(51908)If I watch on the monitor when WAN goes down, the WAN IP address is empty, not even 0.0.0.0. This is also like this on the Interfaces widget on the pfsense index page.
Any idea what's causing this? Problems with ISP - Fault on NIC - Problem with pfSense - ????
Putting latest build up when I post this.
-
If the IP is all 0's, and it's set for DHCP, that usually means the DHCP lease expired and it can't renew it.
That is often, but not always, an issue with the ISP or modem. It could also be an issue with pfSense and DHCP on that particular snapshot.
