<![CDATA[parse error: Invalid numeric literal at line 1, column 10]]>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

]]>https://forum.netgate.com/topic/171355/parse-error-invalid-numeric-literal-at-line-1-column-10RSS for NodeWed, 11 Mar 2026 01:46:53 GMTWed, 06 Apr 2022 00:45:11 GMT60<![CDATA[Reply to parse error: Invalid numeric literal at line 1, column 10 on Fri, 08 Apr 2022 00:26:13 GMT]]>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.

]]>https://forum.netgate.com/post/1036812https://forum.netgate.com/post/1036812Fri, 08 Apr 2022 00:26:13 GMT<![CDATA[Reply to parse error: Invalid numeric literal at line 1, column 10 on Thu, 07 Apr 2022 23:54:29 GMT]]>@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.

]]>https://forum.netgate.com/post/1036807https://forum.netgate.com/post/1036807Thu, 07 Apr 2022 23:54:29 GMT<![CDATA[Reply to parse error: Invalid numeric literal at line 1, column 10 on Thu, 07 Apr 2022 22:17:07 GMT]]>I'm seeing the same after upgrading to 3.1.0_4. Did you find a workaround or fix by chance?

]]>https://forum.netgate.com/post/1036797https://forum.netgate.com/post/1036797Thu, 07 Apr 2022 22:17:07 GMT