Next day no WAN access. Need to reboot pfSense



  • I have a pfSense box which shields 4 PCs and 4 VOIP phones. When I turn all PCs off at night, and the next day I turn them back on, I have no WAN access (as in no access to the outside internet world). I can log into the webGUI and reboot the machine. This solves the problem. However, this is not a desireable solution, as I cannot be here everyday to log in and reboot the machine.

    What do you think is the problem?

    Does the connection between pfSense and the ISP time out? Is pfSense going into sleep mode?

    I tried to look at the log file, unfortunately only after the reboot, so the earliest record is the booting sequence.

    All help is appreciated!



  • It happened again this morning. This is the log that seemed suspicious:

    Mar 31 14:12:00 	php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.*.*
    Mar 31 14:12:00 	php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.*.*
    Mar 31 14:12:00 	sshlockout[49860]: sshlockout/webConfigurator v3.0 starting up
    Mar 31 15:08:50 	apinger: ALARM: WANGW(*.27.*.*) *** loss ***
    Mar 31 15:09:00 	check_reload_status: reloading filter
    Mar 31 15:09:49 	apinger: alarm canceled: WANGW(*.27.*.*) *** loss ***
    Mar 31 15:09:59 	check_reload_status: reloading filter
    Mar 31 16:52:41 	apinger: ALARM: WANGW(*.27.*.*) *** loss ***
    Mar 31 16:52:51 	check_reload_status: reloading filter
    Mar 31 17:19:59 	apinger: alarm canceled: WANGW(*.27.*.*) *** loss ***
    Mar 31 17:20:09 	check_reload_status: reloading filter
    Apr 1 03:01:00 	root: rc.update_bogons.sh is starting up.
    Apr 1 03:01:00 	root: rc.update_bogons.sh is sleeping for 29580
    Apr 1 04:04:00 	check_reload_status: configuring interface wan
    Apr 1 09:34:24 	php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.*.*
    Apr 1 09:34:24 	php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.*.*
    

    So I read up on apinger and I found out that if the packet loss is over 20% the alarm goes off with the message loss.

    Found this info here: http://forum.pfsense.org/index.php/topic,32284.msg169610.html#msg169610



  • And it dropped again just now, but it came on right away. This is different than the previous problem, since that one doesn't fix itself.

    Here's the log:

    Apr 1 09:39:49 	apinger: Error while feeding rrdtool: Broken pipe
    Apr 1 09:40:49 	apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s.
    Apr 1 10:06:54 	apinger: ALARM: WANGW(*.27.*.*) *** down ***
    Apr 1 10:07:04 	check_reload_status: reloading filter
    Apr 1 10:07:56 	apinger: alarm canceled: WANGW(*.27.*.*) *** down ***
    Apr 1 10:08:06 	check_reload_status: reloading filter
    Apr 1 10:12:08 	check_reload_status: syncing firewall
    Apr 1 10:12:08 	syslogd: exiting on signal 15
    Apr 1 10:12:08 	syslogd: kernel boot file is /boot/kernel/kernel
    

    Perhaps I should mention that I have a static IP address and a dedicated 20 Mbit line going into the pfSense box.



  • I have a similar problem, my bonded pair PPPOE WAN connection drops one line and therefor the connection but PFSense 2 RC 1 (build Tue May 3 10:16:12 EDT 2011) appears not to notice, I have to reboot to get it to authenticate again. This does not happen in version 1.2.3

    The Zxyel P-663H-51 modem is in bridged mode.

    Regards Grant


Locked