Community support is offered through the mailing lists. You can subscribe to them and ask questions related to PacketFence.

The PacketFence community is very large and active so do not hesitate to subscribe to the mailing list and ask questions. However, please make sure to respect the following guidelines when posting a new message:

  • search for existing answers consult the archives for previously answered questions
  • do not hijack threads don't generate a post by replying to somebody else's message and changing the subject and text; newsreader software will see your post as a part of the same thread and mix the two subjects, to everyone's confusion
  • send plain text message (no HTML or Rich Text) to avoid getting rejected by the spam filters
  • avoid replying to a message on top of the quoted text of the previous correspondence
  • be nice you are in effect asking a large group of people to give you some of their time and attention; ensure that your message is relevant to as many of the people receiving the message as possible

Internet Relay Chat (IRC)

Join us on IRC! We are in the #packetfence channel on the freenode network.

Please note that while available, IRC is not the preferred option for community support. We recommend using the mailing list.

Consulting Services

Network Access Control (NAC) projects are complex in nature because they usually involve many different technologies. We have done hundreds of large-scale deployment projects for prestigious organizations, all around the world. Let us help you make this deployment project a success by using our unmatched expertise!

If you are looking for a PacketFence expert to help you:

  • Install, configure, customize and optimize the solution to meet your needs
  • Perform a pre or post-implementation audit to make sure your PacketFence deployment performs optimally
  • Correct a specific issue with your installation or with components related to it
  • Migrate from a previous solution to PacketFence
  • Efficiently integrate PacketFence with in-house systems (Active Directory, RADIUS, etc.)
  • Develop specific features or add support to new networking equipment

Contact Us

Available Support Package

Duration 1 year
Support Method Support Portal / Phone
Response Time 1 hour
Support Hours 24 / 7
Multi-Server No
Notifications Security / Bug Fixes
Bug Fixes Yes
Included Incidents Unlimited
Included Consulting Hours None - can be purchased separately
Cost $5,000 USD per PacketFence server

Supported operating systems are:

  • Red Hat Enterprise Linux (RHEL) 8
  • Debian 11

The support packages do not include:

  • components installation
  • custom development
  • preventive system monitoring
  • training and documentation

Consulting hours can be consumed for:

  • architecture design and review
  • migration from another system
  • performance tuning
  • best practices


Installation Guide Download PDF Read Online
Upgrade Guide Download PDF Read Online
Network Devices Configuration Guide Download PDF Read Online
Clustering Quick Installation Guide Download PDF Read Online
Developer's Guide Download PDF Read Online
OpenApi Specification - REST API (Stable) Read Online
OpenApi Specification - REST API (Development) Read Online
OpenApi Specification - REST API (Per Release) v13.0


Captive Portal Load Balancing with F5

Instructions provided by the community to configure several PacketFence’s captive portals behind an F5 load balancer in reverse-proxy mode.

In PacketFence

In conf/pf.conf, add under [captive_portal]:


In F5

  1. Add Nodes (servers) you would like to participate in the load balancing

  2. Create load balancing pool with the associated nodes. Set service port for pool members to listen on non-https port.

  3. Create packetfence virtual servers:

  4. Create virtual server that listens on port 443 (https)Select “TCP” for protocol and for Protocol Profile.

  5. Select appropiate SSL (client) profile that contains cert

  6. Select “Auto Map” for SNAT Pool

  7. Select appropiate load balancing pool.

  8. Select “cookie” for Default Persistence Profile

  9. Create virtual server that listens on port 80 (http)

  10. Select “TCP” for protocol and for Protocol Profile.

  11. Select “http” for HTTP Profile.

  12. Create the following IRule and apply it to the port 80 virtual server: ``` when HTTP_REQUEST { HTTP::redirect https:///captive-portal?destination-url=http://[HTTP::host][HTTP::uri] }


June 7, 2012


If you encounter a possible bug with PacketFence, you can access our github page.

Please make sure to respect the following guidelines when reporting a bug:

  • verify that the bug you found is not already known or even fixed in the trunk version
  • make the actual facts very clear; be precise, we need to be able to reproduce the problem
  • explain your speculations, if any
  • add a screenshot to the ticket if appropriate