View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008159||Kali Linux||[All Projects] Kali Package Bug||public||2023-01-24 22:28||2023-01-26 20:06|
|Target Version||Fixed in Version|
|Summary||0008159: WSL kex and SSH errors|
|Description||Kali running in WSL failing to run kali in windows mode. ESM and SL will open.|
Linking other issue https://bugs.kali.org/view.php?id=7586
as it seems very simular
creating new issue because I have the same error but also issues with running ssh.
SSH will not start for IPv4 was running systemd at one point and got the error report that ssh failed to bind to port 22 on 0.0.0.0 because the address was already in use.
|Steps To Reproduce||kex --win|
sudo service ssh start
Okay, confession time.
I resolved half my problem.
In order to access my kali image via SSH from other devices in my house I needed a way to get to the SSH server through my windows host machine. I accomplished this with a powershell script that I had gotten off the internet.
The script runs netsh portproxy commands that forward ports like 22 from the outside into the kali vm.
I set this script to run at startup and didn't have any issues starting services on the kali machine.
I am not to sure but now if the port proxy is running for 22 the kali machine detects this as the port being used and fails to start up the service for the port.
run the script after the ssh service is running and it works just fine.
This still hasn't resolved the Kex issues so I am not sure if we should close this issue but seeing how the ssh problem was the only thing that made this issue unique from https://bugs.kali.org/view.php?id=7586 then I understand if the reasoning for resolving it.
NIC-BRIDGE.ps1 (1,255 bytes)