error(s) loading the rules: table name too long
-
I got this error after upgrading a existing sg1100. I removed the old version of pfblocker and installed the devel version. Only enabled feeds DNS steven black ads and PRI1 IPv4 except pulsdive. I got one of these after I did the upgrade and a barrage of five of them just now three days later. I have no idea what's wrong or what I should do about this, anyone have an idea?
Filter Reload There were error(s) loading the rules: /tmp/rules.debug:31: table name too long, max 31 chars - The line in question reads [31]: table <pfB_EmergingThreatsCompromised_v4> persist file "/var/db/aliastables/pfB_EmergingThreatsCompromised_v4.txt" @ 2022-08-28 07:05:25 -
Still getting bombarded with these.
-
@maxburn I've not run into that. It reads that "pfB_EmergingThreatsCompromised_v4" is too long, which is right if the limit is 31. On your pfBlockerNG/IP/IPv4 page can you edit the list to change the "name" field to something shorter? Then run an update, and you may need to update rules that use that name. For me that list and others are under a "PRI1" entry (which was a default name for feeds in that section).
-
@maxburn I'm looking for the exact text pfB_EmergingThreatsCompromised_v4.txt and I'm not finding it. But the helper description restrictions makes me think the prefix and suffix are added behind the scenes to the name field? Also the character total limit there plus the prefix and suffix is 31. I shortened that down, hope that does it.
-
@maxburn said in error(s) loading the rules: table name too long:
helper description restrictions makes me think the prefix and suffix are added behind the scenes to the name field?
Yes, that's the case, and that's the spot. It actually does say "Max 24 characters" but doesn't try to enforce that.
-
@maxburn Thanks.
It's odd I'm experiencing this and everyone else isn't. I didn't type that in, apparently that's the default it applies when you turn on that list?
Does no one else run the IP block lists? IMO that is a major strength of pfblocker over things like PiHole.
-
@maxburn Maybe because we check several at once so it defaults to the "PRI1" heading name? I've never had to change a name that I can recall. Dunno...
-
@steveits That didn't do it. I just got blasted with another ten of these. Is there something that needs to be reloaded or just a matter of time or something?
There were error(s) loading the rules: /tmp/rules.debug:31: table name too long, max 31 chars - The line in question reads [31]: table <pfB_EmergingThreatsCompromised_v4> persist file "/var/db/aliastables/pfB_EmergingThreatsCompromised_v4.txt" @ 2022-09-01 11:00:56I did verify that the change was saved.
-
@maxburn Did you force an update? That's what regenerates the files/tables/aliases.
-
@maxburn I didn't, but I just did. I was thinking it would do that itself based on the schedule. I see the new name in the update output and can't find the old one so hopefully that's the end of it.