PfBlocker
-
Needed to restart Squid and the got an alert with the error.
EDIT: Every time Squid is restarted is when the error occurs. I was messing with Squid yesterday, but did not put it together until now.
-
There was a update on squid package today, apply it and see what happens.
-
There was a update on squid package today, apply it and see what happens.
Squid was reinstalled with the latest version, but still the same.
-
I'll try to reproduce it here.
You get this memory alert once or after squid restart alerts are frequent?
-
I'll try to reproduce it here.
You get this memory alert once or after squid restart alerts are frequent?
The memory alerts only shows after a Squid restart. After the initial alerts there are no more alerts. At least that is what is occurring here.
Dec 30 15:11:54 php: : There were error(s) loading the rules: /tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [19]: table <pfblockertbg>persist file "/var/db/aliastables/pfBlockerTBG.txt"
Dec 30 15:11:54 php: : New alert found: There were error(s) loading the rules: /tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded The line in question reads [19]: table <pfblockertbg>persist file "/var/db/aliastables/pfBlockerTBG.txt"
Dec 30 15:11:46 php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was '/tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded'
Dec 30 15:11:16 php: : There were error(s) loading the rules: /tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [19]: table <pfblockertbg>persist file "/var/db/aliastables/pfBlockerTBG.txt"
Dec 30 15:11:16 php: : New alert found: There were error(s) loading the rules: /tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded The line in question reads [19]: table <pfblockertbg>persist file "/var/db/aliastables/pfBlockerTBG.txt"
Dec 30 15:11:07 php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was '/tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded'
Dec 30 15:10:32 php: /pkg_edit.php: Reloading Squid for configuration sync
Dec 30 15:10:32 check_reload_status: Reloading filter
Dec 30 15:10:32 check_reload_status: Syncing firewall
Dec 30 15:10:32 check_reload_status: Reloading filter
Dec 30 15:10:31 php: /pkg_edit.php: Reloading Squid for configuration sync</pfblockertbg></pfblockertbg></pfblockertbg></pfblockertbg> -
When that error occurs, Squid fails to work as a transparent proxy. Squid still works if you manually set the proxy settings in a browser for example. I disabled pfBlocker for now. Will try a few things.
-
Increase even more Firewall Maximum Table Entries in system->advanced -> firewall/NAT
not!!!! Firewall Maximum States ;)
-
PfBlocker use url tables, so it is firewall maximum table entries for sure.
Firewall maximum states are related to active connections. When you reach this value, you can't do anything on firewall.
-
After trying out a few things all is fine for now. Disabled the TBG List and left the Bluetack enabled. Also in System -> Advanced -> Firewall and NAT; Firewall Maximum Table Entries, removed that large number[9999999999999999] from there. Restarted pfBlocker and now there are no error messages and Squid works as transparent proxy, even with pfBlocker enabled. So it seems the TBG list is the cause of all these issues I was having.
TBG list:
http://list.iblocklist.com/?list=ijfqtofzixtwayqovmxn&fileformat=p2p&archiveformat=gz
http://list.iblocklist.com/?list=ecqbsykllnadihkdirsh&fileformat=p2p&archiveformat=gz
http://list.iblocklist.com/?list=tbnuqfclfkemqivekikv&fileformat=p2p&archiveformat=gz
http://list.iblocklist.com/?list=ewqglwibdgjttwttrinl&fileformat=p2p&archiveformat=gzBluetack list:
http://list.iblocklist.com/?list=bt_level1&fileformat=p2p&archiveformat=gz
http://list.iblocklist.com/?list=bt_level2&fileformat=p2p&archiveformat=gz
http://list.iblocklist.com/?list=bt_level3&fileformat=p2p&archiveformat=gz
http://list.iblocklist.com/?list=bt_ads&fileformat=p2p&archiveformat=gz
http://list.iblocklist.com/?list=bt_spyware&fileformat=p2p&archiveformat=gz
http://list.iblocklist.com/?list=bt_proxy&fileformat=p2p&archiveformat=gz
http://list.iblocklist.com/?list=bt_templist&fileformat=p2p&archiveformat=gz
http://list.iblocklist.com/?list=bt_hijacked&fileformat=p2p&archiveformat=gz
http://list.iblocklist.com/?list=bt_dshield&fileformat=p2p&archiveformat=gz
http://list.iblocklist.com/?list=bt_bogon&fileformat=p2p&archiveformat=gz -
You may try if you want add each TBG list until you find what list get errors.
-
You may try if you want add each TBG list until you find what list get errors.
Yes, I'm going to try that. I might spring for the i-block lists, need to do some research on that. Are the i-block lists any better than the public lists?
-
Did some testing.
With the following in the TBG list, whenever I try to enable them[one at a time], get the Fatal error below.
http://list.iblocklist.com/?list=ijfqtofzixtwayqovmxn&fileformat=p2p&archiveformat=gz
http://list.iblocklist.com/?list=ecqbsykllnadihkdirsh&fileformat=p2p&archiveformat=gzFatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 8650655 bytes) in /usr/local/pkg/pfblocker.inc on line 268
Note, the Bluetack list is still enabled. When testing the above.
-
the total download exceeds php memory limit.
try to apply one list at time
-
the total download exceeds php memory limit.
try to apply one list at time
whenever I try to enable them[one at a time]
I did, or do you mean something else?
-
I mean that. Sorry, I didn't saw the "[one at a time]"
-
I mean that. Sorry, I didn't saw the "[one at a time]"
No problem and guess no more lists for me :(
-
The are some file hacks to increase php memory limit, but it is not supported or recommended by core team.
DO IT AT YOUR OWN RISK
edit ini_set("memory_limit","128M"); to 500M in /etc/inc/config.inc file
and include ini_set('memory_limit', '490M'); on pfblocker.inc
Do not increase it to a value greater then 510M, suhosin.memory_limit is set to 512M
-
edit ini_set("memory_limit","128M"); to 500M in /etc/inc/config.inc file
and include ini_set('memory_limit', '490M'); on pfblocker.inc
Do not increase it to a value greater then 510M, suhosin.memory_limit is set to 512M
I take it a reboot is needed for these changes to take affect?
-
Not at all. There is no changes on php.ini
-
Hmm, I edited the following to test:
/etc/inc/config.inc and changed ini_set("memory_limit","128M"); to 500M
/usr/local/pkg/pfblocker.inc and added ini_set('memory_limit', '490M');
Then tried to enable the TBG list, but still get the Fatal error. Did I do something wrong?
