Difference between revisions of "SSH"
(New page: == Tunneling to socks proxy == From here: [http://ubuntu.wordpress.com/2006/12/08/ssh-tunnel-socks-proxy-forwarding-secure-browsing/ ssh-tunnel-socks-proxy] In short: $ssh -D 9999 usern...) |
|||
| Line 6: | Line 6: | ||
$ssh -D 9999 username@ip-address-of-ssh-server |
$ssh -D 9999 username@ip-address-of-ssh-server |
||
Then set in Firefox to use a SOCKS proxy: “localhost", port 9999 |
Then set in Firefox to use a SOCKS proxy: “localhost", port 9999 |
||
== 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: |
|||
$ 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 |
|||
$ ssh -f user@server.com -L my-local-port:server.com:server-port -N |
|||
Revision as of 14:35, 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 aremote server webpage, but there is only ssh port open on 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
$ ssh -f user@server.com -L my-local-port:server.com:server-port -N
