urgent help needed pi hole docker compose installation, gone wild
hi I’m hoping someone can help me with this. Yesterday try to install pi hole exactly according to the instructions on Firewalla. I ran the original set up through Dr compose, upgraded to DOH, although that may not have even started, and then, when I try to restart Firewalla, realizing there were issues pi did not come back so there may be a persistence issue
however, this is not my real problem Realizing there were some very strange resolutions of the DNS, and before you given understanding how this thing works, I saw that firewalla had a client which was local and with DNS 127.0.0.1. now I may be mistaken, but I think this is Firewalla’s DNS? in any case I was getting resolutions that did not make any sense, and on the pi itself
it seems like a lot of the quarries from Firewalla if not all we’re going through there
after restarting the whole system, I am not getting pi back, however, DNS resolutions are still making no sense and worse the Netwerk 127.0.0.1/24 is completely exposed to any client and Firewalla in the Netwerk scan reveals multiple Singapore Ips, and even ones web interface, which I believe is related to Firewalla tools.
I can’t seem to get Firewalla tech-support to do anything about this and I am concerned about the security of my system hoping someone can take a look at this and help me. I am not experienced at all with doctors, but I did try to follow the directions carefully. I’m attaching some screenshots before pi was no longer accessible and after with a scan of the net work and hopefully I can get some help here
thanks a lot and in advance
ps new device just join the network that was supposed to be on quarantine and is not limited nor visible on Firewalla. Firewalla dhcp DNS does not exist practically I don’t know what to do.
see attached
https://www.dropbox.com/sh/6fdzfwajz9hu4uz/AAA-sPMAo9V6ZQqt82ofde5Ca?dl=0
Please sign in to leave a comment.
Comments
0 comments