SSH Tunnel

1. You are using SSH key-based authentication

If the server already has your authorized_keys configured, then when you run:

ssh -D 1080 -C -q -N -p ( your ssh port )  yourusername@your_ip_ssh

…and it doesn’t ask for a password, it means the connection is successful because your SSH key is already recognized by the server.

To check if the tunnel is actually active:

netstat -tlnp | grep 1080

Or using ss:

ss -tlnp | grep 1080

You should see output like this:

tcp   LISTEN  0  128  127.0.0.1:1080  *:*  users:(("ssh",pid=xxxx,fd=3))

That means your SOCKS proxy is running on port 1080 ✅

---

🔹 2. You’re running SSH without a login shell (because of the -N option)

The -N option means no remote command or shell session will be opened, so you won’t see any login prompt or output.
That’s also normal — the tunnel stays active in the background.

If you remove -q and -N, for example:

ssh -D 1080 -C -p (port) yourUsersername@your_ip_ssh_server

you’ll enter the remote shell (you’ll see the login prompt and normal SSH output).

---

🔹 3. Check if the tunnel is really working

Try setting your browser as follows:

• SOCKS Host: 127.0.0.1
• Port: 1080
• SOCKS v5
• Check “Proxy DNS through SOCKS v5”

Then open https://whatismyipaddress.com/
→ If your IP changes to your SSH server’s IP, it means the tunnel is working properly. ✅