New answers tagged ssh-tunneling
With ssh -D 8080 yourserver you can start a SOCKS proxy to your home server. Configure your client to use localhost:8080 as SOCKS proxy.
You can install zebedee in a USA VPS or dedicate and install squid beside it , then install zebedee client then enjoy it. Server side of it: zebedee -s -U But you have to write a config file for client: server false localsource true multiuse true tunnel 81:IP_OF_SERVER:3128 compression zlib:9 detached true You can use localhost:81 in your browser. For ...
You can use "Hola better internet" extension for Chrome browser.
This looks like the linux host is configured to be some sort of RDP gateway. The command will initiate a SSH session to itself (root@localhost), start a local listener on port 3300 (L 3300:) to forward all traffic to a Windows machine on port 3389 (remote_WIN_machine1:3389), typical for RDP. I suspect that the GatewayPorts directive is set to yes in ...
It should work fine, assuming you are not observing any errors with ssh. I would test with telnet to port 8989 and also look at netstat -an for listening connections and make sure you see connections being established all the way
ssh -D works at(via man ssh) Specifies a local ``dynamic'' application-level port forwarding. This works by allocating a socket to listen to port on the local side Then what's a socket?via A socket is just a logical endpoint for communication. They exist on the transport layer. You can send and receive things on a ...
Yes. I use Firefox with it that way on a fedora 19 system
You said, in the comments, After restarting my computer, when trying to login via ssh again, I was asked the password to unlock the id_dsa file There's at least part of the answer. Your other tools have no ability to unlock a private key, and no ability to talk to ssh-agent to have it authenticate on their behalf. You need to remove the password from ...
I was just searching for this and came across the same (or similar) question on stack overflow. On client A ssh -R \*:24680:localhost:12345 serverS and then (still on client A) ssh -D 12345 localhost  You need to the \* bit so it will bind to server S's public IP address and not just localhost. Then on client B simply connect to the socks server at ...
Top 50 recent answers are included