SSH Tunnel via native Windows bash: Address already in use

In case anyone else finds this, there is a work around... you just need to reformat the tunnel with a specific bind address like this:

ssh -L 127.0.0.1:8022:173.22.0.1:22 [email protected]

From reading through the bug listing linked in the other answer, it looks like the issue is in the IPv6 subsystem, so I'm guessing this works by forcing IPv4.

Either way it works for me, using a fully updated Win 10 version 1607 install as of Jan 20, 2017.

It's a known bug and it's tracked here https://github.com/Microsoft/BashOnWindows/issues/739

As an alternative you can try using something like http://sshwindows.sourceforge.net/