Hot answers tagged ssh-tunneling
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; ...
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.
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 ...
Only top voted, non community-wiki answers of a minimum length are eligible