[SOLVED] WireGuard: After adding a second peer, the first can't connect anymore

[Brink7564]

So I just tested this again and it seems like there might be a bug, else I don't understand this behaviour.

I created a WireGuard instance as per the road warrior documentation to connect my phone to my network, and it worked like a charm. I could reach both the Internet and my local network perfectly fine. I then proceeded to add a peer for my laptop, which also worked like a charm.

However, when I now try to connect with my phone, the handshake succeeds, but I can't connect anywhere anymore. Trying to access anything in my local network or the Internet results in timeouts. I checked the WireGuard logs and the firewall live view, but they don't show any obvious hints.

I already went through this a second time because I thought it may be my configuration or I missed something the first time around, but that does not seem to be the case as the exact same thing happened again. What surprises me is that it was working in the first place, so it shouldn't be a connection issue. And the handshake succeeds too, so it seems the connection gets established.

What might be the reason for this? And more importantly, a solution?

[mimugmail]

Sound like you mixed the masks with /24 and /32, may read the docs again

[Brink7564]

Sound like you mixed the masks with /24 and /32, may read the docs again

You're right, thank you! I had put 0.0.0.0/0 in the Allowed IP's field thinking I want to allow all traffic through the VPN. But that setting is done on the client, not the server... Thanks again; made my day!