You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I was wondering if you have considered adding a reverse tunnel option?
I have remote systems behind NAT and it would be useful for them to create a tunnel to a central system that can then connect back over the tunnel (to SSH usually).
I'm having a look at the code to do it myself but I'm a Rust newb so it's hard going :)
The text was updated successfully, but these errors were encountered:
It is not on my personal roadmap for now. I am trying to keep the shuttle binary dedicated to providing a OOBE proxy service without much complexity and versatility.
I was considering to add a new pair of server/client binaries for simplistic port forwarding. But I am currently busy on implementing other features such as multiplexing and up-to-date TLS fingerprints. We can also have an additional option for reverse tunneling on that binaries in the future, while I hope to push the encapsulated inner tunnel protocol to existing projects like rathole (or maintain a minimum fork if anyone is interesting) when the protocol implementation becomes mature enough someday.
Hi,
I was wondering if you have considered adding a reverse tunnel option?
I have remote systems behind NAT and it would be useful for them to create a tunnel to a central system that can then connect back over the tunnel (to SSH usually).
I'm having a look at the code to do it myself but I'm a Rust newb so it's hard going :)
The text was updated successfully, but these errors were encountered: