Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    PfBlocker

    Scheduled Pinned Locked Moved pfSense Packages
    896 Posts 143 Posters 1.3m Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • marcellocM
      marcelloc
      last edited by

      @lpallard:

      What happens?

      Maybe something with the list that pfblocker code could not detect or get around.

      Treinamentos de Elite: http://sys-squad.com

      Help a community developer! ;D

      1 Reply Last reply Reply Quote 0
      • P
        pftdm007
        last edited by

        @marcelloc:

        @lpallard:

        What happens?

        Maybe something with the list that pfblocker code could not detect or get around.

        Do you need something specific to help debugging?  Logs?
        I didnt do anything out of the ordinary so I think this shouldnt happen unless the package was in beta stage which is not.

        1 Reply Last reply Reply Quote 0
        • marcellocM
          marcelloc
          last edited by

          Did you removed pfblocker lists before deleting custom firewall rules?

          pf is complaining about 4 missing aliases.

          Treinamentos de Elite: http://sys-squad.com

          Help a community developer! ;D

          1 Reply Last reply Reply Quote 0
          • J
            justsomeguy6575
            last edited by

            @justsomeguy6575:

            I can't get pfblocker to load this list doc.emergingthreats.net/pub/Main/RussianBusinessNetwork/RussianBusinessNetworkIPs.txt

            Has anyone used this list before?

            Any ideas on this list? Also pfsense says it detected a crash and this is the info it contains:

            Crash report begins.  Anonymous machine information:

            i386
            8.3-RELEASE-p8
            FreeBSD 8.3-RELEASE-p8 #1: Tue Jun 11 06:34:27 EDT 2013    root@snapshots-8_3-i386.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8

            Crash report details:

            PHP Errors:
            in /usr/local/pkg/pfblocker.inc on line 262
            in /usr/local/pkg/pfblocker.inc on line 262
            in /usr/local/pkg/pfblocker.inc on line 262
            in /usr/local/pkg/pfblocker.inc on line 262

            Filename: /var/crash/minfree
            2048

            1 Reply Last reply Reply Quote 0
            • T
              ttblum
              last edited by

              Hi, I meant to add that this only happens when pfBlocker is installed and active.

              I have had two routers running pfBlocker that, when booted after a power outage, all inside hosts have lost internet access
              after the router came back up.

              1 Reply Last reply Reply Quote 0
              • N
                NextPerception
                last edited by

                I have searched around for an answer but I apologize if this has been answered elsewhere. My google-fu sometimes fails me.
                I am trying to set pfblocker so that it's rules apply for all ports except a few that I have manually NATed. I can accomplish this beautifully for a short while by moving the selected firewall rules that are linked to my NAT entries higher in the rules list than the automatically generated pfblocker rules. This unfortunately then reverts back a few hours later to having the pfblocker rules at the top of the list again. I suspect it is reverting when pfblocker updates it's lists. Is there a way to either
                1. Keep the selected NAT rules above the pfblocker auto generated rules even after pfblocker updates or
                2. Have pfblocker ignore certain ports or
                3. Accomplish my desired behavior a different way?

                Thanks in advance!

                Edit: Also, all these rules are in the WAN tab

                1 Reply Last reply Reply Quote 0
                • D
                  Deadringers
                  last edited by

                  Just a quick question on this..

                  with the block list I can see countries like china trying to send me spam emails (from looking at the logs).
                  And that's great! :)

                  But if I browse to a Chinese website does this mean that the pfblocker package won't block it as it has been initiated by myself?

                  1 Reply Last reply Reply Quote 0
                  • Z
                    zenny
                    last edited by

                    Hi:

                    This is an excellent package. Thanks to developers for their hard work. BTW, I am encoutering the following:

                    06-24-13 10:33:54 [ There were error(s) loading the rules: /tmp/rules.debug:26: table name too long, max 31 chars - The line in question reads [26]: table persist file /var/db/aliastables/pfBlockerspamhausdshieldiblocklist.txt]
                    06-24-13 10:37:47 [ There were error(s) loading the rules: /tmp/rules.debug:28: table name too long, max 31 chars - The line in question reads [28]: table persist file /var/db/aliastables/pfBlockerspamhausdshieldiblocklist.txt]

                    Which table is it referring to? And where to make changes?

                    1 Reply Last reply Reply Quote 0
                    • F
                      fragged
                      last edited by

                      @zenny:

                      Hi:

                      This is an excellent package. Thanks to developers for their hard work. BTW, I am encoutering the following:

                      06-24-13 10:33:54 [ There were error(s) loading the rules: /tmp/rules.debug:26: table name too long, max 31 chars - The line in question reads [26]: table persist file /var/db/aliastables/pfBlockerspamhausdshieldiblocklist.txt]
                      06-24-13 10:37:47 [ There were error(s) loading the rules: /tmp/rules.debug:28: table name too long, max 31 chars - The line in question reads [28]: table persist file /var/db/aliastables/pfBlockerspamhausdshieldiblocklist.txt]

                      Which table is it referring to? And where to make changes?

                      pfBlockerspamhausdshieldiblocklist.txt is probably too long of a name for the list to work.

                      1 Reply Last reply Reply Quote 0
                      • Z
                        zenny
                        last edited by

                        @fragged:

                        @zenny:

                        Hi:

                        This is an excellent package. Thanks to developers for their hard work. BTW, I am encoutering the following:

                        06-24-13 10:33:54 [ There were error(s) loading the rules: /tmp/rules.debug:26: table name too long, max 31 chars - The line in question reads [26]: table persist file /var/db/aliastables/pfBlockerspamhausdshieldiblocklist.txt]
                        06-24-13 10:37:47 [ There were error(s) loading the rules: /tmp/rules.debug:28: table name too long, max 31 chars - The line in question reads [28]: table persist file /var/db/aliastables/pfBlockerspamhausdshieldiblocklist.txt]

                        Which table is it referring to? And where to make changes?

                        pfBlockerspamhausdshieldiblocklist.txt is probably too long of a name for the list to work.

                        Thanks. Changing alias to 'spammers' and rebooting worked (without a reboot, the config didn't reload, for developer's attention).

                        1 Reply Last reply Reply Quote 0
                        • S
                          SkyNET
                          last edited by

                          Hi Guys,

                          Quick question about pfBlocker regarding rules.
                          Under "Rules" there are all the pfblocker auto rules.

                          Its about when I change the order of blocking.
                          Lets say Subnet A is allowed to connect to asia and Subnet B is not. (See picture)

                          Every day, the rules are checked and reloaded, and Subnet A is set to the bottom of the list again.
                          So It does not have access to Asia any more. If I change it manually. This works fine for a couple of hours
                          until a filer or rule gets reloaded.

                          What can I do, so I don't have to change the order of the list everyday?
                          Hope the problem is clear. Thanks!

                          ![LAN Rules.PNG](/public/imported_attachments/1/LAN Rules.PNG)
                          ![LAN Rules.PNG_thumb](/public/imported_attachments/1/LAN Rules.PNG_thumb)

                          1 Reply Last reply Reply Quote 0
                          • T
                            ttblum
                            last edited by

                            I configured gateway monitoring, but it didn't seem to help.

                            When the internet connection came back up, the filter reloaded, but pfblocker still would not let traffic through:

                            Jul 1 07:39:53	syslogd: kernel boot file is /boot/kernel/kernel
                            ...
                            Jul 1 07:39:58	php: : The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/pfBlockerAfrica.txt.tmp' 'https://127.0.0.1:8443/pfblocker.php?pfb=pfBlockerAfrica'' returned exit code '1', the output was 'fetch: transfer timed out'
                            ...
                            Jul 1 07:40:09	check_reload_status: Starting packages
                            Jul 1 07:40:09	php: : pfSense package system has detected an ip change -> ... Restarting packages.
                            Jul 1 07:40:14	php: : The command '/usr/bin/grep -v '^#' '/var/db/aliastables/pfBlockerSouthAmerica.txt.tmp' > '/var/db/aliastables/pfBlockerSouthAmerica.txt'' returned exit code '2', the output was ''
                            Jul 1 07:40:14	php: : The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/pfBlockerSouthAmerica.txt.tmp' 'https://127.0.0.1:8443/pfblocker.php?pfb=pfBlockerSouthAmerica'' returned exit code '1', the output was 'fetch: transfer timed out'
                            Jul 1 07:40:14	php: : The command '/usr/bin/grep -v '^#' '/var/db/aliastables/pfBlockerSouthAmerica.txt.tmp' > '/var/db/aliastables/pfBlockerSouthAmerica.txt'' returned exit code '2', the output was ''
                            Jul 1 07:40:14	php: : The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/pfBlockerSouthAmerica.txt.tmp' 'https://127.0.0.1:8443/pfblocker.php?pfb=pfBlockerSouthAmerica'' returned exit code '1', the output was 'fetch: transfer timed out'
                            Jul 1 07:40:16	php: : No pfBlocker action during boot process.
                            Jul 1 07:40:16	php: : No pfBlocker action during boot process.
                            Jul 1 07:40:16	php: : No pfBlocker action during boot process.
                            Jul 1 07:40:16	php: : No pfBlocker action during boot process.
                            Jul 1 07:40:16	php: : Restarting/Starting all packages.
                            ...
                            Jul 1 07:42:16	php: : OpenNTPD is starting up.
                            Jul 1 07:42:16	php: : The command '/usr/bin/killall 'ntpd'' returned exit code '1', the output was 'killall: warning: kill -TERM 26134: No such process'
                            Jul 1 07:42:16	php: : There were error(s) loading the rules: no IP address found for grep: /tmp/rules.debug:18: file "/var/db/aliastables/pfBlockerAfrica.txt" contains bad data no IP address found for grep: /tmp/rules.debug:20: file "/var/db/aliastables/pfBlockerAsia.txt" contains bad data no IP address found for grep: /tmp/rules.debug:22: file "/var/db/aliastables/pfBlockerEurope.txt" contains bad data no IP address found for grep: /tmp/rules.debug:24: file "/var/db/aliastables/pfBlockerSouthAmerica.txt" contains bad data no IP address found for grep: /tmp/rules.debug:26: file "/var/db/aliastables/pfBlockerTopSpammers.txt" contains bad data pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [ /tmp/rules.debug]:
                            Jul 1 07:42:17	check_reload_status: Restarting ipsec tunnels
                            Jul 1 07:42:27	php: : Creating rrd update script
                            Jul 1 07:42:30	php: : No pfBlocker action during boot process.
                            Jul 1 07:42:30	php: : No pfBlocker action during boot process.
                            Jul 1 07:42:30	php: : No pfBlocker action during boot process.
                            Jul 1 07:42:30	php: : No pfBlocker action during boot process.
                            Jul 1 07:42:30	php: : Restarting/Starting all packages.
                            Jul 1 07:42:33	php: : IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
                            Jul 1 07:42:33	check_reload_status: Reloading filter
                            Jul 1 07:42:34	login: login on console as root
                            Jul 1 07:42:41	php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was 'no IP address found for grep: /tmp/rules.debug:18: file "/var/db/aliastables/pfBlockerAfrica.txt" contains bad data no IP address found for grep: /tmp/rules.debug:20: file "/var/db/aliastables/pfBlockerAsia.txt" contains bad data no IP address found for grep: /tmp/rules.debug:22: file "/var/db/aliastables/pfBlockerEurope.txt" contains bad data no IP address found for grep: /tmp/rules.debug:24: file "/var/db/aliastables/pfBlockerSouthAmerica.txt" contains bad data no IP address found for grep: /tmp/rules.debug:26: file "/var/db/aliastables/pfBlockerTopSpammers.txt" contains bad data pfctl: Syntax error in config file: pf rules not loaded'
                            ...
                            
                            

                            Hi, I meant to add that this only happens when pfBlocker is installed and active.

                            I have had two routers running pfBlocker that, when booted after a power outage, all inside hosts have lost internet access
                            after the router came back up.

                            1 Reply Last reply Reply Quote 0
                            • I
                              iamzam
                              last edited by

                              After posting a message about pfblocker not reinstalling in the 2.1 snapshot area I found this thread so I guess I'll just post a link to it here

                              http://forum.pfsense.org/index.php/topic,64312.0.html

                              1 Reply Last reply Reply Quote 0
                              • M
                                Mr. Jingles
                                last edited by

                                @SkyNET:

                                Hi Guys,

                                Quick question about pfBlocker regarding rules.
                                Under "Rules" there are all the pfblocker auto rules.

                                Its about when I change the order of blocking.
                                Lets say Subnet A is allowed to connect to asia and Subnet B is not. (See picture)

                                Every day, the rules are checked and reloaded, and Subnet A is set to the bottom of the list again.
                                So It does not have access to Asia any more. If I change it manually. This works fine for a couple of hours
                                until a filer or rule gets reloaded.

                                What can I do, so I don't have to change the order of the list everyday?
                                Hope the problem is clear. Thanks!

                                Change the Pfblocker auto generated lists to 'alias only', and then manually create a firewall rule for each alias. Thanks to dokternoter for pointing this out before to me  ;D

                                6 and a half billion people know that they are stupid, agressive, lower life forms.

                                1 Reply Last reply Reply Quote 0
                                • S
                                  SkyNET
                                  last edited by

                                  @Hollander:

                                  @SkyNET:

                                  Hi Guys,

                                  Quick question about pfBlocker regarding rules.
                                  Under "Rules" there are all the pfblocker auto rules.

                                  Its about when I change the order of blocking.
                                  Lets say Subnet A is allowed to connect to asia and Subnet B is not. (See picture)

                                  Every day, the rules are checked and reloaded, and Subnet A is set to the bottom of the list again.
                                  So It does not have access to Asia any more. If I change it manually. This works fine for a couple of hours
                                  until a filer or rule gets reloaded.

                                  What can I do, so I don't have to change the order of the list everyday?
                                  Hope the problem is clear. Thanks!

                                  Change the Pfblocker auto generated lists to 'alias only', and then manually create a firewall rule for each alias. Thanks to dokternoter for pointing this out before to me  ;D

                                  Thanks for your help! It works like a charm now!! Description name is important to get it working.

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    doktornotor Banned
                                    last edited by

                                    While at it, it'd be awesome if the custom set up lists did update on reinstall after snapshot upgrade.

                                    1 Reply Last reply Reply Quote 0
                                    • ?
                                      A Former User
                                      last edited by

                                      Hello,
                                      Running pfblocker 1.0.2 on a CARP cluster. The sync tab appears to be broken. Changes in configuration are not carried over to the backup system. Neither are new lists added, old lists modified. Used both sync interface ip and admin interface ip. Logs show this:
                                      Master:
                                      php: : Filter sync successfully completed with https://192.168.xxx.xxx:x.
                                      Slave:
                                      nothing, just a bunch of dhcp and dnsmasq entries.

                                      The sync tab on the master has the sync ticked, contains the ip of the backup system, and the password is correct.
                                      The sync tab on the backup has the sync NOT ticked, and IP is blank.

                                      Thanks

                                      1 Reply Last reply Reply Quote 0
                                      • D
                                        davidfine
                                        last edited by

                                        It seems to think that 66.154.123.x is outside the USA, but it is with a hosting company in Los Angeles. Is this the right place to report this error?

                                        1 Reply Last reply Reply Quote 0
                                        • S
                                          Supermule Banned
                                          last edited by

                                          I think you need to find Marcello in here. I think he was one of the people behind PFblocker.

                                          1 Reply Last reply Reply Quote 0
                                          • marcellocM
                                            marcelloc
                                            last edited by

                                            @davidfine:

                                            It seems to think that 66.154.123.x is outside the USA, but it is with a hosting company in Los Angeles. Is this the right place to report this error?

                                            The contry ip blocklist was updated until the list got paid. There are other free good country lists but I'm still having no time to change pfblocker code to use a new list.

                                            I've asked for donations to speed up update process but had no luck with it.

                                            You can also workaround it by creating a new list with this ip/range and allow ir on pfblocker.  This will be applied before pfblocker deny rules.

                                            Treinamentos de Elite: http://sys-squad.com

                                            Help a community developer! ;D

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.