PfBlockerNG



  • Hope someone can help I have outbound deny selected on the IPV4 list below

    Alias Name Alias Description Action Frequency Logging
    IBlock pfBlockerNG IBlock Deny_Outbound 04hours enabled

    PRI1 pfBlockerNG PRI1 Deny_Outbound 01hour enabled

    PRI2 pfBlockerNG PRI2 Deny_Outbound 04hours enabled

    PRI3 pfBlockerNG PRI3 Deny_Outbound 04hours enabled

    SEC1 pfBlockerNG SEC1 Deny_Outbound 04hours enabled

    TOR     pfBlockerNG TOR Deny_Outbound 04hours enabled

    MAIL pfBlockerNG MAIL Deny_Outbound 08hours enabled

    Now I want to keep all the listed enabled but i keep getting some good sites blocked like dropbox.com.

    Can someone advice how i can exclude these destination domains please. I have tried the advance rule outbound invert but when i do it locks me out of the firewall interface.


  • Moderator

    @Brutos:

    Can someone advice how i can exclude these destination domains please. I have tried the advance rule outbound invert but when i do it locks me out of the firewall interface.

    If an IP is getting blocked, then you can either: 1) Suppress the IP from the Alerts Tab 2) Create a new pfBlockerNG alias (Whitelist), and add the IP to the customlist and set the format to "Permit Outbound". Ensure that the "Rule Order" places the Permit Rules, above the Block/Reject Rules.

    If a domain is getting blocked by DNSBL, then you need to suppress it from the Alerts Tab.



  • @BBcan177:

    @Brutos:

    Can someone advice how i can exclude these destination domains please. I have tried the advance rule outbound invert but when i do it locks me out of the firewall interface.

    If an IP is getting blocked, then you can either: 1) Suppress the IP from the Alerts Tab 2) Create a new pfBlockerNG alias (Whitelist), and add the IP to the customlist and set the format to "Permit Outbound". Ensure that the "Rule Order" places the Permit Rules, above the Block/Reject Rules.

    If a domain is getting blocked by DNSBL, then you need to suppress it from the Alerts Tab.

    Thanks I will try that. :)



  • after i installed this package on a new installation, a error has pop up
    Filter Reload
    •  There were error(s) loading the rules: /tmp/rules.debug:20: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [20]: table <bogonsv6> persist file "/etc/bogonsv6" @ 2016-06-11 23:56:52

    any suggestions what its might be ?


  • Moderator

    @Jamerson:

    after i installed this package on a new installation, a error has pop up
    Filter Reload
    •  There were error(s) loading the rules: /tmp/rules.debug:20: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [20]: table <bogonsv6> persist file "/etc/bogonsv6" @ 2016-06-11 23:56:52

    any suggestions what its might be ?

    The bogons is handled by the pfSense code not pfBlockerNG. Maybe try to disable and re-enable Bogons to see what that does. The package changes the max table entry in the advanced settings automatically so it shouldn't be that.



  • @BBcan177:

    @Jamerson:

    after i installed this package on a new installation, a error has pop up
    Filter Reload
    •  There were error(s) loading the rules: /tmp/rules.debug:20: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [20]: table <bogonsv6> persist file "/etc/bogonsv6" @ 2016-06-11 23:56:52

    any suggestions what its might be ?

    The bogons is handled by the pfSense code not pfBlockerNG. Maybe try to disable and re-enable Bogons to see what that does. The package changes the max table entry in the advanced settings automatically so it shouldn't be that.

    will do it and report back,
    can i filter the internet with this package ?
    block adult websites ? porn ?
    does the package wordt with squad guard and squid 3 ?



  • @BBcan177:

    @Brutos:

    Can someone advice how i can exclude these destination domains please. I have tried the advance rule outbound invert but when i do it locks me out of the firewall interface.

    If an IP is getting blocked, then you can either: 1) Suppress the IP from the Alerts Tab 2) Create a new pfBlockerNG alias (Whitelist), and add the IP to the customlist and set the format to "Permit Outbound". Ensure that the "Rule Order" places the Permit Rules, above the Block/Reject Rules.

    If a domain is getting blocked by DNSBL, then you need to suppress it from the Alerts Tab.

    BBCan- first off, great work. Been using pfblocker for a bit and love it (one of my favorite packages on pfsense.) Second- trying to suppress an internal IP (ie. 192.168.1.xxx). I do not have ANY + sign in the alerts tab to add it to the suppression list. As far as I understand, you can add NATted local IPs to the list right? Even when I modify the alias directly and reload, pfblocker continues to block the packets.

    For reference, I am blocking LAN outbound to certain countries and some on WAN too perhaps (not at the box to check.) But regardless, it just seems like my box is not working as it should. I'm running 2.3.1-p5 but I DID upgrade from 2.2.6 with pfblocker still installed (I stupidly didn't uninstall before the big upgrade.)

    Any ideas?


  • Moderator

    @blueduckdock:

    Trying to suppress an internal IP (ie. 192.168.1.xxx).

    I do not have ANY + sign in the alerts tab to add it to the suppression list. As far as I understand, you can add NATted local IPs to the list right? Even when I modify the alias directly and reload, pfblocker continues to block the packets.

    You don't suppress Internal IPs.. Suppression is for External IPs and the Suppression Icon is only visible when "suppression" is enabled, and when the External IP is a /32 or /24. Also it won't suppress for Country Blocking…

    To have some internal IPs excluded from the Block Rules… Best to use the "Adv. Inbound/Outbound" Rule settings.



  • @BBcan177:

    @blueduckdock:

    Trying to suppress an internal IP (ie. 192.168.1.xxx).

    I do not have ANY + sign in the alerts tab to add it to the suppression list. As far as I understand, you can add NATted local IPs to the list right? Even when I modify the alias directly and reload, pfblocker continues to block the packets.

    You don't suppress Internal IPs.. Suppression is for External IPs and the Suppression Icon is only visible when "suppression" is enabled, and when the External IP is a /32 or /24. Also it won't suppress for Country Blocking…

    To have some internal IPs excluded from the Block Rules… Best to use the "Adv. Inbound/Outbound" Rule settings.

    Sounds good. Part of me thought that I'd have to adjust the rules and couldn't use the suppression but I figured I'd try.
    Thanks again mate.



  • pfsense 2.2.6
    I use the country lists to pretty much block anything outside of US/CA
    I then have a whitelist set up for any exceptions
    I am pretty sure that in the past this worked fine.
    At some point the whitelist stopped having any effect.
    The firewall rules order also seems incorrect in that the whitelist follows the pfb block lists
    After poking around in the settings I found that setting the Rule Order to :
    pfB_Pass/Match|pfB_Block/Reject|pfSense_Pass/Match
    seems to get things working correctly - and the rules are now ordered as expected with the pass rule above the block rules.
    Did something change that requires using this rule order rather than the default to get whitelists to work ?
    I would have thought that this and the default would have been the same thing as far as whitelisting goes.
    Although this works I am concerned that this may have unforeseen consequences.


  • Moderator

    @gerry:

    pfsense 2.2.6
    I use the country lists to pretty much block anything outside of US/CA

    Keep in mind that you could also just "Permit" the Countries that you want instead of blocking the world…

    I am pretty sure that in the past this worked fine.
    At some point the whitelist stopped having any effect.
    The firewall rules order also seems incorrect in that the whitelist follows the pfb block lists
    After poking around in the settings I found that setting the Rule Order to :
    pfB_Pass/Match|pfB_Block/Reject|pfSense_Pass/Match
    seems to get things working correctly - and the rules are now ordered as expected with the pass rule above the block rules.
    Did something change that requires using this rule order rather than the default to get whitelists to work ?
    I would have thought that this and the default would have been the same thing as far as whitelisting goes.
    Although this works I am concerned that this may have unforeseen consequences.

    Nothing has changed in that part of the code for awhile…



  • Having a problem getting Bambenek "C2 All Indicator Feed" going.
    I have tried to put it in DNSBL but get this in log when update:

    
    [ dnsc2allindicatorbambenek ] Downloading update  .. 200 OK
     No Domains Found
    

    Any ideas?


  • Moderator

    @Pippin:

    Having a problem getting Bambenek "C2 All Indicator Feed" going.
    I have tried to put it in DNSBL but get this in log when update:

    
    [ dnsc2allindicatorbambenek ] Downloading update  .. 200 OK
     No Domains Found
    

    DNSBL
    https://osint.bambenekconsulting.com/feeds/dga-feed.gz
    https://osint.bambenekconsulting.com/feeds/c2-dommasterlist.txt

    IP
    https://osint.bambenekconsulting.com/feeds/c2-ipmasterlist.txt



  • Thanks, those I use without problem, only for dga-feed.gz I have dga-feed.txt.

    The one that gives No Domains Found is:
    http://osint.bambenekconsulting.com/feeds/c2-masterlist.txt

    Or is it not suitable for pfB?
    In text editor I see it`s different format then the rest.


  • Moderator

    @Pippin:

    Thanks, those I use without problem, only for dga-feed.gz I have dga-feed.txt.

    The one that gives No Domains Found is:
    http://osint.bambenekconsulting.com/feeds/c2-masterlist.txt

    Or is it not suitable for pfB?
    In text editor I see it`s different format then the rest.

    It seems like that Feed is a mix of IPs and Domains…

    The DNSBL parser is expecting the CSV line to be in a specific format. As you can see from your text editor, the CSV format is different between the two lists...

    I would rather not add another function to the DNSBL parser as its just more overhead to go thru for all the other CSV formatted lists. The feeds that I listed above will work just fine as is...

    I also recommend to use the .GZ feed, as that will save both BBC and yourself some bandwidth...



  • Ok thanks, will adjust the feed to gz.

    I would rather not add another function to the DNSBL parser as its just more overhead to go thru for all the other CSV formatted lists

    Ok but thanks for working on this, very nice.

    Another thing, I forgot.
    In another feed is 127.0.0.1 listed and does not seem to work well with Squid.
    Removing the line manually solves it, I should contact them?



  • Moderator

    @Pippin:

    Ok thanks, will adjust the feed to gz.

    I would rather not add another function to the DNSBL parser as its just more overhead to go thru for all the other CSV formatted lists

    Ok but thanks for working on this, very nice.

    Another thing, I forgot.
    In another feed is 127.0.0.1 listed and does not seem to work well with Squid.
    Removing the line manually solves it, I should contact them?

    Yes some feeds add RFC1918, and loopback addresses occassionaly… I've even seen 0.0.0.0 which is disasterous ;)

    In the case of Firehol, that site updates those feeds once per day. I ususally update the Feeds more often depending on the frequency of updates for a particular Feed. A lot of Feeds make changes hourly... So getting a feed updated once per day, doesn't really do you justice, and I recommend to add the Original Feed source directly into pfBlockerNG and not go thru a third-party to get a Feed.

    Also note, that you can enable "Suppression" in the General Tab, which will remove all RFC1918 and loopback addresses automatically which will avoid this issue for the future…



  • @BBcan177:

    I recommend to add the Original Feed source directly into pfBlockerNG and not go thru a third-party to get a Feed.

    Was thinking about that too now. Next time I have time enough will try to find the original ones.

    Also note, that you can enable "Suppression" in the General Tab, which will remove all RFC1918 and loopback addresses automatically which will avoid this issue for the future…

    Yeah I saw that but it`s not removing 127.0.0.0/8, 10.0.0.0/8 and 192.168.0.0/16.
    0.0.0.0/8 is also on there (:

    Will remove that list later, tomorrow another day.



  • http://someonewhocares.org/hosts/hosts

    Here is another advert list, this guy actually updates his. I have been VERY happy with it


  • Moderator

    @theeddie:

    http://someonewhocares.org/hosts/hosts

    Here is another advert list, this guy actually updates his. I have been VERY happy with it

    FYI - This, and other DNSBL Feeds are listed in this thread below:    (Just in case you didn't see it before)

    https://forum.pfsense.org/index.php?topic=102470.msg572943#msg572943
    https://forum.pfsense.org/index.php?topic=102470.msg573159#msg573159



  • I have a problem when i use this my DNS stops to work out what am I doing wrong?



  • Hello,

    I'm encountering a problem since my update to PfSense 2.3.2.

    I've reinstalled my PfSense Box 8 times in 3 days, each time where I'm using PfSense without PfBlockerNG all is fine, and when I'm installing PfBlockerNG, after few hours (30 minutes to 6 hours) my Box begin to be unaccessible, SSH and Serial, on serial I got a lot of lines of "swap_pager_getswapspace(X): failed".

    **Material :
    I'm using Lanner Box FW-7568B (spec here in 2 words the specs are :
    Intel Atom Dual Core Pineview D-525
    8 x GbE Ports (6 x Intel 82574L and 2x Intel 82541P1)
    4 Gb DDR3 800 Mhz SODIMM (In fact it's 1 Gb on Motherboard and 4 Gb in SODIMM but the max used by system is 4 Gb)
    SSD 128 Go SATA
    Hitachi Travelstar 250 Go

    **OS :
    PfSense 2.3.2 AMD64 (built on Tue Jul 19 12:44:43 CDT 2016)
    Full Install from USB Key, with Custom options, embed Kernel

    **Interfaces setup :
    I'm using a LAGG 8 x 1 GbE with 802.3ad switch behind (2 x Netgear M5300).
    4 x WAN connection, all ADSL, 3 are fixed IP and one is dynamic.
    All interfaces are on VLAN, just LAN is on LAGG0

    **My Packages are :
    Avahi : 1.11_2
    Nut : 2.3.1
    Notes : 0.2.9-2
    Service_Watchdog : 1.8.3
    PfBlokerNG : Before reinstall it was 2.1.1 after 2.1.1_2

    **System tunables :
    I'm using system tunables since this lot of crash for this parameters : kern.ipc.nmbclusters

    I haven't modified my PfSense installation, I'm using my backuped config.xml who contains parameters for all my package listed upon, and for snort (I'm not using i since a lot of time)

    The first time where this happen (10 days ago, with 5 days of balckout because I wasn't near of the box) on 2.3.1, with the update of PfBlokerNG 2.1.1 to 2.1.1_2, I was on vacation, and my Box become unaccessible, when I was back, I've seen my Box unable to boot after the "ldconfig" message during the boot process.

    I've changed my first drive from SSD to HDD, to be sure it wasn't a failed drive problem (same if SMART was ok).

    Can someone tell me what was wrong ? I'm not sure it's only a software problem, maybe hardware too or only, because my Box was up for 90 days (approx) without any problem and suddendly my problem begin with just PfBlokerNG update …
    I don't understand why when PfBlockerNG was installed and did reload the configuration after installation process, my Box become slow specially for Rules and PfBlockerNG page from Web GUI, and for SSH and Serial too.

    My config.xml don't have any "pf_*" rules, I've suppressed it manually for all my WAN interfaces, because latest backup (just before my precedent crash contain PfBlockerNG Rules), so I've clean it all PfBlockerNG related on rules, aliases URL, etc ... All my latest PfBlocker settings still on config.xml.

    So if you can point me  where my problem is I would realy appreciate ...

    Thanks in advance.

    Best regards,
    Alex.**********



  • What do you see in System Log, pfblockerlog, Diagnostic System Activity, etc ?



  • What do you need ?

    I know top -aSH, system.log, but what other ?

    The problem is, if the box was unnaccessible, I have no other way rebooting it, and after this, PfSense no longer boot, still blocked after system 32 ldconfig, just before loading fstab I assume, so if you know how to get back the information, i could give you a lot more … (I think too many process are writing, and finaly file system was corrupted, so I can't no longer mount the system, I've try by rescue mode from PfSense installation,w ithout success !)

    I'll reinstall PfBlockerNG and wait for a crash and give you the results, juste let me know what's the best informations to keep before and after crash and Ill do !

    Thanks in advance.

    Best regards,
    Alex.



  • The logs are located in /var/log/pfblockerng

    Check to see if you have a loopback address with```
    grep "^127" /var/db/pfblockerng/deny/*

    
    When you restore the config, edit the config file first and change <enable_cb>on</enable_cb> to off, this way pfBlockerNG isn't enabled on reboot.
    
    If you are using DNSBL, on restore a missing pfb_dnsbl.conf would prevent the Resolver from starting. You can :```
    touch /var/unbound/pfb_dnsbl.conf
    

    before the reboot in order to have unbound start and get Resolver service running.



  • I don't know if this can help (I doubt) but on my SysLog Server, at the first day where my problem begin, I can see this :

    2016-07-26	00:09:15	info		local7	dhcpd	171,16777216,,1000022611,lo0,match,pass,in,4,0x0,,64,21510,0,none,17,udp,72,127.0.0.1,127.0.0.1,21251,53,52
    2016-07-26	00:09:15	info		local7	dhcpd	178,16777216,,1000022712,lagg0_vlan91,match,pass,out,4,0x0,,64,7240,0,none,17,udp,69,81.210.11.173,212.27.40.241,22626,53,49
    2016-07-26	00:09:15	info		local7	dhcpd	4747,16777216,,1429561533,lagg0_vlan30,match,pass,in,4,0x0,,100,5443,0,none,17,udp,58,192.168.191.245,192.168.191.250,8161,53,38
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(12): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(12): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(12): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(7): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(8): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(8): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(4): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(9): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(9): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(8): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(4): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(7): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(8): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(4): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(7): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(6): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(6): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(6): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(7): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(6): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(7): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(4): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(4): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(15): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(8): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(6): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(9): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(14): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(13): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(6): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(4): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(8): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(12): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(6): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(12): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(9): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(6): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(12): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(9): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(14): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(9): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
    2016-07-26	00:09:01	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
    2016-07-26	00:08:06	info		local7	dhcpd	4647,16777216,,1431955052,lagg0_vlan40,match,pass,in,4,0x0,,64,12387,0,DF,17,udp,63,192.168.194.1,192.168.199.250,37762,53,43
    2016-07-26	00:08:06	info		local7	dhcpd	4747,16777216,,1429561533,lagg0_vlan30,match,pass,in,4,0x0,,100,5301,0,none,17,udp,58,192.168.191.245,192.168.191.250,8091,53,38
    2016-07-26	00:08:06	info		local7	dhcpd	1656,16777216,,1770011086,lagg0_vlan91,match,block,in,4,0x0,,112,32706,0,none,17,udp,134,92.38.104.168,81.210.11.173,59402,38613,114
    2016-07-26	00:08:05	info		local7	dhcpd	178,16777216,,1000022712,lagg0_vlan91,match,pass,out,4,0x0,,64,20656,0,none,17,udp,69,81.210.11.173,212.27.40.241,39154,53,49
    2016-07-26	00:08:05	info		local7	dhcpd	4714,16777216,,1429561478,lagg0_vlan10,match,pass,in,4,0x0,,64,0,0,DF,17,udp,88,192.168.190.114,23.234.53.67,26042,10001,68
    2016-07-26	00:08:05	info		local7	dhcpd	178,16777216,,1000022712,lagg0_vlan91,match,pass,out,4,0x0,,64,0,0,DF,17,udp,88,81.210.11.173,23.234.53.67,44638,10001,68
    2016-07-26	00:08:05	info		local7	dhcpd	4714,16777216,,1429561478,lagg0_vlan10,match,pass,in,4,0x0,,64,0,0,DF,17,udp,88,192.168.190.114,23.234.53.61,26042,10001,68
    2016-07-26	00:08:05	info		local7	dhcpd	178,16777216,,1000022712,lagg0_vlan91,match,pass,out,4,0x0,,64,0,0,DF,17,udp,88,81.210.11.173,23.234.53.61,44359,10001,68
    

    This error from DHCPD only occur when PfBlokerNG is installed, I don't understand why …



  • Out of swap space?

    Too little ram?

    Pfblockerng was starting to swap for me at 8 gigs, so I bought another 8 to be safe.



  • I've found (thanks johnpoz) that my problem seem to be a memory problem :

    2016-07-25 17:18:22 err local7 dhcpd /usr/local/www/pfblockerng/pfblockerng.php: PHP ERROR: Type: 1, File: /etc/inc/config.lib.inc, Line: 202, Message: Allowed memory size of 268435456 bytes exhausted (tried to allocate 13129085 bytes)

    johnpoz gived me thread where this problem is discussed : here

    Is this "patch" working ? :

    Temporary Fix for

    php /usr/local/www/pfblockerng/pfblockerng.php update

    Failing with memory exhaustion:

    cp /etc/rc.php_ini_setup /etc/rc.php_ini_setup.BACKUP
    cp /usr/local/etc/php.ini /usr/local/etc/php.ini.BACKUP
    perl -pi -e 's/536870912/671088640/g' /etc/rc.php_ini_setup /usr/local/etc/php.ini

    512 * 1024 * 1024 -> 536870912
    640 * 1024 * 1024 -> 671088640 works for me. maybe your setup needs more

    What will be the correct memory size for 64 Bits installation ? On i386 BBcan77 seem to recommend 300M.

    Perhaps, I can't upgrade memory, my embeed can handle 4 Gb at maximum (I've update it with a 4 Gb memory).

    Thanks for your help.

    Best regards,
    Alex.



  • Perforado's solution modify the pfsense installation and could be overwritten when fpsense update happens. The BBcan177 solution only fixes the pfBlockerNG system, so it shouldn't break anything else. By default is is 512MB on a amd64 box, so you might rise it to 640M or 768M.

    How big is swap? Do you have /var in ram? Is-it filling up ?

    More info on your swap space issue : https://www.google.com/search?q=swap_pager_getswapspace&hl=en-US

    As for pfBlockerNG have a look at https://forum.pfsense.org/index.php?topic=102470.msg645219#msg645219

    Did you look at the pfblockerNG.log to see if things are running fine ?



  • @Perforado:

    All the php-scripts spawned by the gui are constrained by the memory-limit set by suhosin. Which is 512MB.

    That's what my perl-one-liner was for. I even increased the limit to 4GB for testing today …

    For those wandering about suhosin, it is defined in /usr/local/etc/php.ini

    ; File generated from /etc/rc.php_ini_setup
    output_buffering = "0"
    expose_php = Off
    implicit_flush = true
    magic_quotes_gpc = Off
    max_execution_time = 900
    request_terminate_timeout = 900
    max_input_time = 1800
    max_input_vars = 5000
    register_argc_argv = On
    register_long_arrays = Off
    variables_order = "GPCS"
    file_uploads = On
    upload_tmp_dir = /tmp
    upload_max_filesize = 200M
    post_max_size = 200M
    html_errors = Off
    zlib.output_compression = Off
    zlib.output_compression_level = 1
    include_path = ".:/etc/inc:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg:/usr/local/www/classes:/usr/local/www/classes/Form"
    display_startup_errors=on
    display_errors=on
    log_errors=on
    error_log=/tmp/PHP_errors.log
    extension_dir=/usr/local/lib/php/20131226/
    date.timezone="America/New_York"
    session.hash_bits_per_character = 5
    session.hash_function = 1
    
    ; Extensions
    
    ; opcache Settings
    opcache.enabled="1"
    opcache.enable_cli="0"
    opcache.memory_consumption="50"
    
    [suhosin]
    suhosin.get.max_array_index_length = 256
    suhosin.get.max_vars = 5000
    suhosin.get.max_value_length = 500000
    suhosin.post.max_array_index_length = 256
    suhosin.post.max_vars = 5000
    suhosin.post.max_value_length = 500000
    suhosin.request.max_array_index_length = 256
    suhosin.request.max_vars = 5000
    suhosin.request.max_value_length = 500000
    suhosin.memory_limit = 536870912
    
    

    Setting 'memory_limit' in the inc file is maxed by the suhosin.memory_limit.

    The memory_limit is defined in /etc/inc/config.inc

    // Set memory limit to 512M on amd64.
    if ($ARCH == "amd64") {
    	ini_set("memory_limit", "512M");
    } else {
    	ini_set("memory_limit", "128M");
    }
    

    So for those using many IPV6 GeoIP table on amd64, they probably have to change /usr/local/etc/php.ini /etc/rc.php_ini_setup and the pfblockerng.inc as well as the Firewall Maximum Table Entries

    The php memory issues are not specific to pfBlockerNG, backup crashes when backup size is too big, the Diagnostics/Tables will crash when viewing huge table, etc.



  • Hi There,

    Let me start by saying this is an awesome package and I love all your hard work on it!

    I have a bit of an issue from time to time with the DNSBL. It seems some sites, in this case youtube.com, are getting falsely blocked with unbound/DNSBL. It comes up with "No Match" yet the block rule is still firing away. Any thuoghts as to why?

    I've tried reinstalling the package, doing updates/reloads, to no avail. It does seem to work temporarily if I disable DNSBL, and works for a while until the states reset or DNS refreshes I guess when I re-enable DNSBL.

    Picture attached. Note that youtube.com is already in the suppress list as well to whitelist it!

    Cheers
    Humm3r

    ![false positive dnsbl.PNG](/public/imported_attachments/1/false positive dnsbl.PNG)
    ![false positive dnsbl.PNG_thumb](/public/imported_attachments/1/false positive dnsbl.PNG_thumb)





  • @RonpfS:

    https://forum.pfsense.org/index.php?topic=116490.0

    This has been on and off for a week. I've tried updating as per the thread you linked to all week, but hasn't helped.

    I'll keep trying to update and see what happens. let me know if there's anything else you can suggest, I do appreciate the link! :)

    ![updated not working.PNG](/public/imported_attachments/1/updated not working.PNG)
    ![updated not working.PNG_thumb](/public/imported_attachments/1/updated not working.PNG_thumb)



  • Did you put youtube-ui.l.google.com in the whitelist ?



  • @RonpfS:

    Did you put youtube-ui.l.google.com in the whitelist ?

    That helped, but IE still gets an error about the certificates. I'm guessing this has to do with the ads being blocked. Just wanted to post back my findings, thanks for the help :)

    It works fine in Chrome which is my main browser.

    ![youtube ads.PNG](/public/imported_attachments/1/youtube ads.PNG)
    ![youtube ads.PNG_thumb](/public/imported_attachments/1/youtube ads.PNG_thumb)
    ![pfblockerng alerts.PNG](/public/imported_attachments/1/pfblockerng alerts.PNG)
    ![pfblockerng alerts.PNG_thumb](/public/imported_attachments/1/pfblockerng alerts.PNG_thumb)



  • To install or re-install pfBlockerNG 2.1.1_2

    https://forum.pfsense.org/index.php?topic=102470.msg647719#msg647719



  • Crazy Question:
    Have up to date PFsense,  2.3.2-RELEASE (i386)
    built on Tue Jul 19 13:09:39 CDT 2016

    Installed pfBlockerNG package from web interface.
    INSTALLED SUCCESSFULLY as it said when it completed.

    Could not find (it) anywhere in the web interface.

    REBOOTED

    Shows Installed: pfBlockerNG 2.1.1_2

    Still cannot find it or anywhere in the web interface.
    I understand it should show up under <firewall>in the web interface but is not there.

    Rebooting does not fix it.

    I have no clue what to try next.</firewall>



  • Check the installation logs, /var/log/pfblockerng/*, Dashboard for crash report etc.
    and look here https://forum.pfsense.org/index.php?topic=102470.msg647719#msg647719



  • Thanks will do.


  • Moderator


Log in to reply