Re: [pfSense] 2.4.3 - cannot define table bogonsv6
On 04/19/2018 04:54 AM, Eero Volotinen wrote: > fix is in reddit thread .. > > Someone should fix this on pfsense default config.. It has been fixed for over two weeks in the repo: https://redmine.pfsense.org/issues/8417 There have been numerous threads about it on the forum, reddit, and elsewhere. Jim P. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.4.3 - cannot define table bogonsv6
fix is in reddit thread .. Someone should fix this on pfsense default config.. Eero On Thu, Apr 19, 2018 at 11:53 AM, mayakwrote: > On 04/19/2018 10:33 AM, Fabian Bosch wrote: > >> Same here on v*2.3.3 *and even after update to v*2.4.3 >> *Any news on this?* >> * >> >> >> Am 02.04.2018 um 05:04 schrieb 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.. >>> Travis hansentravisghan...@yahoo.com >>> >> 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 bogonsv6 persist file /etc/bogonsv6 > -- > > 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 > ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.4.3 - cannot define table bogonsv6
On 04/19/2018 10:33 AM, Fabian Bosch wrote: Same here on v*2.3.3 *and even after update to v*2.4.3 *Any news on this?* * Am 02.04.2018 um 05:04 schrieb 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.. Travis hansentravisghan...@yahoo.com 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 bogonsv6 persist file /etc/bogonsv6 -- 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
Re: [pfSense] 2.4.3 - cannot define table bogonsv6
Sounds like a bug: https://www.reddit.com/r/PFSENSE/comments/88ry96/there_were_errors_loading_the_rules/ Eero On Thu, Apr 19, 2018 at 11:33 AM, Fabian Boschwrote: > Same here on v*2.3.3 *and even after update to v*2.4.3 > *Any news on this?* > * > > regards, > > Fabian > > Am 02.04.2018 um 05:04 schrieb 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.. >> Travis hansentravisghan...@yahoo.com >> >> >> On Sunday, April 1, 2018, 5:35:32 PM MDT, Victor Padro < >> vpa...@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. >> >> On Sun, Apr 1, 2018 at 5:25 PM, Olivier Mascia wrote: >> >> Thanks Victor, >>> >>> On Sun, Apr 1, 2018 at 4:46 PM, Olivier Mascia wrote: 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 persist file "/etc/bogonsv6" > > Is there a known bug/quirk at work here? > >>> Le 2 avr. 2018 à 01:05, Victor Padro a écrit : Change the value of the Firewall Maximum Table Entries to 50 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 >>> >>> ___ >>> 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 > ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.4.3 - cannot define table bogonsv6
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 hansentravisghan...@yahoo.com On Sunday, April 1, 2018, 5:35:32 PM MDT, Victor Padrowrote: 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. On Sun, Apr 1, 2018 at 5:25 PM, Olivier Mascia wrote: > Thanks Victor, > > > On Sun, Apr 1, 2018 at 4:46 PM, Olivier Mascia wrote: > > > >> 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 persist file "/etc/bogonsv6" > >> > >> Is there a known bug/quirk at work here? > > > > Le 2 avr. 2018 à 01:05, Victor Padro a écrit : > > > > Change the value of the Firewall Maximum Table Entries to 50 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 > > ___ > 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 ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.4.3 - cannot define table bogonsv6
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. On Sun, Apr 1, 2018 at 5:25 PM, Olivier Masciawrote: > Thanks Victor, > > > On Sun, Apr 1, 2018 at 4:46 PM, Olivier Mascia wrote: > > > >> 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 persist file "/etc/bogonsv6" > >> > >> Is there a known bug/quirk at work here? > > > > Le 2 avr. 2018 à 01:05, Victor Padro a écrit : > > > > Change the value of the Firewall Maximum Table Entries to 50 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 > > ___ > 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
Re: [pfSense] 2.4.3 - cannot define table bogonsv6
Thanks Victor, > On Sun, Apr 1, 2018 at 4:46 PM, Olivier Masciawrote: > >> 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 persist file "/etc/bogonsv6" >> >> Is there a known bug/quirk at work here? > Le 2 avr. 2018 à 01:05, Victor Padro a écrit : > > Change the value of the Firewall Maximum Table Entries to 50 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 ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.4.3 - cannot define table bogonsv6
Change the value of the Firewall Maximum Table Entries to 50 in System | Advanced | Firewall & NAT On Sun, Apr 1, 2018 at 4:46 PM, Olivier Masciawrote: > 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 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" ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold