Difference between revisions of "WSL - Windows Subsystem for Linux"
(Created page with " Brug af systemd under WSL * https://github.com/shayne/wsl2-hacks") |
|||
| Line 3: | Line 3: | ||
Brug af systemd under WSL | Brug af systemd under WSL | ||
* https://github.com/shayne/wsl2-hacks | * https://github.com/shayne/wsl2-hacks | ||
| + | |||
| + | |||
| + | # 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 routing is done in iptables - 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 | ||
Revision as of 11:46, 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 routing is done in iptables - 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
