WSL - Windows Subsystem for Linux
Contents
kernel
remember to check the release notes occasionally https://docs.microsoft.com/en-us/windows/wsl/kernel-release-notes
systemd
Brug af systemd under WSL
OR
iptables
wsl2 kernel will have iptables support - but not nftables so eg debian needs to be configure to use the iptables-legacy variant https://wiki.debian.org/nftables
this will affect both sshuttle and podman/docker
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
docker
Docker.io upstream package works - but you need to get iptables and systemd in order
Docker desktop integrates with WSL(2) but the native docker package will not work within wsl2
Docker Desktop has recently changed license - so it might be time to look into podman instead ?
