Difference between revisions of "WSL - Windows Subsystem for Linux"

From HoerupWiki
Jump to: navigation, search
Line 11: Line 11:
 
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
 
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
 
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
 
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

Revision as of 10:48, 26 August 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