Merry Christmas from the pfSense team – 2.0 now beta!

Our Christmas gift to the community is our 2.0 release reaching the beta milestone.

What does this mean? The release is feature complete, with no new features being added, and should stay relatively stable throughout the remainder of the development process. That’s not to say it’s production ready though, most of 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.0 is not yet for you.

To answer the inevitable “when will it be released?” – as always, “when it’s ready”. The release will happen sometime in 2010, but as for a more specific timeline, we can’t provide one at this time.

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.0 board on the forum. There is additional risk with snapshots as changes are 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 can be found here. Those 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.0 board on the forum where we can help quantify the issue. Before reporting problems, ensure you’re on the latest snapshot. At least 10-20+ changes go in most every day, 7 days a week, so 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 1.2.x to 2.0 just as with any other release, BUT, you cannot downgrade from 2.0 to 1.2.x. And after you upgrade, your configuration will be converted to a format that is usable only on 2.0. If you do upgrade, get a backup first so you can reinstall 1.2.3 if needed. Several of the features in 2.0 were revamped to the extent that a change in configuration formatting was necessitated. Many of the rough edges of 2.0 are in the configuration upgrade code, there is less risk with a clean 2.0 install than one upgraded from 1.2.x at this time. Though that’s largely in more advanced configurations.

Proceed with caution! Expect things to be broken, this is absolutely 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 break their network).

Note that kernel debugging is still enabled, which will reduce performance, though from a packet forwarding perspective it’s usually not noticeable.

Merry Christmas from the pfSense team!

Share this Post:

75 Responses to “Merry Christmas from the pfSense team – 2.0 now beta!”

  1. Kostya Says:

    I just found i386 and amd64 images. Which one should I use for Soekris Net5501 board (AMD Geode LX processor)?

  2. Chris Buechler Says:

    Geodes are not 64 bit, use i386. For right now you probably want 32 bit regardless of your hardware (there are some calculation bugs on 64 bit that haven’t been fixed yet – http://redmine.pfsense.org/issues/show/459).

  3. aldi kavari Says:

    extraordinary psense !
    we hope pfsense can run on mips architecture like RouterBoard mikrotik , in order to save on operational costs
    We also hope that can pfsense with interfaces compatible to usb modem

    thaks

  4. Eino Says:

    What’s the status of 3G USB modem support for 2.0?
    Will I be able to plug in my Huawei E160E and use it as primary or backup WAN?

  5. Richard Bailey Says:

    don’t see any activity since end of march, is development proceeding?

  6. Chris Buechler Says:

    Richard: there have been thousands of commits since March, you aren’t looking in the right place if you don’t see activity. Non-stop activity on rcs.pfsense.org.

  7. Fveggerby Says:

    I can see 2.0 BETA is freq updated, BUT this is VERY long in BETA.
    Any idea when 2.0 is released?

  8. Chris Buechler Says:

    Fveggerby: sometime this year. look at newer posts here.

  9. Fveggerby Says:

    Tnx Chris

  10. mynullvoid Says:

    wow it had been sometimes, i know that pfsense is not dead, …. yes I know it will be ready when it is ready. But when is the ETA of the 2.0, a slight firm date will be good

  11. Chris Buechler Says:

    mynullvoid: I don’t know how many times I have to post it. Check newer posts here for newer info, and it will be released sometime this year.

  12. Tito Zerpa Says:

    Pope
    Michelangelo when you finish the Sistine Chapel?

    Michelangelo
    When completed

    Meanwhile you are doing a good job.
    Thanks

  13. pUnKpUsTeR Says:

    @mynullvoid – let Chris do his work – and believe him – this year has a lot of day before it ends – and if its not ready at the end of the Year u should have to wait som day longe ;)d

  14. Shani Says:

    Hi guys and thanks for all your hard work. I started using pfsense from 1.2.3 beta to release and recently I have upgraded to 2.0 BETA 4 in a production environment. I simply used the web gui update feature and the firewall downloaded and came up fine. The only thing that did not came up automatically was the default gateway. Once I added and configured the default gateway, all my VPNs came up. I really liked the feature where you can see who is connected thru openvpn before it used to be a chore. I wish if you can add a feature like untangle has where you can just click to add an openvpn user or click to remove a user. The moment you add a user it lets you download the config file with certificates. Furthermore when you do not want that user simply click on remove and certificate is revoked for that user. I am planning to try the BGP session under 2.0 let see hot it goes.

  15. Chris Buechler Says:

    Shani: we already have OpenVPN user management with export.

  16. R.R. Says:

    I have implemented pfsense 5 years ago in 2 offices, these devices are still working .. thank you guys! you have done a great work!

  17. Jake Says:

    Just wanted to say – great work! been running the beta for a little while now and it is excellent :-)

    Thanks.

    Kind regards,
    Jake.

  18. t@slinux Says:

    pfsense the best of the best on the ALL the NET for ever, secula seculorum…

    THANKS to all pfsense team, from me and meny meny people I know.

  19. v2final Says:

    eagerly waiting for the v2 final! hope it comes by christmas!

  20. ผลบอล Says:

    THANKS to all pfsense team, from me and meny meny people I know.

  21. Magicool Says:

    Thank you all for the hard work! I am using pfSense at home and office. It works perfect.

    P.S. Guess what we wish for Christmas :)

  22. men Says:

    Will test it next week…!, hope it’ll be as good as previous releases thanks for the great work!

  23. xeonixc Says:

    I am waiting for it since last december, i’m so happy that its finally coming out on christmas….great job by you all filter programmers,, its the best christmas gift i’ll ever get :)

  24. yzy-oui-fi Says:

    We are running banch test of the 2.00 since december 2010 now without particular issues.

    Same device running:

    Squid Proxy (with external radius server)
    PPPoe server (with external radius server)
    Openvpn server (with external radius server)
    PPTP server (with external radius server)
    sip proxy (with external radius server)

    Great job guys! Congratulations to all devs!

  25. sbo Says:

    I have implemented pfsense 5 years ago in 2 offices, these devices are still working .. thank you guys! you have done a great work!
    mynullvoid: I don’t know how many times I have to post it. Check newer posts here for newer info, and it will be released sometime this year.

Please don’t post technical questions or off-topic comments. It is far more likely that your questions and concerns will be addressed effectively through one of our support channels.

Leave a Reply