Hi, I have a fedora32 system behind a firewall without any access from the outside. I'd like to build a reverse ssh tunnel so I can get to it from my remote location while working remotely. I'm familiar with how remote ssh tunnels work, but can't quite get systemctl to create a proper service, presumably because ssh expects to be tied to a terminal.
I've built the following shell script. I believe "bash -s" can be used to spawn processes not connected to a terminal.
# cat /etc/init.d/ssh-tunnel.sh #!/bin/bash -s ssh -i /root/.ssh/orion-key -R 43022:localhost:22 root@orion.example.com I was using this script in a unit file, but got closer to what I want by placing the ssh command itself into the unit file as the ExecStart parameter.
# cat /etc/systemd/system/connection.service [Unit] Description=Reverse SSH to orion After=network.target
[Service] Type=forking #EnvironmentFile=-/etc/sysconfig/sshd-permitrootlogin #EnvironmentFile=-/etc/sysconfig/sshd #ExecStart=/etc/init.d/ssh-tunnel.sh ExecStart=ssh -tt -i /root/.ssh/orion-key -R 43022:localhost:22 root@orion.example.com #ExecReload=/bin/kill -HUP $MAINPID User=root KillMode=process Restart=on-failure #RestartSec=42s
[Install] WantedBy=multi-user.target I also read that -tt can be passed to ssh to start it on a pseudo-terminal.
I then added the unit file as a service using "systemctl enable connection.service"
Can someone guide me on the unit parameters I should be using for this? Should Type=forking?