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

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

Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
5 Posts 3 Posters 712 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.
  • F
    FMRC_Cheeky
    last edited by Apr 11, 2020, 2:05 PM

    Re: [SOLVED] 2.4.3 - /rc.filter_configure_sync: cannot define table bogonsv6

    I am new to PFsence, so I have just installed, updated and configured this machine. I am getting this error:

    There were error(s) loading the rules: /tmp/rules.debug:18: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [18]: table <bogonsv6> persist file "/etc/bogonsv6"
    @ 2020-04-11 18:30:26

    I have increased my Logs to 60000 I assume that is what everyone was talking about before. I could be wrong and that is why I am getting these errors. Please any help would be greatly appreciated and direction to where I can solve this problem
    VER
    2.4.5-RELEASE (amd64)
    built on Tue Mar 24 15:25:50 EDT 2020
    FreeBSD 11.3-STABLE

    1 Reply Last reply Reply Quote 0
    • ?
      A Former User
      last edited by Apr 11, 2020, 2:50 PM

      System->Advanced->Firewall & Nat

      Increase Firewall Maximum Table Entries. You can set this very large if needed.


      There is a well known issue with 2.4.5 and large TOTAL table entries. You will see latency and packet loss anytime the filters are reloaded (pfctl runs).

      You could uncheck block bogons on your WAN interface to eliminate one large (100k+) table. If you are using pfblockerng (you should use the devel version) you might want to rethink what IP blocks you are using. The smaller your TOTAL table items the less severe the latency and packet loss will be.

      1 Reply Last reply Reply Quote 0
      • F
        FMRC_Cheeky
        last edited by Apr 11, 2020, 3:56 PM

        Thank you, that seemed to remove that error. I am not getting a different error via pfB_Top_v4. I will see what I find on the forums for that one.

        ? 1 Reply Last reply Apr 11, 2020, 4:03 PM Reply Quote 0
        • ?
          A Former User @FMRC_Cheeky
          last edited by A Former User Apr 11, 2020, 4:06 PM Apr 11, 2020, 4:03 PM

          @FMRC_Cheeky Go bigger. You need to set that larger than your total table items. You can set it as high as 10 or more million if you want without breaking anything. It's the total actual items in tables that causes the latency/packet loss issue not the value of that tunable.

          Added: You should reboot after increasing that value, even if it doesn't prompt you to.

          1 Reply Last reply Reply Quote 0
          • S
            stephenw10 Netgate Administrator
            last edited by Apr 16, 2020, 8:47 PM

            The maximum table size actually needs to be around double the size of the tables you are loading as it loads in the new tables at update before removing the old ones.
            1M is usually sufficient for bogonsv6 and few large pfBlocker tables.

            Steve

            1 Reply Last reply Reply Quote 0
            5 out of 5
            • First post
              5/5
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
              This community forum collects and processes your personal information.
              consent.not_received