Edit or create new remmina server connection
schema
~/.ssh/rdp-tunnel.sh ACTION TUNNELNAME LOCAL_PORT:REMOTE_SERVER:REMOTE_PORT TUNNEL_PROXY
name | description |
---|---|
ACTION | start|stop |
TUNNELNAME | "string identify socket" slugify to create socket file into ~/.ssh/sockets/string-identify-socket.control |
LOCAL_PORT | the door that will be exposed locally if we use the same port for two connections it will crash |
REMOTE_SERVER | the ip of the server that you would access if you had it on the proxy server that will be used |
REMOTE_PORT | the service port that runs on the server |
TUNNEL_PROXY | the connection you are going to use as a proxy, it needs to be in your ~/.ssh/config preferably using the access keys |
I use the combination (% g-% p) of the remmina group name and connection name to be my TUNNELNAME (this needs to be unique, it will see the socket name)
pre-command
~/.ssh/rdp-tunnel.sh start "%g-%p" 63394:192.168.8.176:3389 tunnel-name-1
post-command
~/.ssh/rdp-tunnel.sh stop "%g-%p" 63394:192.168.8.176:3389 tunnel-name-1
you can and should use this script to access anything, I use it constantly to access systems and services that do not have a public ip going through 1,2,3,4,5 or more ssh proxies
see more into :
Refs: