1.2 status update

I’ve been going through all the open bug tickets cleaning up things that have been fixed and reviewing everything else to help Scott and the other developers fix the remaining issues. We’re down to about a half dozen known issues in the current RELENG_1_2 snapshots, which will hopefully all be fixed in a week or less. At that point, assuming we don’t find any other issues in the mean time, 1.2b2 will be released.

As always, I can’t speculate on a release date for 1.2. That largely depends on what issues people find once 1.2b2 is out, and how much the developers’ real lives and paid work get in the way of open source work. Probably somewhere between 1-4 months from now. We’re shooting for sooner rather than later, as this release is already drastically more reliable and bug free than 1.0.1, but we also want to make sure there are no known issues in the 1.2 release.

Share this Post:

4 Responses to “1.2 status update”

  1. Jason Says:

    As always guys, keep up the good work! It is greatly appreciated

  2. Filippo Says:

    Hello Jason,

    I’ve install pfSense 1.2 BETA 1 but I have a problem with FTP download. I have two ADSL line configured and Load Balancer activated. Is impossible for me to connect to external FTP site trought Windows Command Prompt (when I insert User and Password and make dir, the session remain idle). Other problem is to make connection to external Unix/Linux FTP site. The Direct or Passive mode doesn’t work. Is possibile to resolve these problems in the future release?

    Thanks a lot

  3. Chris Buechler Says:

    This is not a place for support questions, take them to http://forum.pfsense.org or the mailing list.

  4. th3m1n1m4n Says:

    Hi there! I’m using 1.2 for some time now and it has replaced our Sonicwall & Netgear firewall. Its ease of installation and use is just plain great and it’s running very stable. Thank you!


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