New answers tagged ssh-tunneling
There are Tunnels and Port fowardings. You are talking about the second of them. Just not to confuse terms, ok? (1) For Local port forwarding the forwarded combination host:port on local computer is blocked (accepts connections). On the other side remote_host:remote_port is available for different connections. The data are send after you start the ...
netstat and lsof or fuser are typical programs to view what ports are opened by what (though may require root or such access, depending, and vary by flavour of unix). A shared destination port is fine. It may help to work through e.g. Beej's guide to networking to understand the system calls involved. If the client has not connected, then any ports it ...
On a Linux client, you may view listening ports with netstat -lnp |less. Within an ssh session, you can press enter twice, then type ~#. That will list the currently forwarded ports for that session.
Are you sure you use the correct username ? AWS uses different usernames depending on Linux distro. AFAIK, they generally use 'ec2-user' except for Ubuntu installations where they use 'ubuntu'.
This can be done by your router. On some router this feature is called Virtual Server See in below part of image there are two examples of port forwarding. One is of Web and another one is of SSH. In first case any request on your WAN IP i.e. the IP of your router with port 80 will be forwarded to a LAN IP ( 192.168.2.4 in this case) With this feature you ...
I wouldn't try to use multihop proxy but using the intermediate host as a SSH relay for accessing the bastion. From there you can setup your SOCKS proxy. Configure access to the host at work First configure access to host-at-work: Host host-at-work User myself Configure access to the bastion Then we configure the access to the bastion. We use ...
Well, I found an answer: ssh -t -v -A -D9932 -L9933:localhost:9933 -L9934:localhost:9934 FIRST-HOST ssh -D9933 -L9934:localhost:9934 -A -t -v ec2-user@SECOND-HOST ssh -D9934 -A -t -v ec2-user@THIRD-HOST using 9934 as the socks proxy port. Obviously can be mapped to .ssh/config as needed. credits to second link in my question.
Well, this "I have no root" acces on Server A can be a problem to create a good vpn solution since: ip-ip tunneling requires interface manipulation; pptp also requires root privileges to create interfaces; OpenVPN can even run as unprivileged user, but some tricks need to be done like allowing sudo to the ip command to allow the creation of tun interface; ...
You may run an ss command (the modern version of netstat) on the remote system: ssh me@remote ss -ntp | grep 4030 but better still you should use autossh (it exists on all distros). It checks automatically whether a reverse tunnel is operating and, after some user-defined amount of time without receiving pings has elapsed, automatically restarts the ...
Top 50 recent answers are included