PacketFence v5.2 released
June 18, 2015

The Inverse team is pleased to announce the immediate availability of PacketFence 5.2.0. This is a major release with new features, enhancements and important bug fixes. This release is considered ready for production use and upgrading from previous versions is strongly advised.

Here are the changes in v5.2:

New Features

  • Introducing support for the PacketFence PKI application to manage certificates and authenticate RADIUS using EAP-TLS.
  • Twitter OAuth is now supported as an authentication source.
  • New ‘portal’ interface type to spawn a captive-portal instance on selected interface.
  • Inline mode now provides an ipset per devices role allowing for better granularity in managing them.
  • Support for OpenWrt 14.07 with hostapd.


  • Specific vhost for httpd.portal diagnostics.
  • Added option to disable logging of sensitive information when failing to execute a command through pf_run.
  • Support for Meraki APs using web authentication on the cloud controller.
  • Passwords are now obfuscated in the Switch configuration.
  • Introduced new ‘ports.httpd_portal_modstatus’ configuration parameter to limit modstatus to a single virtual host.

Bug Fixes

  • Allow the usage of an external monitoring database when using an Active/Active cluster.
  • Validate that a provisioner is not used before deleting it through the administration interface.
  • Stopped logging database password on schema import failure.
  • Fixed incorrect error message when an external portal authenticated device hits the unknown state.

See the complete list of changes and the UPGRADE.asciidoc file for notes about upgrading.

Back to 2015