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:
Bronze |
Silver |
Gold |
Platinum |
Unlimited |
|
---|---|---|---|---|---|
Duration | 1 year | 1 year | 1 year | 1 year | 1 year |
Support Method | Support Portal | Support Portal / Phone | Support Portal / Phone | Support Portal / Phone | Support Portal / Phone |
Response Time | 1 business day | 4 business hours | 2 hours | 1 hour | 1 hour |
Support Hours | From 8:00am to 5:00pm EST/EDT - Monday to Friday |
From 8:00am to 5:00pm EST/EDT - Monday to Friday |
24 / 7 | 24 / 7 | 24 / 7 |
Multi-Server | No | No | Yes | Yes | Yes |
Notifications | None | Security | Security / Bug Fixes | Security / Bug Fixes | Security / Bug Fixes |
Bug Fixes | No | No | No | Yes | Yes |
Included Incidents | 5 | 10 | 30 | 75 | Unlimited |
Included Consulting Hours | - | - | 2 | 4 | Unlimited |
Cost | $750 USD 700 € |
$1,500 USD 1400 € |
$5,000 USD 4600 € |
$10,000 USD 9200 € |
Contact Us |
Order | Order | Order | 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 |
REST API v1 (Stable) | Read Online |
REST API v1 (Development) | Read Online |
This is a quick how-to in order to add a remote syslog to handle the PacketFence logs.
First, modify the log.conf with a SYSLOG appender. The file should look like this:
log4perl.rootLogger=DEBUG, LOGFILE, SYSLOG
log4perl.category.pf.SNMP = INFO
log4perl.appender.LOGFILE=Log::Log4perl::Appender::File
log4perl.appender.LOGFILE.filename=/usr/local/pf/logs/packetfence.log
log4perl.appender.LOGFILE.mode=append
log4perl.appender.LOGFILE.layout=PatternLayout
log4perl.appender.LOGFILE.layout.ConversionPattern=%d{MMM dd HH:mm:ss} %X{proc}(%X{tid}) %p: %m (%M)%n
log4perl.appender.SYSLOG = Log::Dispatch::Syslog
log4perl.appender.SYSLOG.ident = packetfence
log4perl.appender.SYSLOG.facility = local5
log4perl.appender.SYSLOG.layout = Log::Log4perl::Layout::SimpleLayout
Finally, make sure you include your entry in /etc/rsyslog.conf (RHEL)
local5.* @your_syslog
Restart syslog afterward, and you are done!
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: