Hi,
"Christophe Ségui" <christophe.se...@math.univ-toulouse.fr> wrote:I'tried
pfsense 2.1-BE5A1 as router/firewall (ospf is used for wan) and /22 network as
internal network. With PF activated, the node crash after 2 hours up … since
pf is deactivated, node stays up (routing functionnalities are OK). Does
someone experienced the same issue ?Here we are using 2.1BETA1 for a long time
in production.
What we've learnt is that from one day to the other, fixes are incorporated,
but sometimes fixes break something else, so while we used to upgrade everyday
to benefit from the latest fixes, we now stay with a version which "mostly"
works for us : "2.1-BETA1 (amd64)
built on Thu Feb 28 04:29:38 EST 2013"
Since we're running a two nodes cluster, testing a new release is easy but
takes time : upgrade the slave, shutdown the master, see if all works as
expected. If not, restore the full backup, else upgrade the master as well. But
this can be very very time consuming especially due to pfSense's full backup
(when upgrading from the GUI) which saves, slowly, almost everything including
Squid's cache content.
We're still stuck with some minor problems but this version doesn't crash at
least... We've got planned downtime tomorrow, and planned to try an upgrade,
but reading your message I think we'll wait a bit more :-)
So my advice to you would be to try daily upgrades until you'll find one that
works, and stay with it until a BETA2 or an RC is published.
bye
--
Jerome Alet_______________________________________________
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list
