Skip to content
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

Open
1 of 2 tasks
davidmnoriega opened this issue Jan 6, 2025 · 2 comments
Open
1 of 2 tasks

sshuttle does not work #12439

davidmnoriega opened this issue Jan 6, 2025 · 2 comments
Labels

Comments

@davidmnoriega
Copy link

davidmnoriega commented Jan 6, 2025

Windows Version

Microsoft Windows [Version 10.0.22621.4602]

WSL Version

2.4.8.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Ubuntu 22.04

Other Software

GlobalProtect VPN
sshuttle 1.1.2 with iptables-legacy

wslconfig

[wsl2]
memory=20G
processors=6
swap=4G
networkingMode=mirrored
autoProxy=true

[experimental]
sparseVhd=true

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

Copy link

github-actions bot commented Jan 6, 2025

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

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
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please 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:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@davidmnoriega
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants