-
Notifications
You must be signed in to change notification settings - Fork 841
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sshuttle does not work #12439
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done. If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here Once completed please upload the output files to this Github issue. Click here for more info on logging View similar issuesPlease view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it! Closed similar issues:
|
I had to modify the network collection script as the logs were larger than 2GB, but I've opted to email the details instead of attaching here. |
Windows Version
Microsoft Windows [Version 10.0.22621.4602]
WSL Version
2.4.8.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.167.4-1
Distro Version
Ubuntu 22.04
Other Software
GlobalProtect VPN
sshuttle 1.1.2 with iptables-legacy
wslconfig
Repro Steps
Running latest release 2.3.26.0, or pre-release 2.4.8.0
Connect to vpn
Start sshuttle
ssh to server
Expected Behavior
Expect to ssh to server
Actual Behavior
ssh timeouts
I can see the packet counter increments in iptables
Downgrading wsl to 2.2.4 and sshuttle works again
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: