<story><title>WireHole: Set up Pihole, WireGuard, and Unbound instantly</title><url>https://github.com/IAmStoxe/wirehole</url></story><parent_chain></parent_chain><comment><author>kd913</author><text>I can understand the benefit of automating these things but I think it would probably be better for people to setup these things manually first. At least to understand what each step is doing. Otherwise, people are trusting rather a core piece of infrastructure with a random docker image online.&lt;p&gt;I found personally that there are several aspects of this automation that needs tweaking.&lt;p&gt;* If you need ipv6 support this config needs to be overhauled.&lt;p&gt;* Wireguard config should have ipv6 addresses set to avoid potential leakages (even if ipv6 is disabled).&lt;p&gt;* This setup would benefit from some ddns mechanism as most people do not have static ip setups.&lt;p&gt;* Firefox is beginning to have https only modes in which case maybe I would like to adjust lighthttp to work with that.&lt;p&gt;The list goes on.</text></comment>
<story><title>WireHole: Set up Pihole, WireGuard, and Unbound instantly</title><url>https://github.com/IAmStoxe/wirehole</url></story><parent_chain></parent_chain><comment><author>matrixagent</author><text>If I&amp;#x27;m reading the docker-compose file correctly, this creates an open dns resolver that is accessible to the outside, as Docker by default bypasses the firewall, see &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;chaifeng&amp;#x2F;ufw-docker&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;chaifeng&amp;#x2F;ufw-docker&lt;/a&gt;. I&amp;#x27;m not quite sure about that, though, so I&amp;#x27;d be happy to be corrected and learn more about how your setup works exactly.</text></comment>