[GH-ISSUE #70] LAN access / split tunneling for local networks in AmneziaWG Windows client #45

New issue

Open

opened 2026-10-13 21:11:17 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-13 21:11:17 +00:00

Owner

Originally created by @wisecompile on GitHub (Sep 8, 2025).
Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-windows-client/issues/70

When using the AmneziaVPN Windows client with AmneziaWG (WireGuard), all traffic including LAN (192.168.x.x) is routed into the VPN tunnel.

This makes it impossible to access local devices (e.g. Windows file sharing / Samba to a TV) while the VPN is active.

I see that split tunneling exists for websites and applications, but there is no option to exclude LAN IP ranges or bypass local networks.

Is LAN bypass currently supported in the Windows client?
If not, is it planned to be implemented in future releases?

This feature would be very useful, as many VPN clients allow LAN traffic outside of the tunnel by default.

Originally created by @wisecompile on GitHub (Sep 8, 2025). Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-windows-client/issues/70 When using the AmneziaVPN Windows client with AmneziaWG (WireGuard), all traffic including LAN (192.168.x.x) is routed into the VPN tunnel. This makes it impossible to access local devices (e.g. Windows file sharing / Samba to a TV) while the VPN is active. I see that split tunneling exists for websites and applications, but there is no option to exclude LAN IP ranges or bypass local networks. - Is LAN bypass currently supported in the Windows client? - If not, is it planned to be implemented in future releases? This feature would be very useful, as many VPN clients allow LAN traffic outside of the tunnel by default.

bsakaguchi commented

2026-10-13 21:11:17 +00:00

Author

Owner

@SoVoKaN commented on GitHub (Sep 26, 2025):

As far as I know, the AWG client may not support split tunneling. By using the command
route -p add 192.168.0.0 mask 255.255.0.0 192.168.0.1 metric 25
you configure Windows to route all traffic to the 192.168.x.x subnet through the local gateway 192.168.0.1, bypassing the VPN.

@SoVoKaN commented on GitHub (Sep 26, 2025): As far as I know, the AWG client may not support split tunneling. By using the command `route -p add 192.168.0.0 mask 255.255.0.0 192.168.0.1 metric 25` you configure Windows to route all traffic to the 192.168.x.x subnet through the local gateway 192.168.0.1, bypassing the VPN.

bsakaguchi commented

2026-10-13 21:11:18 +00:00

Author

Owner

@unwnstr commented on GitHub (Oct 6, 2025):

You can exclude desired networks from AllowedIPs in config. Use this calc for example link

Btw this version still lacks simultaneous activation of several tunnels with not overlapping allowedips.

@unwnstr commented on GitHub (Oct 6, 2025): You can exclude desired networks from AllowedIPs in config. Use this calc for example [link](https://www.procustodibus.com/blog/2021/03/wireguard-allowedips-calculator/) Btw this version still lacks simultaneous activation of several tunnels with not overlapping allowedips.

bsakaguchi referenced this issue

2026-10-13 21:11:53 +00:00

[PR #45] [MERGED] Fix bat bug #101