PfBlockerNG



  • 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


  • Banned

    I want to clarify my understanding of blocking and whitelisting here. I'm running a home network with no open WAN ports.

    I have turned off default allow any lan, anti lockout rules, put up a floating block everything rule and write a couple LAN pass rules to allow the ports I need.

    On pfBNG I'm using a bunch of lists the BBCan177 suggested. I'm also using DNSBL lists he suggested and the easy lists. Finally I have the top20 spammers country lists. ALL of these rules are LAN deny outbound.

    I see everywhere that you should not block the world and only allow what you need, but it seems like that is directed to setups with open WAN ports. Is LAN deny outbound for country lists valid? I am getting a lot of blocks for the top spammers country lists.


  • Moderator

    @pfBasic:

    I am getting a lot of blocks for the top spammers country lists.

    If your just using the TOP20, that's not "Blocking the World"… Some users, are clicking every Country in every Continent except for a few, and that's what "B.T.W." was referencing...

    You can review the Alerts Tab, to see what's getting blocked... You can also refine the Alerts by using the "Alert Filter" tool.


  • Banned

    OK great, so setting up my pfBNG rules as LAN deny outbound is ideal and I'm not just wasting processing power?


  • Moderator

    @pfBasic:

    OK great, so setting up my pfBNG rules as LAN deny outbound is ideal and I'm not just wasting processing power?

    NP. ;)



  • @RonpfS:

    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

    Been a busy week not had any time to dig into the issue yet. 
    Looks like many people are having to change or increase memory limits and PHP stuff?
    I'm guessing that may be the direction that I may need to go?

    Please forgive my newbieness here but isn't the point of an installable package that they should just work?
    Should not the package install itself modify memory settings as/if needed? and anything else?

    I don't have any other packages installed nor am I doing anything crazy memory hungry. 
    Wasn't going to do anything fancy with the blocker either just wanted to try it out and only have it block the "top ten" fist and see how that worked.

    I'm also reading that uninstalling the package and/or reinstalling it is an absolute NO-NO and can break things even worse!!!  WTF! :) 
    So being a package I'm not able to just uninstall it or reinstall it.   
    I'll reference this if need be but right now I just noticed mention of it in a few threads I read.





  • Is there any real documentation for this package?

    I installed it and all it seemed to do was destroy DNS lookups for all clients, including the firewall itself, for about 45 minutes.  The configuration page is a huge array of settings that are unexplained.  The package doesn't seem to be doing anything at all.  There are no new rules in the firewall, there seems to be no way of viewing any block lists at all.  I can't even find any obvious setting to tell it which sources to use.  Serously, where did everyone learn how to use this?



  • @metalliqaz:

    Is there any real documentation for this package?

    I installed it and all it seemed to do was destroy DNS lookups for all clients, including the firewall itself, for about 45 minutes.  The configuration page is a huge array of settings that are unexplained.  The package doesn't seem to be doing anything at all.  There are no new rules in the firewall, there seems to be no way of viewing any block lists at all.  I can't even find any obvious setting to tell it which sources to use.  Serously, where did everyone learn how to use this?

    Start with the first pages of each of these threads:
    pfBlockerNG
    pfBlockerNG v2.0 w/DNSBL
    pfBlockerNG v2.1 w/TLD
    And over time ;) why not read all pages.

    Also there are plenty of Information boxes on almost every page, click on them.
    And start slowly, go with one feature at a time, IPV4, IPV6, GeoIP, DNSBL until you get things running.

    Go to Firewall / pfBlockerNG / Log Browser, there you can see the log file and pfBlockerNG files. Also visit the Diagnostics /Tables.






  • Those are only useful if you already know the function of the config page in the first place.

    Firewall / pfBlockerNG / Update / Update Settings:

    Well, it obviously schedules a cron job, but what does the cron job do?  No indication whatsoever.
    What's the difference between update, cron, and reload?  No idea.

    Firewall / pfBlockerNG / Alerts / Alert Settings:

    Well, each category gets a number.  What that number means is not explained.  Doesn't seem to matter though, because there is nothing in any alert queue.

    Firewall / pfBlockerNG / Alerts / IPv4:

    What does this do? It's just an "Add" button.  Probably IPv4 rules?  Okay lets make a rule, click Add:
    Good lord.  Apparently I need to find lists myself, unlike ABP in my browser.  What format does it need? What are valid sources? What is the purpose of country codes?

    Can you, being serious and honest with yourself, say that anyone could come in completely cold and actually be able to configure something that works?

    Nah, I don't have time.  The mysterious disruption of DNS site-wide gives me an uneasy feeling, and the lack of documentation and a homepage seals it.



  • Again if you clicked on some infobox you would get many answers.
    As for finding the lists, yes I could go thru the posts and fetch them to you, but you are probably able to do that on you own.



  • metalliqaz does have a point.

    Digging through forum threads is never a fun task.

    It would be really good to have detailed info on package configuration and updated lists in one place.



  • @BBcan177:

    Its what "Open Source" is all about, and I encourage more people to get involved.



  • @doktornotor:

    @Asterix:

    Educate me where you see the default deny inbound global (all countries) rule on a base pfSense install.

    Nowhere. It's not visible, it's implicit. Anything not allowed is denied by default. Unless you have some "allow from any" rule you wish to restrict via country blocking on your WAN, there's just no point in creating inbound country-based rules at all.

    If everything is blocked on WAN-inbound per default / implicit, what is there reason (need) of having two recommended / additional rules on WAN ?

    1. Block private networks and loopback addresses
    2. Block boon networks

    Unless you have some "allow from any“ rule …

    Do you mean on WAN-interface or on LAN-interface ?

    Thanks a lot in advance !



  • It's either a bug or a feature (old IT joke from when I was younger  ;D ).




  • I have some alerts like that in dnsbl.log, last one was Aug 9

    DNSBL Reject HTTPS,Aug 09 19:21:32,watson.microsoft.com
    

    That was probably with pfBlockerNG-2.1.1_1, what version are you using now?

    From the Info infoblock under Firewall / pfBlockerNG / DNSBL

    So not a bug or a feature, more a limitation of the pfBlockerNG DNSBL Web Server.




  • Just finished to read the whole thread, uff ..
    Thanks to BBCan for the package and this thread, I am quit new to pfSense so I learned a lot!

    WAN = INbound, don’t BLOCK the world, the world ist blocked by default, PASS only what you need and take care on that …
    LAN = OUTbound, PASS what you need first and BLOCK all afterwards.

    That two rules are most important to me, afterwards I can take care on the scenarios I need.

    Thanks once again !!



  • Maybe there is one who is able to answer to me why are there two BLOCK-rules, bogon-networks and private-networks if the WAN is BLOCKED by default …?

    Thanks again in advance !!

    @coliflower:

    @doktornotor:

    @Asterix:

    Educate me where you see the default deny inbound global (all countries) rule on a base pfSense install.

    Nowhere. It's not visible, it's implicit. Anything not allowed is denied by default. Unless you have some "allow from any" rule you wish to restrict via country blocking on your WAN, there's just no point in creating inbound country-based rules at all.

    If everything is blocked on WAN-inbound per default / implicit, what is there reason (need) of having two recommended / additional rules on WAN ?

    1. Block private networks and loopback addresses
    2. Block boon networks

    Unless you have some "allow from any“ rule …

    Do you mean on WAN-interface or on LAN-interface ?

    Thanks a lot in advance !



  • Those can be enabled/disabled on the interface itself.

    These are ip-addresses that should never exist on the WAN side (with the execption if you have a router on the WAN side that's not in bridge mode)



  • Thank you digdug3 !

    That helped finally:

    execption if you have a router on the WAN side that's not in bridge mode


  • Moderator

    Arbor Networks Feeds discontinued:
    https://forum.pfsense.org/index.php?topic=122237.0



  • I know that this thread is a little older now.
    I utilized the php script that Dok presented.
    Should I go through and delete the failed downloads or what?
    [ pfB_MAIL - ToastedSpam ] Download FAIL [ 03/19/17 18:50:22 ] 
    [ pfB_MAIL - VirBL ] Download FAIL [ 03/19/17 18:45:01 ]
    [ pfB_SEC1 - MalwareGroup ] Download FAIL [ 03/19/17 18:35:56 ]
    [ pfB_PRI3 - Geopsy ] Download FAIL [ 03/19/17 18:35:33 ]
    [ pfB_PRI3 - VMX ] Download FAIL [ 03/19/17 18:35:31 ]
    [ pfB_PRI3 - DangerRulez ] Download FAIL [ 03/19/17 18:35:03 ]
    [ pfB_PRI2 - HoneyPot ] Download FAIL [ 03/19/17 18:34:41 ]
    [ pfB_PRI1 - dShield_Block ] Download FAIL [ 03/19/17 18:33:09 ]
    [ pfB_PRI1 - Abuse_Spyeye ] Download FAIL [ 03/19/17 18:32:51 ]
    [ pfB_MAIL - URIBL ] Download FAIL [ 03/19/17 18:29:37 ]
    [ pfB_MAIL - ToastedSpam ] Download FAIL [ 03/19/17 18:29:35 ]
    [ pfB_MAIL - VirBL ] Download FAIL [ 03/19/17 18:25:05 ]
    [ pfB_SEC1 - MalwareGroup ] Download FAIL [ 03/19/17 18:15:43 ]
    [ pfB_PRI3 - Geopsy ] Download FAIL [ 03/19/17 18:15:03 ]
    [ pfB_PRI3 - VMX ] Download FAIL [ 03/19/17 18:14:55 ]
    [ pfB_PRI3 - DangerRulez ] Download FAIL [ 03/19/17 18:14:17 ]
    [ pfB_PRI2 - HoneyPot ] Download FAIL [ 03/19/17 18:13:51 ]
    [ pfB_PRI1 - dShield_Block ] Download FAIL [ 03/19/17 18:11:35 ]



  • I went through each one that failed, retried them, and disabled the ones that failed again,
    Then I attempted to go to each site, and if the site was no longer in existence, then I deleted.
    Answered my own question without getting yelled at!


  • Moderator

    @mtarbox:

    I went through each one that failed, retried them, and disabled the ones that failed again,
    Then I attempted to go to each site, and if the site was no longer in existence, then I deleted.
    Answered my own question without getting yelled at!

    The script is a little dated. Some feeds have changed…. some down... so always best to open the site in a browser and check it out....

    The next version of the package will have an automated Feeds Management Tab, which should make this process easier to manage.



  • The next version of the package will have an automated Feeds Management Tab, which should make this process easier to manage.

    +1 from me for that! This might be a cool rich Option for us all, to get taps named like Malware, Virus, ect.
    and insert there the links or URLs to several lists and perhaps a little "+" button to create his own new tap!
    Perhaps I mean ;)



  • Dropbox is block.  NET::ERR_CERT_AUTHORITY_INVALID

    grep result.

    grep "dropbox.com" /var/unbound/pfb_dnsbl.conf
    local-data: "dl.dropbox.com 60 IN A 10.10.10.1"
    local-data: "dropbox.com.azamgold.com 60 IN A 10.10.10.1"
    local-data: "dropbox.com.paki-library.com 60 IN A 10.10.10.1"
    local-data: "dropbox.com.sexvoorlichting.com 60 IN A 10.10.10.1"
    local-data: "www.dropbox.com 60 IN A 10.10.10.1"

    It seems Iblock is causing the issue. DNSBL alerts says the domain is already in the whitelist.

    And now google is doing the same thing.


Log in to reply