I’m experiencing this same issue.
As soon as I enable my Wireguard Client in my GL-B1300 to connect to my Wireguard server (in EC2), I’m able to ping the Wireguard interface IP on the EC2 server, but I’m no longer able to access the external public IP on that same EC2 server.
Steps to reproduce:
- confirm able to ping external IP of EC2 server.
- setup wireguard client on GL-B1300, and on EC2 server.
- confirm able to ping internal wireguard (wg0) interface IPs over the wireguard tunnel (from either end).
- devices in the LAN of the GL-B1300 are unable to ping the external IP of the server anymore. (get no route to host errors)
it’s worth noting that the GL-B1300 diagnostics (or via SSH → bash shell on the GL-B1300) IS able to still ping the external IP of the EC2 server regardless of if the wireguard tunnel is connected or not.
this breaks my access to all the other (email, https) hosting I’ve got on that same EC2 server.
has anyone gotten any of the suggested fixes working?
Wrong iptables for wg, accessing servers IP appears to be a duplicate of this same issue.