Understood, thanks.Just checked my configuration and all suffixes are set to 32, except for 0.0.0.0 (my bad). The suffix on 0.0.0.0 should be 0.
The suffix is just another way of expressing the subnet mask. 32 limits the number of IP addresses to 1.
Including 0.0.0.0/0 in the list of AllowedIPs for the client should get you access to the outside world (i.e., the internet). I have a near identical configuration (pi-hole, unbound, wireguard), and it works for me. The only difference is that I'm using Addresses in the range 10.0.0.X instead of 10.14.188.X, but that shouldn't make a difference.
See the problem is it did work just fine for weeks and then at some point it just stopped. I only know that during pivpn Wireguard install I did choose to enable unattended upgrades and that must have become the issue. I just have no clue which package caused the failure, why and how to determine it. And since Pi is physically in a remote location - having a clean OS install is not an option
Statistics: Posted by in_sympathy — Sat Jan 31, 2026 2:16 am