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

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

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    52 Posts 22 Posters 20.0k 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.
    • R
      rkillcrazy
      last edited by

      @bingo600:

      I just got the same error today on 2 independent  2.4.2-p1 boxes

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

      It has to be the bogon file that has increased in size , as i haven't touched one of the boxes in 2 weeks

      I have tried to increase from 200K to 500K entries (both are 8G Ram machines)

      Lets see if i keep on getting the errors

      Weird … still get the errors w 500K entries

      Nope 500K entries solves it

      In  "System -> Advanced -> Firewall & NAT" I increased the below from 200K to 500K

      MIght be a good idea to do a reboot after the increase.

      /Bingo

      Just to help other people, you cannot see the full post, with the image showing the needed details, unless you're logged into the forum with a member's creds so here's where you change it if you happened upon this thread via a search engine like I did:  System > Advanced > Firewall & NAT > Firewall Maximum Table Entries

      This bit of info helped with my issue as well.  I don't have but a handful of firewall rules so I didn't think it was anything I did.  Furthermore, I hadn't seen the errors until after the upgrade to 2.4.3.  At first, I was seeing the errors nagging about the couple rules I've created but, after a reboot, it was throwing the errors about the bogon network rule in the table and I know that's a factory rule; not one I customize.  So, watch your red herrings…

      I think when the developers upped the size of the bogon networks file, they should have at least recommended the changing of aforementioned setting.  I don't think changing it for the end user is a good idea as you never know what hardware the OS is running on but a warning would have been nice; that's just my two cents.

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

        Is there a way to see how many of these Firewall Entries we are using, even if we're not getting the error?
        If I'm flying close to the sun I'd like to fix it before it's a problem.

        Thanks

        1 Reply Last reply Reply Quote 0
        • DerelictD
          Derelict LAYER 8 Netgate
          last edited by

          pfctl -vvsT | grep Addresses will get you close.

          Note that reloading the tables requires double the space so if that total is getting close to half the defined table maximum you will want to increase it.

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

            Thanks guys for posting the solution!
            In my case I just did upgrade and since I have email notificatons enabled got below email:

            
            Notifications in this message: 1
            ================================
            
            15:15:49 There were error(s) loading the rules: /tmp/rules.debug:19: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [19]: table <bogonsv6>persist file "/etc/bogonsv6"</bogonsv6> 
            

            Increased to 500k and I'm hoping I won't be getting more errors although after getting it for the first time I rebooted and did not got that error.

            I like to fill my tub up with water, then turn the shower on and act like I'm in a submarine that's been hit!

            1 Reply Last reply Reply Quote 0
            • cybrnookC
              cybrnook
              last edited by

              I did a filter reload as well after changing to 400k. Just to make sure all rules were loaded properly.

              1 Reply Last reply Reply Quote 0
              • R
                rkillcrazy
                last edited by

                @cybrnook:

                I did a filter reload as well after changing to 400k. Just to make sure all rules were loaded properly.

                Care to share with others the steps you took to accomplish this?

                1 Reply Last reply Reply Quote 0
                • cybrnookC
                  cybrnook
                  last edited by

                  @rkillcrazy:

                  @cybrnook:

                  I did a filter reload as well after changing to 400k. Just to make sure all rules were loaded properly.

                  Care to share with others the steps you took to accomplish this?

                  Sure

                  System > Advanced > Firewall & NAT > Firewall Maximum Table Entries > 400000
                  Status > Filter Reload > Reload Filter

                  1 Reply Last reply Reply Quote 0
                  • C
                    corvey
                    last edited by

                    Fresh install of pfSense 2.4.3  introduces these errors while configuring my interfaces for the first time:

                    –---------------------------------------------------------------------------------
                        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"
                        @ 2018-04-03 13:46:06
                        There were error(s) loading the rules: /tmp/rules.debug:19: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [19]: table <bogonsv6> persist file "/etc/bogonsv6"
                        @ 2018-04-03 13:47:12
                        There were error(s) loading the rules: /tmp/rules.debug:20: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [20]: table <bogonsv6> persist file "/etc/bogonsv6"
                        @ 2018-04-03 13:48:04
                        There were error(s) loading the rules: /tmp/rules.debug:20: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [20]: table <bogonsv6> persist file "/etc/bogonsv6"
                        @ 2018-04-03 13:49:17
                        There were error(s) loading the rules: /tmp/rules.debug:21: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [21]: table <bogonsv6> persist file "/etc/bogonsv6"
                        @ 2018-04-03 13:49:36
                        There were error(s) loading the rules: /tmp/rules.debug:21: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [21]: table <bogonsv6> persist file "/etc/bogonsv6"
                        @ 2018-04-03 13:49:37
                        There were error(s) loading the rules: /tmp/rules.debug:21: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [21]: table <bogonsv6> persist file "/etc/bogonsv6"
                        @ 2018-04-03 13:49:40
                        There were error(s) loading the rules: /tmp/rules.debug:22: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [22]: table <bogonsv6> persist file "/etc/bogonsv6"
                        @ 2018-04-03 13:50:22
                        There were error(s) loading the rules: /tmp/rules.debug:22: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [22]: table <bogonsv6> persist file "/etc/bogonsv6"
                        @ 2018-04-03 13:50:23
                        There were error(s) loading the rules: /tmp/rules.debug:22: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [22]: table <bogonsv6> persist file "/etc/bogonsv6"
                        @ 2018-04-03 13:50:26
                        There were error(s) loading the rules: /tmp/rules.debug:23: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [23]: table <bogonsv6> persist file "/etc/bogonsv6"
                        @ 2018-04-03 13:50:55
                        There were error(s) loading the rules: /tmp/rules.debug:23: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [23]: table <bogonsv6> persist file "/etc/bogonsv6"
                        @ 2018-04-03 13:50:56
                        There were error(s) loading the rules: /tmp/rules.debug:23: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [23]: table <bogonsv6> persist file "/etc/bogonsv6"
                        @ 2018-04-03 13:51:00
                        There were error(s) loading the rules: /tmp/rules.debug:24: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [24]: table <bogonsv6> persist file "/etc/bogonsv6"
                        @ 2018-04-03 13:51:37
                        There were error(s) loading the rules: /tmp/rules.debug:24: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [24]: table <bogonsv6> persist file "/etc/bogonsv6"
                        @ 2018-04-03 13:51:38
                    –----------------------------------------------------------------------------------

                    I'm guessing the final solution in this thread is to increase the Firewall Maximum Table Entries to 800000 will be enough to cure the problem problem for awhile without any ill effects.  This is a new error in this release I haven't encountered before.

                    pfSensational™

                    1 Reply Last reply Reply Quote 0
                    • cybrnookC
                      cybrnook
                      last edited by

                      400000 is more than enough for today. As we are right now, the bogon file and our firewall add up to about 95000~ entries. When it reloads this table, it doubles in size before the old entries are dropped. Many of us just break that 200000 limit that is default today 95000*2 + whatever else, pushing us over the 200k limit….

                      The new default will be 400000 in the next release. I am using that value, and it works fine, giving you about an additional 100000 buffer (since it's X * 2 = Y, 200000 Bogon list for example would burp to 400000 on reload. but it's only at about 95000 now all-in, so you have 100000 to go, which is a lot).

                      People are also seeing it in 2.4.2+ as well, so not just a 2.4.3 thing. But pops up soon after the install/upgrade, triggering the error message.

                      1 Reply Last reply Reply Quote 0
                      • H
                        humps
                        last edited by

                        @cybrnook:

                        People are also seeing it in 2.4.2+ as well, so not just a 2.4.3 thing. But pops up soon after the install/upgrade, triggering the error message.

                        Yes Confirmed.
                        I'm Running Pfsense 2.4.2 (X64) and these errors showed up in my logs yesterday (April 2, 2018).
                        I haven't seen none since today but i have upend my entries to 500000 to prevent a re occurrence.

                        Regards

                        1 Reply Last reply Reply Quote 0
                        • cybrnookC
                          cybrnook
                          last edited by

                          I assume what's happening is the monthly cron job that downloads and installs the latest bogons file is slowly working it's way through the community. So regardless of version, people will start popping in here one by one with the issue over the next ~25 - 30 days.

                          I assume what's likely happening on new installs (and likely upgrades), is that part of the post processing setup is to download the latest file, then schedule it to download again in 30 days time. That's why I think I am seeing it on fresh installs, right after initial setup wizard.

                          1 Reply Last reply Reply Quote 0
                          • K
                            karlfife
                            last edited by

                            April 3 2018 bogons:  100,001 rows

                            ipv6 bogon prefixes 95,997
                            ipv4 bogon prefixes 4004

                            bogon table size: 100,001 rows

                            If 2x are required to reload the table, then 200K seems slightly too small  ;)

                            I now notice that my 2.4.2 systems are choking the same way as my freshly updated 2.4.3 systems if I both update bogons and reload the filter.

                            1 Reply Last reply Reply Quote 0
                            • V
                              vMAC
                              last edited by

                              New to pfSense and after installing 2.4.3 on a new install this popped up in my alerts.
                              Unfortunately until I resolved this issue none of my port forwards would work at all.

                              I bumped up the number of entries to 500,000 and my port forwards started working immediately.

                              This is just an FYI in case you can't get your port forwards to work to anyone else who is very new to pfSense.

                              1 Reply Last reply Reply Quote 0
                              • B
                                Bili_boy
                                last edited by

                                The thing I don't understand is why it was 200K for you by default in the first place. I'm still on 2.3.4 and my default for "Firewall Maximum Table Entries" is 2M. (2 000 000). Did they reduce the default on purpose ?

                                1 Reply Last reply Reply Quote 0
                                • cybrnookC
                                  cybrnook
                                  last edited by

                                  Without going through the git revisions, I would say yes that somewhere between your release and the 2.4 releases it got changed to two hundred thousand 200,000. If you look at the link in the op for the bug ticket to get it fixed, the wording reads of changing the old default value of 200k to 400k. Letting you know that yes, 200k was the current default.

                                  What I am also thinking is that maybe some add on packages, like pfblocker or snort etc., change this default value to a higher number based off the nature of what new rules they will likely need. This is purely speculative.

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

                                    @Bili_boy:

                                    The thing I don't understand is why it was 200K for you by default in the first place. I'm still on 2.3.4 and my default for "Firewall Maximum Table Entries" is 2M. (2 000 000). Did they reduce the default on purpose ?

                                    I've wondered the same thing.  I'm on 2.4.3 and the default for "Firewall Maximum Table Entries" is 2M (2,000,000) on my system.  I upgraded from 2.4.2 p1 but I don't remember what it was then and I don't remember ever changing it.  Not sure where all these people are getting that their system has 200K as default.

                                    1 Reply Last reply Reply Quote 0
                                    • cybrnookC
                                      cybrnook
                                      last edited by

                                      @jdeloach:

                                      @Bili_boy:

                                      The thing I don't understand is why it was 200K for you by default in the first place. I'm still on 2.3.4 and my default for "Firewall Maximum Table Entries" is 2M. (2 000 000). Did they reduce the default on purpose ?

                                      I've wondered the same thing.  I'm on 2.4.3 and the default for "Firewall Maximum Table Entries" is 2M (2,000,000) on my system.  I upgraded from 2.4.2 p1 but I don't remember what it was then and I don't remember ever changing it.  Not sure where all these people are getting that their system has 200K as default.

                                      what additional packages do you have installed?

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

                                        @cybrnook:

                                        @jdeloach:

                                        @Bili_boy:

                                        The thing I don't understand is why it was 200K for you by default in the first place. I'm still on 2.3.4 and my default for "Firewall Maximum Table Entries" is 2M. (2 000 000). Did they reduce the default on purpose ?

                                        I've wondered the same thing.  I'm on 2.4.3 and the default for "Firewall Maximum Table Entries" is 2M (2,000,000) on my system.  I upgraded from 2.4.2 p1 but I don't remember what it was then and I don't remember ever changing it.  Not sure where all these people are getting that their system has 200K as default.

                                        what additional packages do you have installed?

                                        I only have the APC UPS Daemon package installed.  Everything else is just the default install.  I don't have any of the other packages like PfBlockerNG, Squid or Squidguard installed.

                                        1 Reply Last reply Reply Quote 0
                                        • cybrnookC
                                          cybrnook
                                          last edited by

                                          @jdeloach:

                                          @cybrnook:

                                          @jdeloach:

                                          @Bili_boy:

                                          The thing I don't understand is why it was 200K for you by default in the first place. I'm still on 2.3.4 and my default for "Firewall Maximum Table Entries" is 2M. (2 000 000). Did they reduce the default on purpose ?

                                          I've wondered the same thing.  I'm on 2.4.3 and the default for "Firewall Maximum Table Entries" is 2M (2,000,000) on my system.  I upgraded from 2.4.2 p1 but I don't remember what it was then and I don't remember ever changing it.  Not sure where all these people are getting that their system has 200K as default.

                                          what additional packages do you have installed?

                                          I only have the APC UPS Daemon package installed.  Everything else is just the default install.  I don't have any of the other packages like PfBlockerNG, Squid or Squidguard installed.

                                          interesting. My install was just a vanilla 2.4.3. as soon as the config wizard was done, the error was already there.

                                          1 Reply Last reply Reply Quote 0
                                          • K
                                            karlfife
                                            last edited by

                                            Am I losing my mind?

                                            I just updated another 2.4.2 system to 2.4.3, but noticed the new default is 400,000 entries whereas this thread started because the default was 200,000 entries just yesterday.  "Ah, they did a minor point-release and updated the default" I reasoned.

                                            However, when I went to the machines that I'd manually overridden from 200,000 to 400,000 I noticed that their defaults had also changed, even though they have not been updated (i.e. via point-release).  Huh?  Aren't the defaults hard-coded into the release?

                                            What I've seen here would be more consistent with the defaults being periodically fetched from somewhere.    Is that true?

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