PacketFence v7.1 released
June 1, 2017

The Inverse team is pleased to announce the immediate availability of PacketFence v7.1. 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 included in this release:

New Features

  • Added support for web authentication (external captive-portal) on Ubiquiti Unifi Controller
  • New Firewall/SSO (JSON-RPC) for communicating with custom firewalls (PR #2320)
  • VoIP detection: LLDP lookup enhancement (#2227) (PR #2316)


  • Add a button to access status from device registration and the other way around (PR #2259)
  • Added the ability to specify multiple DNS server(s) for domain join configuration (PR #2223)
  • Allow to force a predefined sponsor during sponsor authentication (PR #2150)
  • Updated pfdns default filters (PR #2165)
  • Added brands icons to authentication source (i.e Twitter, PayPal etc ..) in the administration interface (PR #2287)
  • Allow pfqueue workers to perform work across multiple queues (PR #2260)
  • Added a way to set time and bandwidth balance in action rule (requires accounting to work) (PR #1936)
  • Do not display the mobileprovider field when doing SMS authentication with only one carrier enabled (PR #2322)
  • Added new reports in the administration interface (PR #2313)
  • Apache based services now support systemd sd_notify (PR #2351)

Bug Fixes

  • Dashboard metrics are now fetched over https (#2272)
  • Renamed Ubiquity to Ubiquiti (PR #2293)
  • Set up variable GOPATH correctly while setting up developer environment for go (PR #2319)
  • Fix too large scoping of authentication sources (#2338)
  • Prevent usage of a Null source in the device registration page (#1784)
  • Fixes duplicate nodes displaying when there are multiple locationlog entries (#1848)
  • Fixed an issue with the Instagram OAuth2 source, where the scope has been modified on the API
  • Fixed and issue where the logging configuration was ignored for and httpd.webservices (#2350)

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

Back to 2017