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

SOCKS only SSH connections #76

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

danfruehauf
Copy link
Owner

  • Allow SOCKS only connections (-D host:port, -D port)
  • Use dummy0 as interface
  • Fix bug in config validation, where only prefix of keys were
    compared

Fixes #41

 * Allow SOCKS only connections (-D host:port, -D port)
 * Use dummy0 as interface
 * Fix bug in config validation, where only prefix of keys were
   compared
@danfruehauf
Copy link
Owner Author

Still incomplete, need to add:

  • UI changes, to allow switching between SOCKS mode and full VPN mode
  • Export/Import support

Currently one can modify the current configuration file and add:

socks=yes
socks-bind-address=localhost:10000

Then run:

$ nm cli con reload

@danfruehauf
Copy link
Owner Author

@ockham FYI. It is still incomplete, but the basic functionality is there. It uses dummy0 as the device of choice to feed to NetworkManager - because we must.

@intika
Copy link
Contributor

intika commented Oct 25, 2018

@ockham FYI. It is still incomplete, but the basic functionality is there. It uses dummy0 as the device of choice to feed to NetworkManager - because we must.

if i did understand right does this mean that if the connection is lost network manager will not know about it ?

@danfruehauf
Copy link
Owner Author

if i did understand right does this mean that if the connection is lost network manager will not know about it ?

In what sense? NM has got nothing to do with it anyway, as it doesn't set any new interfaces or new routes. Are you talking about different events? Well, there will be an event emitted that the connection is up. I'm afraid I didn't understand your question entirely.

@intika
Copy link
Contributor

intika commented Oct 25, 2018

if i did understand right does this mean that if the connection is lost network manager will not know about it ?

In what sense? NM has got nothing to do with it anyway, as it doesn't set any new interfaces or new routes. Are you talking about different events? Well, there will be an event emitted that the connection is up. I'm afraid I didn't understand your question entirely.

Sorry i was not enough clear in my question... let say in the case where the ssh tunnel connection is lost/disconnected in that case does NM change its displayed info ?

@danfruehauf
Copy link
Owner Author

Sorry i was not enough clear in my question... let say in the case where the ssh tunnel connection is lost/disconnected in that case does NM change its displayed info ?

Definitely. It'll show the connection/tunnel as down.

@intika
Copy link
Contributor

intika commented Oct 25, 2018

Sorry i was not enough clear in my question... let say in the case where the ssh tunnel connection is lost/disconnected in that case does NM change its displayed info ?

Definitely. It'll show the connection/tunnel as down.

Thanks for the feedback :) ... i will test that once i manage to replace my current version ;)

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

Successfully merging this pull request may close these issues.

Support ssh -D (SOCKS proxy)
2 participants