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

    Error Loading Firewall Rules

    pfBlockerNG
    4
    5
    955
    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.
    • G
      g.shaffer
      last edited by

      Not sure if this is a general pfSense issue or a pfBlockerNG issue.

      Since upgrading to CE 2.5.2 I get the following notification:

      There were error(s) loading the rules: no IP address found for X:X:X:X::1010101 - The line in question reads [8801]:

      I had enabled IPv6 DNSBL under the DNSBL WebServer Configuration. Prior to the upgrade to 2.5.2 I didn't get these errors. When I disable the option, I don't get the error.

      It looks like the NAT Redirects are setup up correctly (e.g. :10:10:10:1) as well as the VIP.

      pfBlockerNG-devel 3.0.0_16 is loaded.

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

        I had the same error after upgrading to 2.5.2. Under DNSBL Webserver Configuration if you change the webserver interface to Localhost the rule loading error goes away. There seems to be several bugs in 2.5.2 related to Unbound and pfBlockerNG-devel, see https://forum.netgate.com/topic/164972/pfblocker-not-logging-after-2-5-2-pfsense-upgrade

        Screenshot 2021-07-10 105504.png

        G 1 Reply Last reply Reply Quote 1
        • G
          g.shaffer @NickD 0
          last edited by

          @nickd-0 said in Error Loading Firewall Rules:

          https://forum.netgate.com/topic/164972/pfblocker-not-logging-after-2-5-2-pfsense-upgrade

          Thanks for the suggestion, I'll give it a try.

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

            @NickD 0, thanks, that solved it for me.

            1 Reply Last reply Reply Quote 1
            • K
              kaj
              last edited by

              i have the same error to after upgrading from 2.5.1 to to 2.5.2

              1 Reply Last reply Reply Quote 0
              • johnpozJ johnpoz referenced this topic on
              • johnpozJ johnpoz referenced this topic on
              • johnpozJ johnpoz referenced this topic on
              • johnpozJ johnpoz referenced this topic on
              • I interessierter referenced this topic on
              • I interessierter referenced this topic on
              • johnpozJ johnpoz referenced this topic on
              • johnpozJ johnpoz referenced this topic on
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.