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

SSH Tunnels? #12

Closed
martinklepsch opened this issue May 8, 2014 · 4 comments
Closed

SSH Tunnels? #12

martinklepsch opened this issue May 8, 2014 · 4 comments

Comments

@martinklepsch
Copy link

Just thinking that tunneling ports might be useful:

overcast tunnel 7733:instance.01:4567

to allow users to access port 4567 on the remote machine as if it is port 7733 on their machine.

What do you think?

@andrewchilds
Copy link
Owner

Yeah, that could be nice to have. The signature could be more consistent with other commands though - look alright to you?

# Signature
overcast tunnel [instance] [local-port:remote-port...]

# Example
overcast tunnel instance.01 7733:4567 12345:67890

@martinklepsch
Copy link
Author

There is a difference between:

-L 4242:127.0.0.1:42042

and

-L 4242:actualhostname:42042 -N

I wonder how that could be handled? Maybe it's fine to assume that the localhost version is wanted?
(other than that I like the signature you suggested)

@andrewchilds
Copy link
Owner

Ah, right. We could allow for that like so:

overcast tunnel instance.01 7733:4567 12345:otherhost:67890

So if otherhost is missing, we could (safely) assume 127.0.0.1. Sound good?

@martinklepsch
Copy link
Author

Sounds solid!

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