"non-`--setup`" mode in Windows
ge9 opened this issue · comments
Currently, Windows version implicitly uses --setup because creating a tun device itself requires admin privilege.
However, I think it will be useful if we can use this tun device only for specific routes (like 10.0.0.0/24).
FYI, just disabling --setup in Windows configuration didn't work for me (it still sets the default route).
I don’t know the necessity of doing this. Moreover, according to my memory, if the routing table is not set, tun2proxy will not work. I’m not sure if my memory is accurate.
I tried changing the source code not to use tproxy_setup function in your "tproxy-config" crate (https://github.com/tun2proxy/tproxy-config/blob/master/src/windows.rs), but it still creates the device with the default route with metric 6. That seems weird but maybe wintun's behavior.
As a workaround, I use netsh and route commands to modify route settings manually.
I thini it's useful that I can use remote network such as 10.0.0.0/24 from the local computer, without affecting other unrelated internet traffic.
Thank you.