2016-01-20 10:55:10 +01:00
|
|
|
Microsoft Windows
|
|
|
|
|
=================
|
|
|
|
|
Currently there is no built in support for running sshuttle directly on
|
|
|
|
|
Microsoft Windows.
|
|
|
|
|
|
|
|
|
|
What we can really do is to create a Linux VM with Vagrant (or simply
|
|
|
|
|
Virtualbox if you like). In the Vagrant settings, remember to turn on bridged
|
|
|
|
|
NIC. Then, run sshuttle inside the VM like below::
|
|
|
|
|
|
|
|
|
|
sshuttle -l 0.0.0.0 -x 10.0.0.0/8 -x 192.168.0.0/16 0/0
|
|
|
|
|
|
2016-01-20 11:01:13 +01:00
|
|
|
10.0.0.0/8 excludes NAT traffic of Vagrant and 192.168.0.0/16 excludes
|
|
|
|
|
traffic to local area network (assuming that we're using 192.168.0.0 subnet).
|
2016-01-20 10:55:10 +01:00
|
|
|
|
|
|
|
|
Assuming the VM has the IP 192.168.1.200 obtained on the bridge NIC (we can
|
2016-01-20 11:01:13 +01:00
|
|
|
configure that in Vagrant), we can then ask Windows to route all its traffic
|
2016-01-20 10:55:10 +01:00
|
|
|
via the VM by running the following in cmd.exe with admin right::
|
|
|
|
|
|
2021-09-22 14:13:22 +02:00
|
|
|
route add 0.0.0.0 mask 0.0.0.0 192.168.1.200
|
