New answers tagged ssh-tunneling
If you can connect to your SSH server from the hotspot you can tunnel forward a local port to the VPN server. Assuming the VPN is available over TCP: ssh my-raspberry-pi -L9000:vpn.example.com:openvpn`. It won't be very efficient however. If your VPN is using UDP, I don't know any clean off-the-self way to tunnel UDP datagrams over SSH. You could use a ...
How about using agent forwarding? You can enable it in /etc/ssh/ssh_config (or ~/.ssh/config): Host * ForwardAgent yes or add "-A" every time you connect to your proxy: ssh -A user@remote_host By enabling this, you allow your proxy to forward your key to your target machines, so you can freely connect to other machines.
Sounds like autossh (Automatically restart SSH sessions and tunnels) could be something for you: http://www.harding.motd.ca/autossh/ To keep tunnels alive, and to administrate them in general. Should be on most distros base repos, so just use one of the following: apt-get install autossh # deb pacman -S autossh # arch yum install autossh # rhel
I have found this link on SSH ProxyCommand to be a very useful way to enable SSH proxies. It lets you go from Server --to-->proxy---to-->destination very easily and transparently!
Figured out my answer, figured I would post my answer, in case anyone is interested or googles an answer like I did and not find it. So when I did x.x.x.x this was the WAN IP of my remote server. The autossh has not clue of this as the IP is not one of its adapters. If you run ifconfig on the server then you'll get your local loopback of 127.0.0.1 and other ...
Top 50 recent answers are included