SSH Port Forwarding -D not working anymore

apache-2.2port-forwardingPROXYssh

I have a virtual server in the US. When I first set it up I was able to use dynamic port forwarding with

ssh -D PORTNUMBER serveraddress

After that I could set up Firefox to use that as SOCKS5 proxy.
I don't know what changed, but for some reason that doesn't work anymore.

Is there a place, where it is set if tunneling is allowed or not? I tried ssh_config file, there was in fact a

Tunnel yes/no

option, but even after switching it to yes and restarting, it didn't change anything.

Where should I look?

EDIT (01:41 GMT+1):
The output with -vvv options is rather long, therefore uploaded it to pastebin. I hopefully removed all sensitive data:
http://pastebin.com/r4BVC5F1

EDIT (02:13 GMT+1):
New output file: http://pastebin.com/VvPVv0ff

I added the "PermitTunnel" option in my config file, now I can log in with -vvv active. However the proxy still won't work. I havent changed on settings on the client side, at least none that I know of. And yes, I 'm using Mac OSX.

EDIT (09:45 GMT+1):
Could this have anything to do with messed up hostnames? Or maybe dante or squid configurations intereferring? I seriously don't know, why it's not working anymore…

LAST EDIT:
OK, I'm just plainly stupid! Seriously. Everything worked fine. The problem was that I typed in the IP address of my server into the SOCKS server settings. Which can't possibly work. localhost ist of course the right answer. Darn… wasted so much time… Thanks everyone!

Best Answer

There is also an option called PermitTunnel. Make sure this is set to yes. If you can't find it, add it.

In your -vvv-log, it says Exit status 127, this is set by bash when it can not find the command. This could mean it's a client problem. I think you are using OSX, right?

Can you connect to another server? Maybe localhost? Has anything changed to your ssh-client installation? Nothing in .ssh/config?

Related Solutions

SSH Port Forwarding – Comprehensive Guide

SSH remote port forwards will default binding to localhost/loopback for security purposes. It's not often preferable to allow other hosts access to your forwarded ports.

To override this behaviour you will need to do two things:

Enable the GatewayPorts option on the server.
Specify a bind address, or * to bind to all addresses, on the client.
```
ssh -R \*:8000:localhost:22 user@public
```

Escape the asterisk to ensure that your shell doesn't expand it.

Ssh – How to automate SSH login with password

Don't use a password. Generate a passphrase-less SSH key and push it to your VM.

If you already have an SSH key, you can skip this step… Just hit Enter for the key and both passphrases:

$ ssh-keygen -t rsa -b 2048
Generating public/private rsa key pair.
Enter file in which to save the key (/home/username/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/username/.ssh/id_rsa.
Your public key has been saved in /home/username/.ssh/id_rsa.pub.

Copy your keys to the target server:

$ ssh-copy-id id@server
id@server's password:

Now try logging into the machine, with ssh 'id@server', and check-in:

.ssh/authorized_keys

Note: If you don't have .ssh dir and authorized_keys file, you need to create it first

to make sure we haven’t added extra keys that you weren’t expecting.

Finally, check to log in…

$ ssh id@server

id@server:~$

You may also want to look into using ssh-agent if you want to try keeping your keys protected with a passphrase.

Best Answer

Related Solutions

SSH Port Forwarding – Comprehensive Guide

Ssh – How to automate SSH login with password

Related Topic