1.2 Release Candidate 3 released!

1.2-RC3 has been released! Here is a list of bug fixes in this new version:

  • IPSEC Carp rules cleanup
  • IPSEC stability worksarounds for > 150 tunnels
  • Only reload webConfiguration from System -> Advanced when cert changes
  • Increase net.inet.ip.intr_queue_maxlen to 1000 which is the IP input queue.
  • Do not allow sticky connection bit to be set if pppoe is enabled. Ticket #1319
  • Disable firmware upgrade for embedded and cdrom and suggest using the console option to upgrade. Ticket #1433
  • Recompile MPD with MSS/dial-on-demand patches (also fixes idle timeout bug) Obtained-from: http://svn.m0n0.ch/wall/tags/release-1.3b3/build/patches/packages/mpd.patch
  • Fix CP not sending Acct-Session-Time to Radius during accounting update Ticket #1434
  • Work around heavy network activity issues. [20070116, update 20070212] Systems with very heavy network activity have been observed to have some problems with the kernel memory allocator. Symptoms are processes that get stuck in zonelimit state, or system livelocks. One partial workaround for this problem is to add the following line to /boot/loader.conf and reboot: kern.ipc.nmbclusters=”0″
  • Bump lighttpd to 1.4.18
  • Show wireless nodes regardless if we can deterimine BSS value.
  • IPSEC tunnel endpoint highlighting in system logs
  • Show the IPSEC interface as a option for the traffic graph.
  • Add RRD Settings page.
  • Make it possible to disable RRD graphs. Bump config so it’s on by default if it wasn’t already.
  • Correctly set reflection timeout for all protocols.
  • Restart snmp services after LAN IP changes Ticket #1453
  • Bump miniupnpd version to RC9 -add multiple interface support
  • Speedup ARP page by using diag_dhcp_leases.php page code for parsing the dhcpd.leases file
  • Relax the ip address check and allow duplicate ip address entries which allows fr example a wireless card and a ethernet card on a laptop to share the same ip address
  • Do not allow DHCP server to be enabled when DHCP relay is enabled, and vice versa Ticket #1488
  • IPSEC keep alive pinger using the wrong source IP address Ticket #1482
  • Failover DHCP Server in 10 seconds as opposed to 60 seconds

1.2-RC3 will appear at a mirror near you very soon. Please let us know what you think on the forum or mailing list.

Update: more than half of the mirrors have these files now, if you try one that doesn’t have the files, try another. They’ll all be updated within 24 hours.

Share this Post:

15 Responses to “1.2 Release Candidate 3 released!”

  1. Paul M Says:

    Please can you release the update version for those of us who’re running it installed to hard drive on our servers?

  2. budman Says:

    Um wasn’t this released like a month ago? I have been running since then


    Has there been changes to the release done on Oct 8th?

  3. Chris Buechler Says:

    The update version is available here:

    It was released yesterday, 1.2 snapshots had the RC3 label on them starting about a month ago, they were pre-release versions. There have been several changes since a month ago.

  4. Jason Ip Says:

    Keep up the good work guys, waiting for 1.2 final before I upgrade

  5. pfSense 1.2 RC3 released « FreeBSD, the unknow giant Says:

    […] pfSense 1.2 RC3 released Published November 8th, 2007 pfSense The pfSense team have now released version 1.2-RC3. A lot of new improvements and features have been added to this version, a list of which can be found here. […]

  6. budman Says:

    Does that make a lot of sense?? Releasing versions with the same name on them? If its not RC3, why would you call the file RC3? How about RC2.1 RC2.2, etc. 😉 or preRC3build1 ?

    I just checked — an the latest version I grabbed, with a build date of built on Wed Nov 7 19:10:57 EST 2007

    An the md5 does not match the one listed where you linked too — hehehe guess Im updating again 😉

    Please keep up the great work guys — but it might be easier for us if you used a simpler method of keeping track of released builds 😉 heheheh

  7. budman Says:

    I guess I should of known since it was in snapshots.pfsense.org 😉 Thanks for the info though.. I’ll pay more attention to where Im grabbing the updates from next time..

  8. jmorey Says:

    Paul M: Go up a directory level from the updates directory and then into the downloads directory. I think you’ll find what you are looking for there.

  9. Colin Says:


    Why are you putting “new improvements and features” into a release candidate?

    Please see:


    I’ve been waiting to upgrade from 1.0.1 for a long time because I need a full release.

    Now I see that instead of working towards a full release you are sneaking (and yes that is the correct word) changes into the release candidates.

    Please – fix any major bugs in RC2 and issue it as a full release (or another release candidate) and leave all the new stuff for 1.3 where it belongs.

  10. javivf’s blog » pfsense 1.2 Release Candidate 3 time! Says:

    […] El pasado 7 de noviembre anunciaban en su blog el lanzamiento de la nueva RC que nos acerca mas a la version final. Podeis consultar las nuevas features en el articulo del mismo blog […]

  11. Chris Buechler Says:

    Colin: If you actually read the change list, you would have seen there are NO NEW FEATURES. Those were only bug fixes. In fact there haven’t been new features in any of the RC’s. Scott just takes a template intro for every release and pastes in the change log, I changed the verbiage on this post.

  12. Arab Says:

    Nice work, I wish more features to be added soon like smoothwall features.

  13. hadi57 Says:

    excellent work guys, keep it up. hoping for more features in squid like upddatexlrator, addon to ipcop

  14. toro Says:

    i switched back to RC2, RC3 keeps crashing after offloading network devices, dunno what is happening there

  15. Chris Buechler Says:

    toro: please post and describe your problem on the forum or mailing list so we can look into it. It’s certainly not a widespread issue, and given the minor scope of the changes in this release, it’s probably not a RC3-specific issue.

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