Alles anzeigenThank you for all your suggestions.
So, I copied again the peer files from the server and reloaded it: same behaviour, unfortunately:
1 - with Alowed IPs 192.168.1.0/24, I can see my server at 192.168.1.96... but no access to the internet.
2 - I modified directly the connection on the app (thanks for the tip!) to 0.0.0.0/0: now I can access everything, but whatismyip points to the external IP from home... I assume in this case, all my traffic is going through home. Not optimal, right?
3 - I tried a cowboy thing: put allowed Ip to 10.13.13.0/24. Then I have an external IP on my phone, but I could not access my server on it's local IP...
I got exactly the same issue (even though my Wireguard installation is on a RasPi via PiVPN script). Was searching for a solution and saw this post. Even though this was considered solved, I'd add some information:
1. A workaround: add a Public DNS Server (eg. 8.8.8.8) to the "DNS=xxxx" under [Interface] section of the client config.
[Interface]
...
DNS=1st-one-is-your-WG-Server-IP, 8.8.8.82. Have only been using OpenVPN on Asuwrt Merlin. They has an option to route "LAN only" traffic through the tunnel. So when I got this issue with Wireguard, I thought Wireguard behaviour was different. But reading chente answer, it turned out WG behaviour was the same, except that it was actually different on my setup (and luisfmrosa setup). Well, I'll continue to search and find the actual reason/solution.