Bitcoin Forum
June 23, 2018, 02:27:36 PM *
News: Latest stable version of Bitcoin Core: 0.16.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: I require Linux help... specifically SSH...  (Read 2184 times)
Immanuel
Member
**
Offline Offline

Activity: 73
Merit: 10


View Profile
September 08, 2010, 11:40:39 PM
 #1

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?

"I swear by my life, and my love of it, that I will never live for the sake of another man, nor ask another man to live for mine."
1529764056
Hero Member
*
Offline Offline

Posts: 1529764056

View Profile Personal Message (Offline)

Ignore
1529764056
Reply with quote  #2

1529764056
Report to moderator
1529764056
Hero Member
*
Offline Offline

Posts: 1529764056

View Profile Personal Message (Offline)

Ignore
1529764056
Reply with quote  #2

1529764056
Report to moderator
1529764056
Hero Member
*
Offline Offline

Posts: 1529764056

View Profile Personal Message (Offline)

Ignore
1529764056
Reply with quote  #2

1529764056
Report to moderator
Automated Bitcoin Fork Extraction Tool WE DO TOUGH WALLETS: BCH | BTG | BCD | SBTC | UBTC | B2X | BCX | BTF Electrum 2FA, Trezor, Ledger, SegWit, Bech32
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1529764056
Hero Member
*
Offline Offline

Posts: 1529764056

View Profile Personal Message (Offline)

Ignore
1529764056
Reply with quote  #2

1529764056
Report to moderator
1529764056
Hero Member
*
Offline Offline

Posts: 1529764056

View Profile Personal Message (Offline)

Ignore
1529764056
Reply with quote  #2

1529764056
Report to moderator
omegadraconis
Jr. Member
*
Offline Offline

Activity: 39
Merit: 0


View Profile
September 09, 2010, 04:00:55 AM
 #2

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.

1HKYXgu9uLp8AQXabYrqbmAGqS73huNM7K
Immanuel
Member
**
Offline Offline

Activity: 73
Merit: 10


View Profile
September 09, 2010, 01:08:39 PM
 #3

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!

"I swear by my life, and my love of it, that I will never live for the sake of another man, nor ask another man to live for mine."
theymos
Administrator
Legendary
*
Offline Offline

Activity: 3066
Merit: 3200


View Profile
September 09, 2010, 01:39:55 PM
 #4

Quote
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.

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
Immanuel
Member
**
Offline Offline

Activity: 73
Merit: 10


View Profile
September 09, 2010, 01:46:37 PM
 #5

Quote
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!

"I swear by my life, and my love of it, that I will never live for the sake of another man, nor ask another man to live for mine."
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!