Discussion:
[pfSense] 2.4.3 - cannot define table bogonsv6
Olivier Mascia
2018-04-01 22:46:27 UTC
Permalink
Since I have upgraded 2 HW box and 2 VMs to 2.4.3 I have started seeing such occasionally:

0:40:54 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"

Is there a known bug/quirk at work here?
--
Best Regards, Meilleures salutations, Met vriendelijke groeten,
Olivier Mascia
Victor Padro
2018-04-01 23:05:36 UTC
Permalink
Change the value of the Firewall Maximum Table Entries to 500000 in System
| Advanced | Firewall & NAT
Post by Olivier Mascia
0:40:54 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"
Is there a known bug/quirk at work here?
--
Best Regards, Meilleures salutations, Met vriendelijke groeten,
Olivier Mascia
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
--
"Everything that irritates us about others can lead us to an understanding
of ourselves"
Olivier Mascia
2018-04-01 23:25:10 UTC
Permalink
Thanks Victor,
Post by Victor Padro
Post by Olivier Mascia
Since I have upgraded 2 HW box and 2 VMs to 2.4.3 I have started seeing
0:40:54 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"
Is there a known bug/quirk at work here?
Change the value of the Firewall Maximum Table Entries to 500000 in System
| Advanced | Firewall & NAT
Indeed it then reloads filter cleanly. The default (empty) is said to be 200'000. So 500'000 is a large change from default. Is that the default is now highly underestimated and should/will be raised later or that this needs be significantly higher than default only because I use IPv6 and have Block logon networks checked?
--
Best Regards, Meilleures salutations, Met vriendelijke groeten,
Olivier Mascia
Victor Padro
2018-04-01 23:35:20 UTC
Permalink
Don't think so, since I'm not using IPv6 and the issue wasn't there in
version 2.4.2, looks to me it's something else, but haven't dug in deeper
since that occured to me early this morning and changing that value helped
me too, I saw that recommendation in the pfsense reddit site while
troubleshooting a reinstall I had to do urgently.
Post by Olivier Mascia
Thanks Victor,
Post by Victor Padro
Post by Olivier Mascia
Since I have upgraded 2 HW box and 2 VMs to 2.4.3 I have started seeing
cannot
Post by Victor Padro
Post by Olivier Mascia
define table bogonsv6: Cannot allocate memory - The line in question
reads
Post by Victor Padro
Post by Olivier Mascia
[22]: table <bogonsv6> persist file "/etc/bogonsv6"
Is there a known bug/quirk at work here?
Change the value of the Firewall Maximum Table Entries to 500000 in
System
Post by Victor Padro
| Advanced | Firewall & NAT
Indeed it then reloads filter cleanly. The default (empty) is said to be
200'000. So 500'000 is a large change from default. Is that the default is
now highly underestimated and should/will be raised later or that this
needs be significantly higher than default only because I use IPv6 and have
Block logon networks checked?
--
Best Regards, Meilleures salutations, Met vriendelijke groeten,
Olivier Mascia
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
--
"Everything that irritates us about others can lead us to an understanding
of ourselves"
Travis Hansen
2018-04-02 03:04:11 UTC
Permalink
I'm seeing this same issue on 2 separate 2.3.x boxes the last couple days as well that haven't been tampered with in ages.  Something strange going on for sure..
Travis ***@yahoo.com

On Sunday, April 1, 2018, 5:35:32 PM MDT, Victor Padro <***@gmail.com> wrote:

Don't think so, since I'm not using IPv6 and the issue wasn't there in
version 2.4.2, looks to me it's something else, but haven't dug in deeper
since that occured to me early this morning and changing that value helped
me too, I saw that recommendation in the pfsense reddit site while
troubleshooting a reinstall I had to do urgently.
Post by Olivier Mascia
Thanks Victor,
Post by Victor Padro
Post by Olivier Mascia
Since I have upgraded 2 HW box and 2 VMs to 2.4.3 I have started seeing
cannot
Post by Victor Padro
Post by Olivier Mascia
define table bogonsv6: Cannot allocate memory - The line in question
reads
Post by Victor Padro
Post by Olivier Mascia
[22]: table <bogonsv6> persist file "/etc/bogonsv6"
Is there a known bug/quirk at work here?
Change the value of the Firewall Maximum Table Entries to 500000 in
System
Post by Victor Padro
| Advanced | Firewall & NAT
Indeed it then reloads filter cleanly.  The default (empty) is said to be
200'000. So 500'000 is a large change from default.  Is that the default is
now highly underestimated and should/will be raised later or that this
needs be significantly higher than default only because I use IPv6 and have
Block logon networks checked?
--
Best Regards, Meilleures salutations, Met vriendelijke groeten,
Olivier Mascia
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
--
"Everything that irritates us about others can lead us to an understanding
of ourselves"
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
Fabian Bosch
2018-04-19 08:33:30 UTC
Permalink
Same here on v*2.3.3 *and even after update to v*2.4.3
*Any news on this?*
*

regards,

Fabian
Post by Travis Hansen
I'm seeing this same issue on 2 separate 2.3.x boxes the last couple days as well that haven't been tampered with in ages.  Something strange going on for sure..
Don't think so, since I'm not using IPv6 and the issue wasn't there in
version 2.4.2, looks to me it's something else, but haven't dug in deeper
since that occured to me early this morning and changing that value helped
me too, I saw that recommendation in the pfsense reddit site while
troubleshooting a reinstall I had to do urgently.
Post by Olivier Mascia
Thanks Victor,
Post by Victor Padro
Post by Olivier Mascia
Since I have upgraded 2 HW box and 2 VMs to 2.4.3 I have started seeing
cannot
Post by Victor Padro
Post by Olivier Mascia
define table bogonsv6: Cannot allocate memory - The line in question
reads
Post by Victor Padro
Post by Olivier Mascia
[22]: table <bogonsv6> persist file "/etc/bogonsv6"
Is there a known bug/quirk at work here?
Change the value of the Firewall Maximum Table Entries to 500000 in
System
Post by Victor Padro
| Advanced | Firewall & NAT
Indeed it then reloads filter cleanly.  The default (empty) is said to be
200'000. So 500'000 is a large change from default.  Is that the default is
now highly underestimated and should/will be raised later or that this
needs be significantly higher than default only because I use IPv6 and have
Block logon networks checked?
--
Best Regards, Meilleures salutations, Met vriendelijke groeten,
Olivier Mascia
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
Eero Volotinen
2018-04-19 08:41:24 UTC
Permalink
Sounds like a bug:
https://www.reddit.com/r/PFSENSE/comments/88ry96/there_were_errors_loading_the_rules/

Eero
Post by Fabian Bosch
Same here on v*2.3.3 *and even after update to v*2.4.3
*Any news on this?*
*
regards,
Fabian
Post by Travis Hansen
I'm seeing this same issue on 2 separate 2.3.x boxes the last couple days
as well that haven't been tampered with in ages. Something strange going
on for sure..
On Sunday, April 1, 2018, 5:35:32 PM MDT, Victor Padro <
Don't think so, since I'm not using IPv6 and the issue wasn't there in
version 2.4.2, looks to me it's something else, but haven't dug in deeper
since that occured to me early this morning and changing that value helped
me too, I saw that recommendation in the pfsense reddit site while
troubleshooting a reinstall I had to do urgently.
Thanks Victor,
Post by Victor Padro
Post by Olivier Mascia
Since I have upgraded 2 HW box and 2 VMs to 2.4.3 I have started seeing
cannot
define table bogonsv6: Cannot allocate memory - The line in question
reads
[22]: table <bogonsv6> persist file "/etc/bogonsv6"
Post by Olivier Mascia
Is there a known bug/quirk at work here?
Change the value of the Firewall Maximum Table Entries to 500000 in
System
Post by Olivier Mascia
| Advanced | Firewall & NAT
Indeed it then reloads filter cleanly. The default (empty) is said to be
200'000. So 500'000 is a large change from default. Is that the default is
now highly underestimated and should/will be raised later or that this
needs be significantly higher than default only because I use IPv6 and have
Block logon networks checked?
--
Best Regards, Meilleures salutations, Met vriendelijke groeten,
Olivier Mascia
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
mayak
2018-04-19 08:53:12 UTC
Permalink
Post by Fabian Bosch
Same here on v*2.3.3 *and even after update to v*2.4.3
*Any news on this?*
*
Post by Travis Hansen
I'm seeing this same issue on 2 separate 2.3.x boxes the last couple days as well that haven't been tampered with in ages.  Something strange going on for sure..
Same here:
3 APU boxes -- two running 2.3 and the other 2.4
1 Intel based pizza box running 2.4

All 4:
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 &lt;bogonsv6&gt; persist file &quot;/etc/bogonsv6&quot;
--
It's not what you look at that matters, it's what you see

— Henry David Thoreau
Eero Volotinen
2018-04-19 08:54:39 UTC
Permalink
fix is in reddit thread ..

Someone should fix this on pfsense default config..

Eero
Post by mayak
Post by Fabian Bosch
Same here on v*2.3.3 *and even after update to v*2.4.3
*Any news on this?*
*
Post by Travis Hansen
I'm seeing this same issue on 2 separate 2.3.x boxes the last couple
days as well that haven't been tampered with in ages. Something strange
going on for sure..
3 APU boxes -- two running 2.3 and the other 2.4
1 Intel based pizza box running 2.4
There were error(s) loading the rules: /tmp/rules.debug:22: cannot define
--
It's not what you look at that matters, it's what you see
— Henry David Thoreau
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
Loading...