DNSBL Service Wont Start

usaiat

I have the following version 2.7.2 and pfBlockerNG-devel 3.2.0_7 and Im not able to start the pfb_dnsbl services

The following subnets are configured on the interfaces
LAN - 10.1.85.1/24
OPT1 - 10.1.86.1/24
vti0 - 10.11.1.146/30

Could it be that my Virtual IP Address on the DNSBL Webserver Configuration is on the default i.e 10.10.10.1 ?? Should I change this ?

Gertjan

@usaiat

The 10.10.10.1 isn't overlapping with your other networks.

Can you check up with your system why there is an issue :

Check all the log files.

A test :

and under Action, disable your DNSBL.
Then activate them one by one, and do a force reload every time.
As soon as you have a failure, you know what to stop loading.

usaiat

@Gertjan Thanks for the response. So this ip address 10.10.10.1 is just a /32 address ?
I note the notes under this settings which says "This address should be an Isolated range that is not already used in the network"

Then below it shows the RFC918 compliant range which has 10.0.0.0/8. If this is the case then all my IP address spefified with the 10.10.10.1 falls under that range.

Gertjan

@usaiat said in DNSBL Service Wont Start:

10.0.0.0/8

That's ok.
Like me, I'm using 192.168.1.0/24 as my LAN, and a second LAN with 192.168.2.0/24.0
The total available space is 192.168.0.0/16 which means I can pick 255 networks (from x.x.0.0 to x.x.255.0 with a size of 255 (/24))

Did you find anything in the logs ?

Also when you installed pfBlocker, the service was running - as I presume one small (!) DNSLBL is/was already present.
Then you started adding other DNSBL and / or change DNSBL settings.
Then the service started to not working anymore.
Knowing how to 'undo' things is now as important as knowing how to 'do' things. By going back, you'll find the point of failure.

usaiat

@Gertjan Got it thanks. Yeah it could be when I did add in another list on the DNSBL Groups apart from the default one. Ill see if I can diable that list and see how it goes

usaiat

This is working now. I believe I must have mucked it up while the cron job was running I must have tried to reload it again.