Bug #6814
closed
pfBlockerNG cannot define table pfB_Europe_v6 after pfsense upgrade to 2.3.2-RELEASE (amd64)
0%
Description
Pfsense version:
2.3.2-RELEASE (amd64)
built on Tue Jul 19 12:44:43 CDT 2016
FreeBSD 10.3-RELEASE-p5
Package
pfBlockerNG 2.1.1_4
Issue:
There were error(s) loading the rules: /tmp/rules.debug:37: cannot define table pfB_Europe_v6: Cannot allocate memory - The line in question reads [37]: table <pfB_Europe_v6> persist file "/var/db/aliastables/pfB_Europe_v6.txt" @ 2016-09-24 18:01:48
Getting same alert generated every few minutes or so, I already tried reinstalling and clean install of pfBlockerN, removing /tmp/rules.debug and /var/db/aliastables/pfB_Europe_v6.txt
Updated by Kill Bill over 8 years ago
You either don't have enough RAM, or you don't have large-enough limit set for tables. Either way, nothing that could be fixed in the package. Duplicate of Bug #4876 (and note that GeoIP v2 got much bigger, notably the IPv6 lists.)
Updated by BBcan177 . over 8 years ago
Increase the pfSense Advanced / Firewall-NAT / Firewall Maximum Table Entries to 10M entries...
Updated by yunior alvarez over 8 years ago
Thank you @BBcan177, my pfsense Firewall Maximum Table Entries were set on default (20mb) I increased the entries to 40Mb and so far so good no more alerts. See below my stats after I reloaded pfBlockerNG filters.
My unit specs:
CPU Type AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
2 CPUs: 1 package(s) x 2 core(s)
Memory usage
52% of 4444 MiB
pfSense Table Stats
-------------------
table-entries hard limit 4000000
Table Usage Count 1528478
Updated by