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

prbecker · Apr 8, 2018, 11:02 PM

I'd like to thank you all as well for explaining this! Very helpful in resolving this issue.

Smoothrunnings · Apr 8, 2018, 11:16 PM

I guess the big question here is why?

Why do we need to increase the Firewall Maximum Table Entries from 200k (default) to 500k all of a sudden? I have been running pfSense a long time and have never had to make this change. So what changed all of a sudden?

It's great there is a solution but there isn't any real explanation as to why we have to change this value?

Thanks,

Derelict · Apr 8, 2018, 11:38 PM

The size of the IPv6 bogons table in the April update changed and pushed some systems over the edge.

The default has been changed to 400000 in 2.4.4

The timing of the bogons table monthly update and the release of 2.4.3 was simply coincidental.

AR15Dude · Apr 9, 2018, 1:43 PM

I'm confirming that after I upgraded from 2.4.2_1 to 2.4.3, I had the same type of error:

Filter Reload
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-09 09:15:46

Changing the Firewall Maximum Table Entries from 200000 to 500000 and rebooting solved the problem.

epalzeolithe · Apr 9, 2018, 7:04 PM

Tricky situation

if increase the maximum entries size from 200k to 400k, then rules modification and filters reload work without need of reboot
BUT, then i lose all my bandwidth, coming from 140Mb/s to 1Mb/s
if i use back 200k instead of 400k, then i have the bug back, but my bandwidth is back to 140mb/s !!!

What the hell is that issue ???

pl0ink · Apr 9, 2018, 11:38 PM

I have the same problem, even increased to 4,000,000, it does not make the error go away.
Tried several values, increasing from default (listed as 200,000) to current 4,000,000 with reboots.

Only solution i have for now is to "uncheck" the allow IPv6 Traffic in the System / Advanced / Networking section.
No more errors.
So i guess the bogonsv6 data is not loaded now?

Have run PFSense for years without problems, 4 physical interfaces configured with about 10 VLANS, reasonable amount of rules, aliases etc.
Should i continue to increase the number and try? 4,000,000 already seems excessive.

Derelict · Apr 10, 2018, 12:19 AM

Your experience does not mirror countless others.

Are you sure you are changing maximum table entries and not maximum states? They are completely different things.

pl0ink · Apr 10, 2018, 12:35 AM

yes, i'm sure, did not touch the default for Max Firewall States.

![Screen Shot 2018-04-10 at 02.32.01.png](/public/imported_attachments/1/Screen Shot 2018-04-10 at 02.32.01.png)
![Screen Shot 2018-04-10 at 02.32.01.png_thumb](/public/imported_attachments/1/Screen Shot 2018-04-10 at 02.32.01.png_thumb)

Derelict · Apr 10, 2018, 1:04 AM

Zero reason for 4,000,000 there. Try 400000. Maybe you are really running out of RAM at 4,000,000.

It really is working for everyone but you.

pl0ink · Apr 10, 2018, 1:51 AM

Well, solved it, but don't understand.

Did at least 10 WebGUI reboots, system did really reboot, but kept having the problem.
Finally did a complete system shutdown, removed power and restarted, problem is gone.

After that I changed the 4,000,000 back to 400,000 as you suggested and it still works.
(i had previously increased in increments 200K, 400K, 800K etc, did not change a thing)

so, weird but solved, thanks for your help. :)

CNLiberal · Apr 13, 2018, 3:21 AM

My buddy is having this exact same issue on a fresh 2.4.3 install on a Dell R210 II with E3-1320 v2. He has the bogons error, and when we changed it to 400,000 the error went away, but his internet speed TANKED. I'll tell him to leave it at 400,000 and to save and restart. If that doesn't work, shutdown, pull power and pop it back in. I have no idea why it would be different between the two options, except one is setting run level 6, the other run level 0.

Derelict · Apr 14, 2018, 12:08 AM

I suppose it's possible there is an issue with processing the tables if the table size is increased but I have not seen it. In any case a simple reboot should fix it. That is strange.

CNLiberal · Apr 15, 2018, 3:24 AM

My buddy was able to change the Max Table Entries to 400k and rebooted. His slowness went away. However, he still want receiving the same 250Mb down that he was getting on speedof.me. We tried a different speed test site (Comcast's as that's his ISP) and he was receiving 400Mbps. We confirmed this with the interfaces traffic graph on the dashboard.

This seems like a bad bug. Netgate should think about issueing a p1 immediately to fix this issue along with new install media. My friend nearly gave up on pfSense. I convinced him otherwise, but for a complete newbie with no one to go to, this could be a deal breaker.

cybrnook · Apr 15, 2018, 3:15 PM

It should be taken care of in the next release.

CNLiberal · Apr 16, 2018, 3:53 PM

I understand that it should be, but it seems like a large bug if a fresh install kicks the error, but also causes very slow speeds. A fresh install should just work. Seems like a simple thing for Netgate to do. Not to mention it being the right thing to do.

cybrnook · Apr 16, 2018, 3:57 PM

Well keep in mind this isn't really an issue with the build itself. It's caused from the fact the bogons file (which gets downloaded) has now just barely exceeded the default 200k allocation.

While I agree with you that it's frustrating, and it caught me on a fresh install as well, it's not just specific to 2.4.3. It "should" be happening on all older releases as well that are downloading updated bogons and still have the default 200K value.

I assume for the dev's to come and issue a single commit to the exist 2.4.3 release branch, recompile, and then re-upload, they are likely just going to address in the next point release, which hopefully isn't too far behind. Something like a 2.4.3_p1 release.

I think it's just timing that the updated, larger bogons file came into play at the same time 2.4.3 was released.

Speed wise, I will say I have not seen a single issue as far as my bandwidth is concerned after updating to 400K (the new upcoming default), you are the first to say anything like that. I see my full 500Mbps down and 50Mbps up, consistently.

purdue512 · Apr 23, 2018, 12:24 PM

Confirmed - We started getting these errors in the last few weeks out of nowhere, no config changes on

2.3.2-RELEASE-p1 (amd64)

l0rdraiden · Apr 29, 2018, 11:15 AM

I still get 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"
@ 2018-04-29 13:12:47

And I have alread set Firewall Maximum Table Entries to 400000
and do the reload filters.

Why?

CNLiberal · Apr 29, 2018, 3:44 PM

Have you rebooted?

l0rdraiden · Apr 29, 2018, 4:10 PM

@joltman:

Have you rebooted?

Yes, in addition I have found that If I go to "System/General Setup" and click save without changing anyting it appears again.
Does it make any sense?

Ops it looks like there was an empty space after the 400000