Might be a little off-topic but I don't know maybe it's more related to tor than networking.

Basically, I have the following scenario I want to accomplish:

home access point is,

computer-1 is,

computer-2 is

and phone-3 is

On computer-1 [] I have a tor circuit established on its localhost:9050 (default torrc config etc..). I can use this circuit from computer-1 only.

What I'd like to do is make computer-1's localhost:9050 availalbe to computer-2 and phone-3 and all other devices on the network, so they can use it when they want. I want to accomplish this without changing anything in the way the circuit is opened on computer-1.

I am not good in networking, I guess I should maybe open the 9050 external port on computer-1? It runs debian and I tried with iptables -A INPUT -p tcp --dport 9050 -j ACCEPT with no success.

Thanks to any help in advance.


You have to use SocksPort option to specify not just the port, but IP+port explicitly. You will need to have two lines: one for localhost, one for so it will be available for the localhost apps and for remote ones

  • Thank you, a little out-dated guidance but I managed in the end, here is what I went through: [notice] Read configuration file "/etc/tor/torrc". [warn] Skipping obsolete configuration option 'SocksListenAddress' [warn] Option 'SocksListenAddress' used more than once; all but the last value will be ignored. [warn] Skipping obsolete configuration option 'SocksListenAddress' [notice] Opening Socks listener on [notice] Opened Socks listener on Looks like an old argument, I pondered around and found the very exact new vrsion of sockslistenaddress: SocksPort Feb 5 '19 at 0:49
  • So adding these two lines: SocksPort SocksPort (instead of sockslistenaddress) did the trick. Feb 5 '19 at 0:53
  • maybe update and clean out the answer now Feb 5 '19 at 0:53
  • SocksPort is working also, in the very same way - be sure and double-check for the lines for localhost and LAN SEPARATELY
    – Alexey Vesnin
    Feb 5 '19 at 1:00
  • 1
    ok so I am confused, what is the difference between adding SocksPort SocksPort to torrc and editing TorAddress TorPort 9050 in torsocks.conf? And does the option AllowInbound 1 in torsocks.conf have anything to do with this as well? Feb 5 '19 at 14:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.