2.2.3 Snapshots Available

cmb

The currently-open target 2.2.3 tickets are available here.

Resolved issues in 2.2.3 are available here.

Please help test and report your experiences and any problems here on the 2.2.3 board.

heper

is there an auto-update url or only for manual update?

Gertjan

No auto-update.
It the GUI auto-update would install a "2.2.3 (xxx) HIGHLY EXPERIMENTAL pfSense 2.2.3 developers tree" then all hell would break lose.
Its, as said https://snapshots.pfsense.org/ experimental for 'experts-only' ;)

Use one of the two Update Files sets to update your working 2.2.2 version to an experimental 2.2.3 version.

cmb

No auto-update URL for this round of snapshots. It would use the same URL as pre-2.2-RELEASE did, which we redirected to the stable updates so those using pre-2.2.0 snapshots would get the official release. If this were going to be a longer-term development cycle, we'd do something to accommodate that. This time around, you can use the manual update.

phil.davis

Can someone build a current 32-bit set of snapshots?

jimp

They should be building now.

jimp

Also for those following the thread, the work-in-progress release notes may be found here:
https://doc.pfsense.org/index.php/2.2.3_New_Features_and_Changes

phil.davis

32-bit builder seems to have taken the weekend off.

xbipin

32 bit updates have halted since 13th june, no new snaps coming out

phil.davis

@phil.davis:

32-bit builder seems to have taken the weekend off.

Seems it took a long weekend, I guess Monday must have been a public holiday in 32-bit land? ;)

cmb

It did take an extended weekend. :) It's running again, new i386 snaps are up.

rcfa

Just read through the release notes, and realized the file system stuff, in particular bug #4523.
This just sounds like what I was bitten by, and which necessitated my unit to be shipped half-way across the country, with corresponding downtime and costs…

So, since I'm about to set up that unit again, before I ship it out, it would seem to be a good idea to upgrade to 2.2.3 while I'm at it, such that this particular thing won't bite me anytime soon.

However we have this:

It the GUI auto-update would install a "2.2.3 (xxx) HIGHLY EXPERIMENTAL pfSense 2.2.3 developers tree" then all hell would break lose.

but when I follow the link to the updater/install images, what I see is:

2.2.3 (amd64)
HIGHLY EXPERIMENTAL pfSense 2.2.3 developers tree

which sounds pretty similar.

So what are the files I should use to prevent "all hell" from breaking lose, if I want to install a system from scratch and or update an existing one?
Or does only auto-update cause "hell to break lose", and manual updates are all fine and dandy?

phil.davis

No auto-update URL for this round of snapshots

You have to get the update or full image from http://snapshots.pfsense.org/
and install from System->Firmware, Manual Update.

I believe the quality of 2.2.3-DEVELOPMENT is good. There is a list of things fixed since 2.2.2 was released: https://doc.pfsense.org/index.php?title=2.2.3_New_Features_and_Changes

And I am not aware of any regressions from 2.2.2

I am running 2.2.3-DEVELOPMENT at home and at 2 offices that have new SG-2440 systems with dual-WAN failover-load-balancing, OpenVPN site-2-site servers, DynDNS, limiters…

What to say - the day before a DEVELOPMENT or BETA version of anything is officially called RELEASE actually the DEVELOPMENT/BETA version was fine. Personally I would install 2.2.3-DEVELOPMENT on any new system to start out with a new office having the least bugs possible.

cmb

At this point snapshots should be really safe, we should be days away from release.