Please follow the below template, it will help us to help you!
Expected Behaviour:
DHCP packets should be sent to a client on the local network upon request. Clients should also be able to access the admin console via http:// or ssh using port 22
RaspberryPi 3B
Raspbian 11
FirewallD service running (setup based on pre-requisites instructions from pihole website)
Actual Behaviour:
Unable to resolve DNS on the client-side when manually setting an IP address for the client or receive a DHCP packet for newly connected clients requesting an IP address. Clients are also unable to access the admin portal - I've had to hook up a monitor and keyboard to view details of whats going on on the piHole system. I'm also not able to access the Pi via SSH from the local network.
I did a lot of digging - found this command: pihole-FTL dhcp-discover
I get this error: "Could not sendto() in send_dhcp_discover(): Network is unreachable"
I continue to see the following DNSMASQ errors: "failed to send packet: Destination address required"
Your debug log suggests your Pi-hole is operational.
Your warning messages suggest that Pi-hole is trying to send a DHCP packet to an IP address that either does not exist anymore (e.g. device went offline since requesting DHCP), is not accessible (incorrect routing configuration, router device isolation, etc.) or is blocked by some routing equipment's firewall (e.g. physical or VLAN switch/router/AP).
Your debug log suggests you are co-hosting Wireguard on the same machine as Pi-hole.
Is your observation somehow related to clients connecting both directly and through a Wireguard tunnel, perhaps a site-to-site-VPN?
The ssh process is an OS-level process. Given that you can't access the Pi via ssh, this indicates an OS level problem that would be resolved at the OS level.
Clients don't access the admin portal via port 22 - port 80 is the port that leads to the http page.