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 |
When using the inline or VLAN enforcement mode in large environments, you may have ARP table overflows. This happens when a lot of devices are on the same layer 2 segment. The symptoms are dhcpd not handing out IP addresses as it should or failing pings in the registration or quarantine VLANs.
To identify if you have this problem look into your dmesg log and if you see Neighbour table overflow messages.
In order to mitigate the problem, you need to tweak kernel settings. In order to enlarge the ARP cache table on a live system, change the following in sysctl.conf :
net.ipv4.neigh.default.gc_thresh1 = 2048
net.ipv4.neigh.default.gc_thresh2 = 4096
net.ipv4.neigh.default.gc_thresh3 = 8192
Then run the following as root to enable the changes:
# sysctl -p
This means that the layer 2 garbage collection will kick in at 2048 MAC addresses exposed to the server with the most aggressive collection kicking in at 8192. This should be large enough for most but feel free to increase if necessary (at the cost of more kernel memory consumed).
Another approach to solve this problem is to do more segmentation of your layer 2 networks.
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: