pfsense:pfblockerng:install_pfblockerng:increase_firewall_maximum_table_entries
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
pfsense:pfblockerng:install_pfblockerng:increase_firewall_maximum_table_entries [2021/01/28 09:57] – created peter | pfsense:pfblockerng:install_pfblockerng:increase_firewall_maximum_table_entries [2021/01/28 18:38] (current) – peter | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== PFSense - pfBlockerNG - Install pfBlockerNG - Increase Firewall Maximum Table Entries ====== | ====== PFSense - pfBlockerNG - Install pfBlockerNG - Increase Firewall Maximum Table Entries ====== | ||
+ | pfBlockerNG uses a lot of firewall entries. | ||
+ | |||
+ | It is important that enough memory has been allocated to support all these firewall entries. | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Increase Firewall Maximum Table Entries ===== | ||
+ | |||
+ | Navigate to **System -> Advanced -> Firewall & NAT**. | ||
+ | |||
+ | In **Firewall Advanced**: | ||
+ | |||
+ | * Firewall Maximum Table Entries: | ||
+ | |||
+ | <WRAP info> | ||
+ | **NOTE: | ||
+ | |||
+ | If lots of blocklists are being used, then look at setting these slightly higher if you notice any slowness in DNS resolving. | ||
+ | |||
+ | * Be careful of setting this too high as it directly uses more RAM the higher you set it. | ||
+ | * In terms of RAM; 1 state == 1k of RAM, so 1 million states is 1GB of RAM. | ||
+ | |||
+ | As a rough guide, set this value to the following, depending on how much memory there is. | ||
+ | |||
+ | ^Memory^Firewall Maximum Table Entries^ | ||
+ | |4GB|800000| | ||
+ | |8GB|1000000| | ||
+ | |16GB|1200000| | ||
+ | |32GB or Higher|2000000| | ||
+ | |||
+ | </ | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ---- | ||
+ | |||
+ | Return to [[PFSense: | ||
+ | |||
+ | ---- |
pfsense/pfblockerng/install_pfblockerng/increase_firewall_maximum_table_entries.1611827856.txt.gz · Last modified: 2021/01/28 09:57 by peter