Tailscale has an technical article on this if you are starting from scratch.
If you can’t install tailscale on the pi-hole directly, you can also use a subnet router and a /32 with just that address to expose it to tailscale.
Came here to say this. Now I just need to upvote.
“It incurs additional battery usage.“
Does it? I always use a vpn on my phone and laptop and it’s not even measurable. Sure there’s gonna be more CPU usage, but with hardware acceleration and whatnot it’s almost nothing.
This is anecdotal experience, but last time I left Wireguard on for an entire day and it accounted for 5% of battery usage that day.
Fair enough, this is 10 days of usage for me always being on.
Mine is so low it says “no usage”.
I use Home Assistant DuckDNS and Nginx addons. DuckDNS handles the dynamic DNS updating when my ISP inevitably changes my IP address. Let’s Encrypt for certificates. Nginx for proxying to IPs on my network
If pi-hole blocks all ads how does the web look? Do pages have a lot of blank areas on them or what?
Yes and no. You just have to see its beauty to get it. I also have been using it for a long ass time, almost a decade, so I could not even tell even tell you what sites look like with ads.
I haven’t set up this yet, but I use AdGuard on my phone and yes, it does leave blank space. Sometimes I don’t realized there was more text to read because it’s empty.
It’s not about the adblocker though. It’s on the quality of the developer. A good developer tells the browser to leave space for ads before it loads them. It makes the page load faster and also prevents the page jumping around as each item loads.
Ironically, a bad developer that doesn’t do that, probably has better website layouts for people who use adblockers. 🙃
LOL yeah I actually understand that last part LOL (former web dev, retired). Sites jinking around while the ads load and I’ve already started reading the content are super annoying.
Don’t you love scrolling right when the page loads and you click an ad instead?
It’s a feature, not a bug! Haha!
One thing I really do hate is a download page with a giant green DOWNLOAD button that’s just an ad link, and the thing I went there to download is a tiny text link.
A big problem for me is, that Android is not allowing custom DoT servers. Even though the system supports DoH and is even using it for their built in resolver (Google/cloud flare) Networks that only whitelist TCP 433 (some guest wifis) will fail to use DoT.
I believe you swapped DoT (TLS, port 853) and DoH (HTTPS) in your message. I have yet to be in a network that restricts port 853, but if I could I would rather use DoH on Android.
For me its been wireguard with split tunnel but that had a glaring issue with my home IP change (running 2 Pi-hole+unbound instances on separate network segments and hardware). Some time ago I switched to tailscale and added a Pi-hole on a VPS. Closed system, nothing exposed to the wide internet, works 99.99…% of the time, whole family protected against low hanging fruit attacks and adds.
Use ddns on your router with a domain so you can then get something like wireguard.example.com and then use that as the endpoint in your wireguard.
Set the wireguard DNS as your pihole.
To make life easier set your home network IP space to something that another WiFi would never use, ie 192.168.46.xx
That way it will never conflict if you are on a public WiFi and you can access anything on your home lab when you need.
I’ve been using this setup for years on laptop, phone etc
I do exactly this as well. Works great! Dynamic DNS is kind of a hilarious hack.
Quick question: since I use wireguard, do I need to use DNS-over-HTTPS for security? My assumption is that my entire session is already encrypted with my wireguard keys, so it doesn’t matter. But I figured I should double check.
Depends, do you have pihole/unbound setup to only recursively resolve? Or do you forward requests to an upstream (either as a fallback or just as a primary). If that’s the case, and depending on your threat model, you’ll want to set up DoH or DoT as your DNS requests will be forwarded in plaintext
You do not need anything else. DNS requests are all sent over Wireguard with encryption
Excellent to have confirmation, thanks. What about the VPN connection handshake? I always assumed it was OK over non-SSL, because the exchange should use signed keys. But that is quite an assumption on my part.
Wireguard uses public and private keys which are designed from the ground up to be used over plain text to establish the handshake so it isn’t an issue. Same idea with ssh keys and ssl keys
Thanks. Wild that folks build SSH and HTTP around the same time without realising that HTTP could benefit from some of that same tech!
I have ddns on Cloudflare. It works great, until your home IP changes. After that wireguard will happily hammer the old IP, till something breaks the tunnel and it reestablishes it to the new IP. Working as intended. My workaround was forcing the IP change over night while everyone was home.
Tailscale sorts all the issues I had.
Whats the issue with the Home IP changing? - Have you setup a DynDns hostname?
It may since have been fixed, but the Android client didn’t handle IP changes well in my experience. From my understanding, it only checks DNS when it initially connects, and so if the public IP changes the connection just stops working. This might be fine if the public ip changes infrequently or if you frequently connect and disconnect rather than leave the client always on, but not so much otherwise.
Tailscale (and headscale) handles this gracefully, and you also get the nice NAT traversal features so no need to worry about CGNATs which are becoming more common.
that’s how it works on desktop too regarding DNS, but when it receives a response from a new IP, it should send future traffic there as I know
From my understanding, it only checks DNS when it initially connects, and so if the public IP changes the connection just stops working.
This is pretty standard TCP network behavior for long duration connections. The client queries dns for the IP address, opens a socket, and leaves it open as long as needed.
One thing that would help here is some kind of keepalive feature, like a client to server TCP connect or SYN, or better yet a higher level protocol signal. Check your client to see if there is some tunable keepalive. It may be set so something long like 1h.
Wireguard uses UDP, by the way.
Wireguard does have a KeepAlive option, but I found it didn’t seem to help in practice.
Could be bugs with the client, which is pretty barebones.
