[Chugalug] pfSense issue
phil.sieg at gmail.com
Tue Oct 22 19:28:12 UTC 2013
All of the hardware sans CF card has been replaced.
Next step: New CF card with latest release.
If that does not work it is something that is being triggered by the network itself.
SeniorTech LLC / snapfōn®
phil.sieg at seniortechllc.com
"The computer is the most remarkable tool that we've ever come up with. It's the equivalent of a bicycle for our minds."
Steve Jobs, 1955-2011
On Oct 22, 2013, at 3:07 PM, Dave Brockman <dave at brockmans.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 10/22/2013 12:19 PM, Phil Sieg wrote:
>> Need some help:
>> Got a pfsense box running 1.2.2. It has been in production for
> That release is almost 5 years old now. My first recommendation would
> be to update the "firmware" of your firewall device.
>> 3 years. Lately it has started to reboot randomly. Fo most of the
>> 3 years it had 6months plus of "uptime" before I would go in and
>> futz with something and reboot.
>> Could something on the network be causing this?
> Anything is possible, and chances are if it is, it is fixed in newer
> releases of pfsense. But an actual hardware reset would make me look
> at hardware. Can you replace the MLB and/or CPU on the unit? Lot of
> bridges, slots and controllers on the MLB that could go bad. What
> chipset are the NICs? I've had a few RT chipsets crap out, but they
> usually stop passing traffic on the wire, not cause a reboot of the
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> -----END PGP SIGNATURE-----
> Chugalug mailing list
> Chugalug at chugalug.org
More information about the Chugalug