Like the other commenter said, that is correct. For SSH, I set up a VM as my SSH bastion or jump host. I connect to that, and the SSH from that to any other machine on the network.
Comment on Port forward to different IP based on destination address in opnsense
doctorzeromd@lemmy.world 5 months agoI have a reverse proxy, but that won’t do ALL traffic, right? Just http or https?
thejevans@lemmy.ml 5 months ago
lemmyvore@feddit.nl 5 months ago
If you control the software stack at both ends you may want to consider Chisel which is a HTTP tunnel for TCP and UDP.
The connections would go SSH client > Chisel client > HTTP reverse proxy > Chisel server > SSH server. The Chisel parts speak HTTP to each other so that part can be routed by domain.
Chisel can also do its own encryption so you can use HTTP and avoid the HTTPS-specific issues about extracting the domain name from the HTTPS connection.
ad_on_is@programming.dev 5 months ago
you only have one IP. As you rightfully said, reverse proxy does only http(s), port 80/443. this works because of the nature how http requests work. They carry the hostname as part of the protocol (request headers). SSH is a whole other story, since the client does not send the hostname as part of the protocol, only the IP and the port.
What you can do is forward different ports to different machines… 2021 -> server1, 2022 -> server2, etc.
bjoern_tantau@swg-empire.de 5 months ago
For SSH the ’ProxyJump’ directive is awesome. Have one server reachable from outside and then use it to jump to all the others.