Can't connect to local devices on Windows 10

[TarekSalama]

I have noticed that I can't connect to local devices if I am using Wireguard with Algo on Windows 10 and I try to connect to my router/phone for example (192.168.1.x).

Is this a limitation with Algo or the Wireguard client itself on Windows 10? How can I get around this? It's worth noting that it works fine on macOS

[TC1977]

That's because macOS doesn't send LAN traffic through the VPN, by default.

[TarekSalama]

By default? So how do I change that?

[TC1977]

Well, one way to do it would be to modify the WIreGuard client config on your Windows machine to exclude local IPs. I'm using this from the WireGuard mailing list archives.

As of today (version 0.0.38), the way to do that would be to open up the WireGuard client, click on your connection in the left windowpane, and then click "edit" in the lower right hand corner of the right windowpane. Then in the AllowedIPs field in the [Peer] section, put in the following:

0.0.0.0/5,8.0.0.0/7,11.0.0.0/8,12.0.0.0/6,16.0.0.0/4,32.0.0.0/3,64.0.0.0/2,128.0.0.0/3,160.0.0.0/5,168.0.0.0/6,172.0.0.0/12,172.32.0.0/11,172.64.0.0/10,172.128.0.0/9,173.0.0.0/8,174.0.0.0/7,176.0.0.0/4,192.0.0.0/9,192.128.0.0/11,192.160.0.0/13,192.169.0.0/16,192.170.0.0/15,192.172.0.0/14,192.176.0.0/12,192.192.0.0/10,193.0.0.0/8,194.0.0.0/7,196.0.0.0/6,200.0.0.0/5,208.0.0.0/4

This should tunnel only traffic that's bound for non-local IP addresses.

You may also have to uncheck the "block untunneled traffic (kill-switch)" box at the bottom of the edit screen. Not sure though.

Let us know how that works out.

[Zeushn]

I have the same problem, this solution works only if I removed the 0.0.0.0/0, ::/0 entry in the allowed IPs but kills the outbound connection, any ideas? I know for connection between clients connected in the same VPN server the BetweenClients_DROP option in the config.cfg works but haven't try if it works in the local LAN.