pfSense 2.2 enters BETA!

The 2.2 release has now reached the beta milestone. This means the release is feature complete, a comprehensive list of new features and changes can be found here, and should stay relatively stable throughout the remainder of the development process. That’s not to say it’s production ready though, our developers are using it in production and have been for months, but unless you have a solid understanding of the underlying system and can manually verify the configuration, 2.2 is not yet for you (young padawan).

If you have a non-critical environment where you can try it out, you can find the latest build on the snapshot server. Please report your experiences on the 2.2 board on the forum. Note that snapshots have the risk of changes being made in the source very frequently, and you may get a snapshot from a point in time that caught part but not all of certain changes.

Known Issues

The most current list of known issues marked as “Feedback” are either believed to be resolved but need more testing, or need further details to be able to replicate and resolve – feel free to add comments to any of those tickets if you can test the specific scenario described. Those marked as “New” are outstanding issues. We welcome contributions, if you can provide a fix for any of the open issues. Before opening a new ticket there, please post to the 2.2 board on the forum where we can help quantify the issue. Before reporting problems, ensure you’re on the latest snapshot, it’s very possible the issue you found is already fixed in our git repository. You can see all commits here.

Important upgrade warning

You can upgrade from 2.1.x to 2.2 just as with any other release, BUT, you cannot downgrade from 2.2 to 2.1.x. And after you upgrade, your configuration will be converted to a format that is usable only on 2.2. If you do upgrade, get a backup first so you can reinstall if needed. Several of the features in 2.2 were revamped to the extent that a change in configuration formatting was necessitated.

Proceed with caution! Expect things to be broken, this is not production-ready for most scenarios for non-developers, but development is moving along rapidly, and we would appreciate feedback from those in a position to test things (and potentially break their network).