-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Jump Hosts #577
Comments
Having had time to think about some of my use cases for ProxyJump, I can indeed see why you created a separate feature request for this. For example, #266 is great because it allows me to SSH to an internal client via my proxy (tunnel) SSH server. However, what (I think) it doesn't let me do is forward ports from that internal SSH client, via the tunnel SSH server. From what I can gather, the Tunnel connection has a Port Forwarding field, but does this only allow me to forward ports from that tunnel SSH server only? What I would like to do is forward ports from different internal servers via my single proxy/tunnel SSH server. e.g. access an internal VNC server (on port 8123) from my laptop when away from home, via my tunnel/proxy server (locked down with public/private keys only). I imagine this working by adding "Port Forwarding" fields to the SSH tab connections, and then still using a Tunnel connection with * in Port Forwarding. Or perhaps I've misunderstood how the current implementation works and this is indeed something that can already be done? |
You could forward external hosts and ports reachable from your jump host : About the * wildcard for Dynamic Port Forwarding :
Does I have understand your use case? |
Ah yes I see now, I didn't realise it could be used that way! I've just tested and can confirm that it works as I was hoping! Thank you again Arnaud! 🎉 |
You're Welcome @jarrah31 Don't worry I'm also the same type of person 😉 |
Actually, what you wrote above would work really well as a working example within the Port Forwarding page because it explains the feature in a simple way and goes into more detail on how Dynamic Port Forwarding works. Perhaps one suggestion could be a couple of blogs linked from help pages that do in-depth working examples to explain to users how they can make the most out of your app. e.g. How-to do Remote Desktop (RDP) access to internal Windows Desktop PCs from outside your home (3389:192.168.0.10:3389 - using Microsoft RD Client on iPad - works great!) I know how time consuming these type of guides can be though, plus you'd have to keep maintaining them, and ensuring they offer correct advice, etc. Just a thought anyway, not necessarily these topics. :) |
Feature description
Ability to jump a SSH / SFTP connection without the need to create a Dynamic Port Forwarding tunnel.
The text was updated successfully, but these errors were encountered: