Development update

1.2.3-RC1 has been out for nearing a couple months now, and while there aren’t any issues with it that 1.2.2 and earlier versions don’t have, we’re holding out on release because of some issues outside our code base that we hope to get resolved in the underlying software (FreeBSD and ipsec-tools). These affect both 1.2.x and 2.0. Most should be resolved now, though we’re still working on a DPD issue with ipsec-tools.

June 29 Update: We’re still working on one last FreeBSD issue – kern/127528. We will not be releasing RC2 until we have a resolution for this problem.

Share this Post:

20 Responses to “Development update”

  1. Brian Scholer Says:

    Thanks for the update; much appreciated. I’ve been checking the blog every day. I have 1.2.3-RC1 running at home but am waiting (anxiously!) for a final release before putting it on anything in real production, so it’s great to hear something!

  2. Belthazar Says:

    Great news thank you, we have been running 1.2.3-RC1 for a while now (replaced our G2 firewall) in production and we are pretty much happy with it.
    Looking forward to release 2.0.

  3. Lars Maul Says:

    I have been running your software for what seems like years now. Just wanted to give you all working on this project the thanks and a job well done that it so deserves.

    Keep up the good work guys.

  4. Bill A Says:

    Thanks for the update. Just purchase an Alix board an looking forward to RC2 and V2. Keep up the good work!

  5. Nico Says:

    Finaly! News about the stuff under the hood instead of window-dressing…. Don’t get me wrong, pfSense sells a lot better when it looks good but it is not going to sell at all if the technology does not get enoug TLC!

  6. Chris Buechler Says:

    Nico: If you want to see what happens under the hood, there is constantly work happening there, far more than “window dressing” work which might comprise 0.5% of total commits at most. The details, as always, in the various repos at

    The noteworthy ones always make the release announcements, so if you want the cliff notes version you just have to watch the release announcements.

    Though it seems like there are a number of users interested in the back end stuff, so we’ll try to post more frequently aside from release announcements on those topics.

  7. xeonixc Says:

    Nice to hear that RC2 is coming out this week because i just installed RC1 on friday ( 19th june ) but still looking forward to 2.0 based on BSD 8.0 and more support for my crappy hardware

  8. Simby Says:

    will you add theme from testing screenshot?

  9. Aaron Cherman Says:

    Hey Chris, I’ve been a loyal m0n0wall follower for years. Just moved over to pfSense a few weeks ago – so far a few issues have been solved with the move to a newer BSD version. I want to say thanks again for everyone’s hard work and for your help over the years. I look forward to following the growth of pfSense as well.

  10. johnnydawson Says:

    I see that the preferred installation is via hard drive. Are the new solid state drives supported via hard drive installation? That would give the reliabilitiy of embedded monowall, but the power of the non-embedded vesions…just a thought

  11. Chris Buechler Says:

    Aaron: Welcome. 🙂

    Johnny: Yeah SSD should be supported just fine. Though given the experience of one of our developers who has been working with them, the reliability factor just isn’t there yet it seems. Very high failure rates.

    The next generation of embedded is coming soon, at which point it will be a much better choice than the current embedded. You’ll still be limited to some extent due to the nature of CF, but the upgrade problems will be gone, and package support (for those suitable on such a platform) will be available. ETA a month or so.

  12. xeonixc Says:

    cant wait any more for RC2, checking your website six times a day, throw it out quick or i jump out of the window 😛 . Well any bug fixes in wireless and LAN bridge code in RC2?

  13. Chris Buechler Says:

    xeonixc: that is one of the suspected FreeBSD issues that I’m looking at but I don’t see any problems other than the one we got fixed upstream about 3-4 weeks ago.

  14. Steven Says:

    Chris, just out of curiosity – have the FreeBSD devs been able to reproduce or acknowledge the bug within “ping”? I read over the report that started back in Sept 2008, and it seems that it isn’t being readily acknowledged. I wonder how long it will take to resolve this issue, without that acceptance.

    BTW, great job on PFSense, I’m part of the silent majority, but I must say that PFSense is totally sexy, and the best firewall platform I’ve ever had the pleasure to work on. I am looking forward the 1.2.3 release!

  15. Chris Buechler Says:

    Steven: Yes it has finally been acknowledged, we’re working with one of the FreeBSD core developers to find a solution.

  16. tohil Says:

    hi Chris,
    i saw in the issue 127528 since may no comment update. are you near on a solution or is the problem not so easy to fix? is release of 1.2.3 hold till this is fixed?


  17. Chris Buechler Says:

    No update to the PR doesn’t mean we’re not working on it. Yes, the release is on hold until that is resolved, and we are actively working on it.

  18. Shaun Says:

    Is there a spot on the web other than that we can follow the progress on the ping issue? I am by no means a developer but I did find the thread very interesting, at least what’s online.


  19. Chris Buechler Says:

    Shaun: no, that discussion is happening in IRC and emails for right now.

  20. roy slinkman Says:

    I have been running 1.2.3-RC1 at five different sites all connected by IPSEC vpns with squid, squidguard and lightsqid packages installed.

    absolutely NO issues!!!

    great product and the five sites were ipcop sites (replaced them).
    using old dell’s and intel nic’s.

    Keep up the great work.

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