Well it is a siginificant jump for pfsense as it has to adopt the new freebsd 10...

As expected there are bumps along the road.. at the moment reverting to 2.1.5 is your best bet as 2.2's key issues are still being fixed and i dont see the 2.2.1 being released any time soon.

rgds


Sent from my VEGA

-------- Original Message --------
Subject: Re: [pfSense] Pfsense web filter
From: Brian Candler <[email protected]>
Date: Mon, 2015-03-02 18:52
To: pfSense Support and Discussion Mailing List <[email protected]>
CC:

On 02/03/2015 10:39, Alessandro Baggi wrote:
> Why release 2.2 as stable if it is very buggy?
>
Because it's not "very buggy" - the poster was just trolling.

I have 2.2 in production. I was affected by one problem with IPSEC which
is due to a bug in the upstream StrongSwan (which replaced racoon)
https://redmine.pfsense.org/issues/4178

2.2 has also fixed some bugs which were present in 2.1.5, so YMMV.

However, you should be aware that it is a bigger change than the minor
2.1->2.2 version number implies. The base system has changed from
FreeBSD 8 to FreeBSD 10; this implies changes to a number of subsystems
including CARP, IPSEC and DNS tools.
https://doc.pfsense.org/index.php/2.2_New_Features_and_Changes

Hence if you were using 2.1.5 with a specific configuration, it's
possible that it will behave differently. If so, the most constructive
thing to do is to report the specific regression you are seeing.

Regards,

Brian.

_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Reply via email to