Difference between revisions of "SSH"

From DiLab
Jump to: navigation, search
(Tunneling between any two ports)
Line 10: Line 10:
== Tunneling between any two ports ==
== Tunneling between any two ports ==


Say, you want to read aremote server webpage, but there is only ssh port open on the server. Then you can create a tunnel, like this:
Say, you want to read a remote server web page, but there is only ssh port open on the server. If you have a valid user account to the server, then you can create a tunnel, like this:


$ ssh -f user@server.com -L 8080:server.com:80 -N
$ ssh -f user@server.com -L 8080:server.com:80 -N
Line 16: Line 16:
Now you can enter the following in your browser: http://server.com:8080
Now you can enter the following in your browser: http://server.com:8080


Or in general, -f means sit in background and -N menas do not execute any command:
Or in general


$ ssh -f user@server.com -L my-local-port:server.com:server-port -N
$ ssh -f user@server.com -L my-local-port:server.com:server-port -N

Revision as of 14:38, 14 July 2010

Tunneling to socks proxy

From here: ssh-tunnel-socks-proxy

In short:

$ssh -D 9999 username@ip-address-of-ssh-server
Then set in Firefox to use a SOCKS proxy: “localhost", port 9999


Tunneling between any two ports

Say, you want to read a remote server web page, but there is only ssh port open on the server. If you have a valid user account to the server, then you can create a tunnel, like this:

$ ssh -f user@server.com -L 8080:server.com:80 -N

Now you can enter the following in your browser: http://server.com:8080

Or in general, -f means sit in background and -N menas do not execute any command:

$ ssh -f user@server.com -L my-local-port:server.com:server-port -N