parse error: Invalid numeric literal at line 1, column 10

pftdm007 · Apr 6, 2022, 12:45 AM

Hello,

Out of the blue, pfblockerNG ver 3.1.0_4 started spitting out parse errors when updating the ASN's from IPv4:

Downloading ASN: XXXX... completed
parse error: Invalid numeric literal at line 1, column 10
Downloading ASN: XXXX... completed
parse error: Invalid numeric literal at line 1, column 10
Downloading ASN: XXXX... completed
parse error: Invalid numeric literal at line 1, column 10
Downloading ASN: XXXX... completed
parse error: Invalid numeric literal at line 1, column 10

I remember this problem in the past but if my memory serves me well, there was a bug in pfblockerNG and latest version needed to be installed. However I have the latest version so how to debug this?
FYI I am running pfsense 2.6.0

mbentley · Apr 7, 2022, 10:17 PM

I'm seeing the same after upgrading to 3.1.0_4. Did you find a workaround or fix by chance?

pftdm007 · Apr 7, 2022, 11:54 PM

@mbentley

I am no longer seeing this at this moment but I'm sure it will come back soon. Not sure why. I'll keep an eye on this.

mbentley · Apr 8, 2022, 12:26 AM

Ah, looks like the ASN source is returning errors right now. For example: https://api.bgpview.io/asn/6161/prefixes returns a 500 server error.