I’m looking for Little Snitch users here, not really a Pi-hole problem.
I use LS in parallel to Pi-hole to restrict traffic whenever I’m on the road (or at a client) where there’s no Pi-hole.
In the Pi-hole log and Dashboard I get lots of inspiration of what to add to LS.
And there is my problem:
In the Pi-hole log I see: ads.spam.it
Pi-hole blocks it by returning its own IP, say: 192.168.1.1
Now I want to add a rule in LS to block ads.spam.it.
But as soon as I enter “ads.spam.it” to LS, it is resolved to the local IP of the Pi-hole server, thus
a) effectively blocking my access to the Pi-hole dashboard (since LS then block access to 192.168.1.1) and
b) not working when I am in a different environment (since 192.168.1.1 is not the real address of ads.spam.it).
I’ve tried to deactivate Pi-hole for the time while I create the rule in LS. Did not work.
I’ve tried the above and in addition cleared my arp cache (sudo arp -d -a). Did not work.
I am able to add the rule to LS properly when outside my own network, but thats not the solution.
How do you guys/gals add new rules to LS while Pi-hole is working its magic? Any solution?