Firewalla Gold - PiHole - my ip or follow verbatim?
I currently have pihole running as a virtual and thinking it would be nice to have a self contained environment where if my host is down my network isn't.
https://help.firewalla.com/hc/en-us/articles/360051625034
Based on the above instruction it references
You have to choose
- a network as your docker network, we use 172.16.0.0/24 in this tutorial
- a static IP for your pi-hole instance, we use 172.16.0.2 in this tutorial
Should I be following that or if my network router IP is 192.168.11.1 I would change 172.16.0.0/24 to 192.168.11.0/24 and 172.16.0.2 to 192.168.11.2?
For me I went with 192.168.11.42 and in theory the docker started and says up to date, but I can't access the page using that IP. So not sure what I missed. Maybe I need to delete the docker, not sure how though can probably find documentation and start over with the referenced IP address.
Edit: Best I can tell the pihole container is running, (sudo docker stats - shows it running and using resources) but a device never comes online with the ip I've defined or any as far as I can tell. I'm not sure how to troubleshoot further.
-
This is something I have been contemplating as well.
And answer would be greatly appreciated, unless it is answered elsewhere. A link would be great.
I currently have a PiHole running in a docker on my QNAP NAS in Container Station and I read it would reduce a hop if used on Firewalla. But I would like wo know these details first.
-
Any tips from the community on what I can look at to determine why the docker pihole is not online/reachable? I can run sudo docker stats and pihole is listed as using CPU and memory, even has NET I/O, but I can not hit the IP address I assigned (192.168.11.48) from my network so I'm not sure what I'm missing.
Using PING I can not ping the address from Windows or SSH while connected into Firewalla so I must have done something wrong to break it or not open up the network correctly but I am not sure what.
Please sign in to leave a comment.
Comments
4 comments