Request: Non-VPN mode
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- networking
Research direction
The issue points to the README and the how-it-works documentation but names no source file or test. Start by tracing the client entry point and existing forwarding path, then determine how a client-only SOCKS4 mode would fit. Done means a documented standalone mode that provides the requested SOCKS4 server without requiring VPN-style operation.
Written by the indexing model from the issue text.
Description
Hi,
I readed the documentation multiple times. In special this part: https://sshuttle.readthedocs.io/en/stable/how-it-works.html
where it comments: "sshuttle assembles the TCP stream locally, multiplexes it statefully over an ssh session, and disassembles it back into packets at the other end. So it never ends up doing TCP-over-TCP. It’s just data-over-TCP, which is safe".
So, compared to a simple "ssh -D 1080" command the shuttle improves the performance using some techniques to multiplexing different flows and assign to it different queues.
However, in the README page this project comments:
"The remote network has no VPN, or only stupid/complex VPN protocols (IPsec, PPTP, etc). Or maybe you are the admin and you just got frustrated with the awful state of VPN tools."
And I'm one of these users that don't want to use VPNs to connect to some remote networks. I prefer to use simple port forwadings with tunnels.
However the performance of sshuttle is better than the simple "ssh -D 1080". So assuming this... Why not implement an standalone (aka non-VPN) mode? Please, note that this request is related only to the client part. The idea is to open a simple SOCKS4 server in the client machine.
Please consider this idea.
Regards.
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 795
- Avg merge
- 8h 49m
- Merged PRs (30d)
- 12
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sshuttle/sshuttle
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
All issues in sshuttle/sshuttle
Similar issues
-
link-check link-check:sphinx-theme
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
qgis/QGIS-Documentation#11275 ·
-
bug priority:normal ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
OpenHands/extensions#626 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
CSCfi/sd-search-api#39 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100