pfBlockerNG-devel 3.0.0_3 DNSBL alerts no longer showing source IP

[Mr_JinX]

I've just updated to the latest release and noticed under the reports and alerts its no longer displaying the source IP that generated an alert,

The bottom two rows are pre upgrade.

[fireodo]

@mr_jinx
Hi,
as I have read this should be normal if you are in Unbound Python Mode.

Regards,
fireodo

[provels]

@mr_jinx
Is this the page you're referring to? This, mine on 3.0.0_2 on Python.

[fireodo]

@provels said in pfBlockerNG-devel 3.0.0_3 DNSBL alerts no longer showing source IP:

@mr_jinx
Is this the page you're referring to? This, mine on 3.0.0_2 on Python.

No. mr_jinx is meaning this: "DNSBL Block- Last 50 Alert Entries"

[provels]

@fireodo
OK, found. I see a mix of Unknown and IPs on my 3.0.0_2 version using Python.

[Mr_JinX]

@fireodo your right, I changed it back to unbound mode and i can now see the source IP being logged.

[mind12]

@mr_jinx you can also leave python mode enabled and tick this to have alerts

[Paint]

@mind12 said in pfBlockerNG-devel 3.0.0_3 DNSBL alerts no longer showing source IP:

@mr_jinx you can also leave python mode enabled and tick this to have alerts

I have DNSBL Event Logging enabled with the pfBlockerNG python module filtering enabled. It seems like this fixes the issue for HTTP requests, but HTTPS requests still show up as unknown.

Is there anyway to fix this while still using the pfBlockerNG python module?

How do we change the SSL certificate used for pfBlockerNG with the python module? Perhaps that is the issue since the machines on my LAN show all DNSBL rejections/redirects as an invalid SSL certificate

[Paint]

I am running Version 2.4.5-RELEASE-p1 and pfBlocker DEVEL 3.0.0_3