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:
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.
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:
Unlimited |
|
---|---|
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 |
Order |
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 |
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]:
loadbalancers_ip=<loadbalancer_ip1>,<loadbalancer_ip2>,...
In F5
Add Nodes (servers) you would like to participate in the load balancing
Create load balancing pool with the associated nodes. Set service port for pool members to listen on non-https port.
Create packetfence virtual servers:
Create virtual server that listens on port 443 (https)Select “TCP” for protocol and for Protocol Profile.
Select appropiate SSL (client) profile that contains cert
Select “Auto Map” for SNAT Pool
Select appropiate load balancing pool.
Select “cookie” for Default Persistence Profile
Create virtual server that listens on port 80 (http)
Select “TCP” for protocol and for Protocol Profile.
Select “http” for HTTP Profile.
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] }
</li></ol>
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: