PacketFence 4.0.4 released
August 5, 2013

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

Here are the changes in 4.0.4:

New feature

  • Portal profiles can now have multiple filters


  • Added new regexp operator for strings in authentication rules
  • Automatic landing on the sign-in page if no internal/oauth authentication source is used by the portal profile
  • Self-registration is now enabled when a profile has at least one external authentication source
  • Authentication sources of portal profiles are now displayed in a sortable table
  • Sort actions of a violation in reverse order to set the role before auto registration
  • Added hostapd configuration in the Network Devices Configuration Guide
  • Version number is now sent when submiting dhcp and useragents fingerprints

Bug fixes

  • External authentication sources of portal profiles are not respected
  • A portal profile can have multiple external authentication sources of the same type
  • Port 443 on the management interface is not open when gaming registration is enable
  • Crash of FreeRADIUS with SOAP::Lite prior to version 1.0
  • Wrong permissions on the logs files causes an error with the log action of violations
  • Error with violations with tainted chain in pfmailer and action_log subroutines
  • Triggering a violation with a trap action doesn’t reevaluate access
  • authentication.conf and profiles.conf are overwritten when updating PacketFence
  • First element of button groups is not properly displayed
  • Sponsors are not extracted from LDAP sources

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

Back to 2013