2.5.0 no love for Unbound python mode

BBcan177

@chudak
When you first enabled Unbound Python Mode, you could only do that if DHCP Registration was disabled.
My suspicion, is that after Unbound Python Mode was enabled, you manually re-enabled the DHCP Registration option in the DNS Resolver.
So when the code sees that DHCP Registration is enabled, it will terminate Python mode.

chudak

@bbcan177

Possibly but then I should be able to make it right, but I do:

Make sure Unbound has DHCP Registration is disabled => Save, Apply
Restart Unbound
Enable DNSBL Python mode
+
Restart DNSBL and then Unbound
Or
Other way around, but DNSBL Python mode still shows error !

:(

RonpfS

@chudak said in 2.5.0 no love for Unbound python mode:

Make sure Unbound has DHCP Registration is disabled => Save, Apply
Restart Unbound
Enable DNSBL Python mode

Save, Apply should restart Unbound.

After Enabling DNSBL Python Mode, do a Force Update, monitor pfblockerng.log at the end of DNSBL processing.

chudak

@ronpfs

Same result

RonpfS

@chudak maybe post the log.

BBcan177

Where are you enabling Unbound Python Mode? That needs to be enabled in the pfBlockerNG package > DNSBL Tab. Do not touch the setting in the Resolver as those are managed by the package.

chudak

@bbcan177

Here :

BBcan177

@chudak
So when you hit save in the pfBlockerNG package, do you get a warning about DHCP Registration being enabled? Or when you Force Update?
Have you rebooted this box?

RonpfS

@bbcan177 Also do you see dhcp leases in DHCP server log? Does that trigger Unbound reload ?

BBcan177

@ronpfs He has Static DHCP enabled, so that doesn't reload Unbound.

RonpfS

@bbcan177 DHCP service will issue new leases if the device is not in Static map.

chudak

@bbcan177 said in 2.5.0 no love for Unbound python mode:

@chudak
So when you hit save in the pfBlockerNG package, do you get a warning about DHCP Registration being enabled? Or when you Force Update?
Have you rebooted this box?

I get no warning, but again it’s not enabled
I see the yellow icon on the dashboard and error in the log.

Again, I was running Unbound python mode with DHCP Registration disabled for awhile on 2.4.5 (after you warned to disable it via Twitter or in the release notes) and had no issues.

All this is new in 2.5.0 since I upgraded today.
And yes, the box was rebooted multiple times today.

The only thing I didn’t do - remove and reinstall pfB

Will that help ?

Thx

PS - it runs fine without python mode too

chudak

@BBcan177

Well, did a clean reinstall today and - Unbound python mode love is back !
What was it ? No clue, suspect that package updates did not worked well after 2.5.0. upgrade.

Thanks all !