0

When running through WireGuard VPN tunnel from outside the network, I can access machines inside directly via IP. For example, hitting IP of PiHole box in a browser returns the PiHole UI. I can also access the internet fine.

When issuing a ping command to that same IP address through WireGuard results in a “no route to host” error. Same applies to pinging the router’s IP. When inside network on WiFi, running ping gets a response for both.

Ultimately trying to troubleshoot why mDNS packets aren’t making it to and from the device on VPN. There’s a mDNS reflector on the router, specifically enabled for WireGuard interface, so should be making it across the tunnel. The ping and mDNS issues could be related.

Where should I be looking to troubleshoot?

Overflowed
  • 1
  • *Where should I be looking to troubleshoot?* - your wireguard configuration – Jaromanda X Aug 12 '23 at 03:05
  • 1
    The ping could be blocked by a firewall: if the same IP destination works with TCP (HTTPS...) and not ICMP, This can't be a routing problem, or you didn't provide everything (like iptables/nftables port redirection etc.). – A.B Aug 12 '23 at 07:04

1 Answers1

1

Wireguard connections do not support multicast by default (you may be able to force it on after the link is created), so even with a mDNS reflector it's not going to see the mDNS requests over the tunnel.

hardillb
  • 1,552
  • 2
  • 12
  • 23