Difference between revisions of "WSL - Windows Subsystem for Linux"
| Line 13: | Line 13: | ||
you can eg install squid http proxy inside WSL and configure your browser to use localhost:3128 for proxy, and thereby force your req to go into wsl and from there be able to utilize the sshuttle tunnel | you can eg install squid http proxy inside WSL and configure your browser to use localhost:3128 for proxy, and thereby force your req to go into wsl and from there be able to utilize the sshuttle tunnel | ||
| + | |||
| + | if you combine this with a local https://en.wikipedia.org/wiki/Proxy_auto-config file and use file:///c:/path-to-your-pac in your browser you can specify which hosts to route to squid | ||
Revision as of 17:26, 19 September 2021
Brug af systemd under WSL
network
you can have services listen on *:<port> inside WSL and access the services from windows
sshuttle works under WSL (rembember that sshuttle only handles TCP - so forget UDP+ICMP !) but the traffic redirection is done in iptables within wsl - so windows applications can't use it
BUT
you can eg install squid http proxy inside WSL and configure your browser to use localhost:3128 for proxy, and thereby force your req to go into wsl and from there be able to utilize the sshuttle tunnel
if you combine this with a local https://en.wikipedia.org/wiki/Proxy_auto-config file and use file:///c:/path-to-your-pac in your browser you can specify which hosts to route to squid
