vithusel
commented
3 months ago Having checked this myself I can confirm that is the case and is the correct procedure.
Allow 0.0.0.0/0 is a blanket cover for all ip's.
There should be a function to dynamically disable VPN for local network (likely via a tick box)
If you disregard this template, your issue may risk being overlooked and closed. Kindly invest some time in furnishing as much information as possible. This enables us to promptly diagnose your issue without necessitating multiple follow-up inquiries. Your cooperation is greatly appreciated.
If any of the following questions are irrelevant, indicate them as "Not Applicable."
Describe the issue I chose to use this app instead of official because by default it wouldn't route local network traffic to vpn, but after upgrading from 0.x version to 1.0.6 i noticed that now all traffic goes through vpn, is that expected behavior? I can exclude local addresses but it was convenient not to have to when managing 50+ PCs
To Reproduce
Expected behavior Local adress ranges (192.168.0.0/16, 172.16.0.0/12, 10.0.0.0/8) don't get routed through vpn connection by default
Tested on official WireGuard client Are you experiencing the same issue using the official Windows WireGuard client? Yes
Tested on different VPN servers Only have one to test
Screenshots and GIF's Not Applicable
Tunnel Config Not sure if required Allow 0.0.0.0/0 but app would not force local connections through vpn anyway on 0.x versions
Logs Can't provide at the moment
Starting WireSock directly Can't provide at the moment, mostly just asking anyway