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

socks5 support #14

Open
mudler opened this issue Mar 15, 2022 · 4 comments
Open

socks5 support #14

mudler opened this issue Mar 15, 2022 · 4 comments

Comments

@mudler
Copy link
Owner

mudler commented Mar 15, 2022

No description provided.

@matti
Copy link

matti commented Oct 9, 2022

@mudler can you add a bit description here? Might give this a shot

@mudler
Copy link
Owner Author

mudler commented Oct 10, 2022

Hi @matti ! thanks for showing interest in this.

The idea I had behind this feature is to provide a socket server from one side, and a "proxy" on the other side, similarly to https://github.com/mudler/edgevpn/blob/master/pkg/services/egress.go.

Egress works that a node starts a HTTP proxy server and connections to the proxy are sent to another node which is advertised as egress (this needs to be explicitly enabled from the CLI). The egress accepts connections and will proxy through them - the same thing could have be done with socks5, and hence this card!

I hope it was clear enough and spiked your interest :)

@matti
Copy link

matti commented Oct 10, 2022

What's the benefit of using socks5 instead of http proxy? lower overhead?

@mudler
Copy link
Owner Author

mudler commented Oct 27, 2022

not really, just providing legacy support and isolation with old protocols. In this way we could be on pair with tor and provide the same abstraction layer

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

No branches or pull requests

2 participants