Oh yes, I need to update.@Feek did you try to dig out any possible domain names to whitelist for wifi calling to explicitly allow or just disabled the list that you found causing it?
That sounds like an iPhone setting. Does this still happen when not connected to the WiFi?For example, her mail app was showing the warning about network privacy settings blocking content and this is because the mask.icloud.com and mask-h2.icloud.com domains were being blocked, even though no block lists are attached to the “No block” group. Am I missing a setting somewhere?
So Pihole has had an update, but also i have noticed the Hagezi github addresses have stopped working for the moment, the alternative links do work
Reddit - The heart of the internet
www.reddit.com
Also for me, after updating pihole, i needed to rename the FTL database in order for pihole to start working again and the web interface to be accessible
sudo service pihole-FTL stop
sudo mv /etc/pihole/pihole-FTL.db /etc/pihole/pihole-FTL-old.db
sudo service pihole-FTL start


There's a method described earlier in this thread, it's how I've got mine set up for that.Have they added DoH/DoT capability yet like most of the other providers ?
Have they added DoH/DoT capability yet like most of the other providers ?
I was leaning towards an answer if pihole has added the Functionality yet or not, there seems to be a lot of hack jobs to get DoH to work. I tried the one above for a giggle which works by just pasting the compose example into portainer. I think you used the old trusty way here>> https://pimylifeup.com/rapberry-pi-dns-over-https/comment-page-1/There's a method described earlier in this thread, it's how I've got mine set up for that.
Sounds about right.Looking for some help please? Just setup up Pi Hole it seems to be working or doing something but i'm confused on the DHCP bit?
I have a VM 5X modem/router thing and have disabled DHCP. I have enabled a static IP address on the Pi and on the router, I think (it seems to be working anyway). I have turned on DHCP server on the Pi Hole settings and set the Gateway address to the address I use to log into my router but am confused with the RANGE of addresses hand out part? I have set this to 192.168.0.10 to 192.168.0.254 but literally have no idea? Then because I can't setup up DNS on my router I have changed the DNS settings on my PC and other things to the IP of the Pi Hole server? Thanks.
VoIP (specifically SIP for signalling and RTP for media) highly relies on a solid firewall setup and NAT traversal. UPnP takes care of this on most occasions, but the NAT translations can sometimes stop updating and a reboot is usually the only way to clear it. Double check that SIP ALG is disabled on your router as the endpoint is always much better at rewriting SIP headers than the firewall ever is.Oh yes, I need to update.
I had a situation a couple of days later when I had an incoming call, which I answered but couldn't hear anything, it was from the local surgery so I called them back and they said I'd not answered. I went straight onto my Piholes and dropped them both down to just the minimal list but at the same time, I remembered that a few years ago, I had a situation with my work desk phone, which is an IP phone. When anyone called me, I couldn't hear them and all my outgoing calls failed.
The fix for that was to reboot my Draytek 2865.
So I rebooted my Draytek 2865 and WiFi calling has worked perfectly since. I've left my Piholes with just the minimal Hagezei list enabled and nothing else and that's been perfectly adequate, I've not noticed any ads getting through which were previously blocked.
It was probably my router, perhaps a little confused by something.

Yup, none of the ALG stuff is enabled.Double check that SIP ALG is disabled on your router as the endpoint is always much better at rewriting SIP headers than the firewall ever is.
	Nothing wrong with a regular reboot to keep things fresh. If it's something that occurs infrequently and a reboot always fixes it, a regular reboot schedule sounds like a good workaround. Getting Draytek to patch the firmware may be a harder task!That's all really interesting, thanks. It does make me wonder if it's adding a scheduled monthly reboot to the Draytek.
Yup, none of the ALG stuff is enabled.
![]()
Sounds about right.
I'd cut your DHCP range down a bit, usually I go from .51 to .199 to give yourself some static room before and after the DHCP clients.
If it's working though....you're done.