Daniel Boone
I missed your SOCKS question.
If you do not intend to directly use this Tor instance to access the Tor network, you should leave the SocksPort as it was. By default Tor only listens on localhost:9050 (as the documentation indicates). Therefore, even if you *do* intend to use this Tor instance to access the Tor network, by default you can already point your applications towards localhost:9050.
So in most cases, this option can be left alone so the default configuration can do its thing. Either you won't use the SOCKS proxy and it is harmlessly listening on localhost anyway, or you are like most people and don't need it to listen on non-localhost non-9050. For either case, the default behavior is fine.
Hope this helps.
Matt
On 09/03/2016 03:55 PM, daniel boone wrote:
I got a couple of question to ask on the torrc file and I hope one of you will direct me.
Ok here we go. I got it working as a relay which i can see in the terminal. I just started so it is still testing bandwidth. but this is not my questions
- on line 18 of mine it is about Socks. I was reading in the man pages
on this. It was #Socksport 9050. Per the man pages I took out the comment and placed as "+" per the page. So now it is *+SOCKSPort 9050 # Default: Bind to localhost:9050 for local connections.*