No ASN shown in reports any longer

manilx

Hi

I just found out that the ASN of blocked IP's are no longer shown in the reports. I'm on 23.05.1 pfsense+ and pfblocker-ng 3.2.0_6.

This has worked in the past but as I didn't have a look at the reports for quite some time I can't tell when this started happening.

I see DNS requests on nextDNS for "api.bgpview.io" all the time...
I also have ASN Reporting set to on.

Any idea?

manilx

Running an Update-reload I also now find the following:

[ Manually_blocked_Domains_custom_v4 ] Reload
  Downloading ASN: 202425... completed
parse error: Invalid numeric literal at line 1, column 10
  Downloading ASN: 207812... completed
parse error: Invalid numeric literal at line 1, column 10
  Downloading ASN: 50360... completed
parse error: Invalid numeric literal at line 1, column 10
  Downloading ASN: 204428... completed
parse error: Invalid numeric literal at line 1, column 10
  Downloading ASN: 202425... completed
parse error: Invalid numeric literal at line 1, column 10
  Downloading ASN: 207812... completed
parse error: Invalid numeric literal at line 1, column 10
  Downloading ASN: 44446... completed
parse error: Invalid numeric literal at line 1, column 10
  Downloading ASN: 207812... completed
parse error: Invalid numeric literal at line 1, column 10
  Downloading ASN: 398324... completed
parse error: Invalid numeric literal at line 1, column 10
  Downloading ASN: 207812... completed
parse error: Invalid numeric literal at line 1, column 10
  Downloading ASN: 202425... completed
parse error: Invalid numeric literal at line 1, column 10
  Downloading ASN: 23528... completed
parse error: Invalid numeric literal at line 1, column 10
  Downloading ASN: 29470... completed
parse error: Invalid numeric literal at line 1, column 10
 . completed ..

This is also new, I haven't changed anything in my config.

Bob.Dig

@manilx It is a known problem.

manilx

@Bob-Dig OK.....

There is a patch mentioned "curl -o /usr/local/pkg/pfblockerng/pfblockerng.sh "https://gist.githubusercontent.com/BBcan177/1c1fee14759bc574350a3bc85b63a57e/raw"

Should I apply this? Run from the pfsense CLI I suppose?

jrey

@manilx said in No ASN shown in reports any longer:

Should I apply this?

you would still need to modify that file at line ~ 761 in order to get the download to get new/updated data. It will stop the error from appearing in the log file, however.

manilx

@jrey I applied the original patch and started getting ASN entries in thr report. So some advance.

Guess will have to wait for the dev to completely fix this.