You can use port forwarding on ssh. 1. Open a terminal and run: On your local system: ssh -L 6000:<target_server_ip>:22 <proxy_server_user>@<proxy_server_ip> You should be connected to the proxy now. You can substitute 6000 with any port. 2. (optional) Test Now you can ssh into the target server on another terminal with: ssh -p 6000 <target_server_user>@localhost … Read more
Try this one-liner: rsync -av -e “ssh -A root@proxy ssh” ./src root@target:/dst
Netcat is your friend: nc -z localhost 6000 || echo “no tunnel open”
Solved it! The thing was to connect to the correct server when creating the tunnel itself – should’ve seen that one coming. ssh -f user@ssh.example.com -L 3307:mysql1.example.com:3306 -N Then mysql -h 127.0.0.1 -P 3307 worked as intended. 🙂
1) Assuming you connect from home to foo, you need a reverse tunnel (-R) ssh -R 8080:localhost:3000 foo.mycompany.com This will enable processes running at foo to connect to localhost:8080 and actually speak to your home computer at port 3000. If you want other computers at your work to be able to connect to foo:8080 and … Read more
Using your hosts network as network for your containers via –net=host or in docker-compose via network_mode: host is one option but this has the unwanted side effect that (a) you now expose the container ports in your host system and (b) that you cannot connect to those containers anymore that are not mapped to your … Read more
Yes, it is possible: ssh -L 8443:serverA:443 -Nf [user@]<serverB> This will let you point your desktop browser at port 8443 and send it to port 443 (the HTTPS port) on your server A. The -Nf will background the session and exit immediately back to your desktop, not establishing an actual shell session to server B.
3) A netcat tunnel is created from bastion.com to port 22 of final.com. false, there’s no netcat. 1) The user enters ssh final on localhost. This launches the parent ssh process 2) The parent ssh creates a child ssh with I/O redirected to pipes 3) The child ssh creates a connection to bastion.com. 4) The … Read more
Wouldn’t a VPN be more appropriate? OpenVPN is super simple to configure. Here is a sample config and some links to guide your through the certificate creation process: apt-get install openvpn mkdir /etc/openvpn/easy-rsa mkdir -p /etc/openvpn/ccd/client_server touch /etc/openvpn/ipp.txt cp -a /usr/share/doc/openvpn/examples/easy-rsa/2.0/* /etc/openvpn/easy-rsa cd /etc/openvpn/easy-rsa source ./vars ./clean-all ./build-ca ./build-dh ./build-key-server server cd /etc/openvpn/easy-rsa/keys openssl pkcs12 … Read more
The syntax of the ssh_config file was correct – so the error had to be somewhere else. The command line which worked was: ssh 12.34.56.78 -L 8888:localhost:8000 but in the LocalForward directive, you used the “real” IP address. Obviously, the app just listened to localhost – either change the listen interface in the app, or … Read more