pfBlockerNG_devel commit reverse

incith

Maybe this? Not the one I'm trying to remove (it's already unchecked that is), but maybe it's parsing through it.

jrey

that would are my guess, but sorry no way for me to troubleshoot this case specifically- it just "looks" like a similar issue to me.

if you want to see a similar error (where the config gets restored) on the ASN side
create or go to a list you already have with ASN data items (assuming you are using ASNs somewhere and have ipinfo.io up and running)

simply try to add (any ASN that contains international characters in the name) and save the list. the data won't be saved and it will "restore" the config.

the new ipinfo data ASN names contain these, the old bgpview ASN data did not.

here are a couple samples (with the new ASN data) that will cause it to fail.. (of course there are many more)

AS29571
AS273867

BBcan177

Ok there is a bug and it will be fixed in the next upcoming version.

https://github.com/pfsense/FreeBSD-ports/commit/3586bb086db9a1ff7dcddc3e2e30605ecac99796

This can be applied by the System Patches package using the commit ID and setting "Path Strip Count" to 4.

Or you can edit /usr/local/www/pfblockerng.php and change the single quotes to a double quote as per the commit above.

Once that has been patched, you can run this command to rebuild the GeoIP pages:

php -f /usr/local/www/pfblockerng/pfblockerng.php dc

incith

@BBcan177 Works great, thank you!

TommyMoo

Updated today pfblocker devel to version 3.2.0_19, all went well, no problem. Thank you very much, my impression is, that it gained some speed compared to previous version & Thanks for bugfixes

BBcan177

@TommyMoo

Thanks for reporting.

More info here:

https://www.reddit.com/r/pfBlockerNG/s/4Yrr4ffq3I

tman222

@BBcan177 said in pfBlockerNG_devel commit reverse:

@TommyMoo

Thanks for reporting.

More info here:

https://www.reddit.com/r/pfBlockerNG/s/4Yrr4ffq3I

Hi @BBcan177 - thanks for this new version; the install went smoothly. I have a quick question about the release: I see that in the release notes that setting the ASN Cache setting is no longer required. Does this mean that under IP -> ASN Configuration -> ASN Reporting, we can now choose "Disabled" and everything will continue download / work fine as before? If yes, what would be the purpose of the ASN Reporting field, i.e. when it would be useful to still enable the cache setting? Could this field be removed altogether now that the switch IPinfo has occurred? Thanks in advance.

BBcan177

@tman222

Yes you can set that to disabled and it will still download OK. That setting was more useful with BGPview, but I would still recommend to set it to atleasy 1 hour as it might give a small micro performance boost.

tman222

@BBcan177 said in pfBlockerNG_devel commit reverse:

@tman222

Yes you can set that to disabled and it will still download OK. That setting was more useful with BGPview, but I would still recommend to set it to atleasy 1 hour as it might give a small micro performance boost.

Thanks @BBcan177. Since the IPinfo ASN data is updated only once every 24 hours, do you see any additional advantage to increasing that ASN cache setting from 1 hour to e.g. 4 or 12 hours? Thanks again.

TommyMoo

Updated pfBlocker devel from 3.2.0_19 to 3.2.0_20 ..all good (on x86 qemu), GEOIP / ASN entrys etc. all working well, Thank you for the Update!