Comment on The Beauty Of Having A Pi-hole · Den Delimarsky
normalexit@lemmy.world 4 weeks agoIf you have a server running, I wouldn’t buy more hardware. They have good example documentation for just such a configuration:
If your server already has those ports bound (specifically the DNS port 53) you are going to have to get creative; otherwise it’ll work well!
If not a cheapo pi 3 works, just so long as it is always on.
PoopMonster@lemmy.world 4 weeks ago
If your using docker and the ports are bound you can just use the network mode host so the container gets it’s own ip. It’s how I have adguard running on my unraid server
normalexit@lemmy.world 4 weeks ago
Thanks, that’s a good tip!
starkzarn@infosec.pub 3 weeks ago
That’s not how that works.
network_mode: host
shares the network namespace with the container host, so it doesn’t do any NAT, it only exists on the host’s IP. It would be akin to running a natively installed app, rather than in a container.macvlan
networking is what gives a container its own IP on the logical network, without the layer of NAT that the defaultbridge
mode networking that docker typically does.PoopMonster@lemmy.world 3 weeks ago
Thanks for the clarification I had mixed up the details and went to check my containers. You sir are correct. I added some documentation to my post regarding macvlan network creation.