I require Linux help... specifically SSH...

[Immanuel]

I am trying to create a SOCKs proxy on my local Bitcoin server. It ends up I have no idea what I am doing. I entered the following commands:

sudo ssh -ND 443 <my server's hostname>@<my ip address>
sudo ssh -ND 9999 <my server's hostname>@<my ip address>

I forwarded the ports on my router. In short, it doesn't work. How do I revert these commands?

[1715219573]

1715219573

[1715219573]

1715219573

[omegadraconis]

I am trying to create a SOCKs proxy on my local Bitcoin server. It ends up I have no idea what I am doing. I entered the following commands:

sudo ssh -ND 443 <my server's hostname>@<my ip address>
sudo ssh -ND 9999 <my server's hostname>@<my ip address>

I forwarded the ports on my router. In short, it doesn't work. How do I revert these commands?

Run "ps", that should list the processes running. Once you find the pid's of the commands above you can issue a "kill" command for the pid.

You could also use "top" to see a list of the active processes on the system. Once in top if you hit k and then enter the pid it will kill the process.

[Immanuel]

I am trying to create a SOCKs proxy on my local Bitcoin server. It ends up I have no idea what I am doing. I entered the following commands:

sudo ssh -ND 443 <my server's hostname>@<my ip address>
sudo ssh -ND 9999 <my server's hostname>@<my ip address>

I forwarded the ports on my router. In short, it doesn't work. How do I revert these commands?

Run "ps", that should list the processes running. Once you find the pid's of the commands above you can issue a "kill" command for the pid.

You could also use "top" to see a list of the active processes on the system. Once in top if you hit k and then enter the pid it will kill the process.

Alright, I'll try this when I get home. Port 22 is blocked at my school. >_< Thank you!

[theymos]

sudo ssh -ND 443 <my server's hostname>@<my ip address>
sudo ssh -ND 9999 <my server's hostname>@<my ip address>

You would run these commands with the SSH on the non-server computer. Then you'd connect to localhost:443 or localhost:9999 with SOCKS. Also, it's remoteUsername@remoteIP; you're connecting to the user at the IP.

You could use antinat to set up a SOCKS server on your server. Then you wouldn't have to run SSH on the non-server computer.

[Immanuel]

sudo ssh -ND 443 <my server's hostname>@<my ip address>
sudo ssh -ND 9999 <my server's hostname>@<my ip address>

You would run these commands with the SSH on the non-server computer. Then you'd connect to localhost:443 or localhost:9999 with SOCKS. Also, it's remoteUsername@remoteIP; you're connecting to the user at the IP.

You could use antinat to set up a SOCKS server on your server. Then you wouldn't have to run SSH on the non-server computer.

Yeah, I see where I am going wrong. Thanks!