The other day, I was using ssh as a SOCK5 proxy. To recap, I needed to access a resource that was only available from a remote Linux PC (i.e. my machine → remote Linux PC → network resource). One of the network resources was an embedded device with an SSH server. Hopping to the remote Linux PC over SSH was fine, but once there, I would then need to connect to my embedded device by calling SSH again (i.e. my machine → remote Linux PC (hop 1) → embedded device (hop2)). Fortunately, this step is, in fact, unnecessary and the process can be simplified.
I recently needed to access a resource that was only available from a remote Linux PC (i.e. my machine → remote Linux PC → network resource). The problem? There’s no GUI, no X Server I only have SSH access. The solution? One option is to set up a local port forward (ssh -L local_socket:host:host_socket), but this is limited to only a single end point and won’t work if the remote network resource redirects traffic to another port. This would work if we are, for example, talking to a web server over HTTP (port 80), but we would need to create a separate rule for HTTPS (port 443) and any other port required (e.g. for web sockets).