> Not sure offhand whether Suricata is even usable in 2.3, but that
> might be worth a shot.
Given that we're using CARP, if we install it on our router2 to test, how long
would you recommend running router2 on 2.3 and router1 on 2.2.6? Generally
I've not waited more than a few minutes between
Chris Buechler wrote on Sat, Jan 16 2016 at 2:23 am:
> The fact you're hitting at least one lighttpd crash makes me think
> there's some other issue there, though no one else has seen any issues
> in 2.2.6, the issue in 2.2.5 wasn't replicable in most cases either.
> There's a reason nginx is now
On Fri, Jan 15, 2016 at 11:59 PM, Steve Yates wrote:
> I don't like leaving things not fully stable so I bit the bullet and
> clicked "Remove Enable/Disable changes in the current Category" so it would
> at least sync. To my surprise it did not help, even after doing it on
> router2 as
I don't like leaving things not fully stable so I bit the bullet and
clicked "Remove Enable/Disable changes in the current Category" so it would at
least sync. To my surprise it did not help, even after doing it on router2 as
well. Then I noticed the CARP sync was also starting to fail
Steve Yates wrote on Tue, Jan 12 2016 at 1:25 am:
> 6) I started on pfSense 2.2.5 and upgraded both routers to 2.2.6 since it
> said it
> fixed some sync issues. On at least two occasions, with 2.2.6, I start
> getting
> "unread notice" alerts for sync errors, and can't connect to the web GUI o
I've been working on implementing Suricata (package 2.1.9.1) on a CARP
dual router setup, and Suricata is set to sync to router2 as well. I have
several issues, the worst of which ends with me unable to connect to router2
via a browser (and of course sync fails).
1) Agonizingly slow pa
