PFSense Box locking up.
-
I bought one of the pf sense hardware box's after using it installed on various pc's over the years.
Since the replacement I've had 2 SOLID lockups. No SSH, no WebConfigurator, pings to it fail, also the COM Port session via the USB cable fails to work.
It appears that some existing connections are instantly dropped, and most new ones are refused.
This is in a production environment with about…. 100 remote RD lgins, and a few small websites on a 30 Meg Colo hosted connection.
Below is the only logging that I've found that shows anything happened...
Is there a configuration that I'm screwing up-here? Resetting the box solves the issue, but that is my least favorite solution so far.
Thanks,
-C
Apr 18 22:03:51 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 4.16.144.49 bind_addr 4.16.144.50 identifier "WANGW "
Apr 18 22:03:52 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 4.16.144.49 bind_addr 4.16.144.50 identifier "WANGW "
Apr 28 13:38:12 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 4.16.144.49 bind_addr 4.16.144.50 identifier "WANGW "
Apr 28 13:38:15 dpinger WANGW 4.16.144.49: Alarm latency 449us stddev 0us loss 50%
Apr 28 13:38:32 dpinger WANGW 4.16.144.49: Clear latency 7512us stddev 26522us loss 10%
Jun 3 06:16:17 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 4.16.144.49 bind_addr 4.16.144.50 identifier "WANGW "
Jun 3 06:16:20 dpinger WANGW 4.16.144.49: Alarm latency 0us stddev 0us loss 100%
Jun 3 06:16:39 dpinger WANGW 4.16.144.49: Clear latency 5373us stddev 23142us loss 11%