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

    There were error(s) loading the rules: /tmp/rules.debug:25: cannot define table

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 2 Posters 1.1k 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.
    • Yet_learningPFSenseY
      Yet_learningPFSense
      last edited by

      I've been using pfSense for about two months, and I encountered an error when trying to whitelist an IP address using pfBlocker.

      The error message is as follows: "There were error(s) loading the rules: /tmp/rules.debug:25: cannot define table pfB_Asia_v4: Cannot allocate memory - The line in question reads [25]: table <pfB_Asia_v4> persist file "/var/db/aliastables/pfB_Asia_v4.txt" @ 2023-07-02 23:54:44."

      I believe I have sufficient memory with 8GB, so I'm unsure of the cause. How can I resolve this issue?

      R 1 Reply Last reply Reply Quote 0
      • R
        rcoleman-netgate Netgate @Yet_learningPFSense
        last edited by

        @Yet_learningPFSense

        @Yet_learningPFSense said in There were error(s) loading the rules: /tmp/rules.debug:25: cannot define table:

        The error message is as follows: "There were error(s) loading the rules: /tmp/rules.debug:25: cannot define table pfB_Asia_v4: Cannot allocate memory - The line in question reads [25]: table <pfB_Asia_v4> persist file "/var/db/aliastables/pfB_Asia_v4.txt" @ 2023-07-02 23:54:44."

        https://docs.netgate.com/pfsense/en/latest/config/advanced-firewall-nat.html#firewall-maximum-table-entries

        Ryan
        Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
        Requesting firmware for your Netgate device? https://go.netgate.com
        Switching: Mikrotik, Netgear, Extreme
        Wireless: Aruba, Ubiquiti

        Yet_learningPFSenseY 1 Reply Last reply Reply Quote 1
        • Yet_learningPFSenseY
          Yet_learningPFSense @rcoleman-netgate
          last edited by

          @rcoleman-netgate Thank you. Despite increasing the maximum values of the firewall states and restarting, the situation did not change. However, upon checking the package manager, it was discovered that upgrades were available. Accordingly, I upgraded the PFSense package, and after upgrading the package, the initial error no longer occurred. I was still unable to establish an OpenVPN connection at first, but with this method, I was able to successfully connect.

          R 1 Reply Last reply Reply Quote 0
          • R
            rcoleman-netgate Netgate @Yet_learningPFSense
            last edited by

            @Yet_learningPFSense Yes, running current and updated release is a smart move.

            Same with your Firmware -- if there was an update for pfB there is probably also one for pfSense. What release are you running?

            Ryan
            Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
            Requesting firmware for your Netgate device? https://go.netgate.com
            Switching: Mikrotik, Netgear, Extreme
            Wireless: Aruba, Ubiquiti

            Yet_learningPFSenseY 1 Reply Last reply Reply Quote 1
            • Yet_learningPFSenseY
              Yet_learningPFSense @rcoleman-netgate
              last edited by

              @rcoleman-netgate It was about two months ago that I set up PFSense myself, using version 2.6.0 of PFSense and installing pfBlocker about a month ago (I didn't note down the version). There might have been some issues due to the version mismatch.

              Yet_learningPFSenseY 1 Reply Last reply Reply Quote 0
              • Yet_learningPFSenseY
                Yet_learningPFSense @Yet_learningPFSense
                last edited by

                @Yet_learningPFSense said in There were error(s) loading the rules: /tmp/rules.debug:25: cannot define table:

                @rcoleman-netgate It was about two months ago that I set up PFSense myself, using version 2.6.0 of PFSense and installing pfBlocker about a month ago (I didn't note down the version). There might have been some issues due to the version mismatch.

                I am currently using the latest version of PFSense, which is 2.7.0.

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