Author: moritz Date: 2013-03-06 11:01:46 +0000 (Wed, 06 Mar 2013) New Revision: 26077 Modified: website/trunk/docs/en/faq.wml Log: TBB uses 9150 now, removed info about auto port selection Modified: website/trunk/docs/en/faq.wml =================================================================== --- website/trunk/docs/en/faq.wml 2013-03-05 21:49:41 UTC (rev 26076) +++ website/trunk/docs/en/faq.wml 2013-03-06 11:01:46 UTC (rev 26077) @@ -955,24 +955,15 @@ Browser Bundle. How do I predict my Socks port?</a></h3> <p> -Typically Tor listens for Socks connections on port 9050. TBB -on OSX and Linux has an experimental feature where Tor listens -on random unused ports rather than a fixed port each time. The -goal is to avoid conflicting with a "system" Tor install, +Typically Tor listens for Socks connections on port 9050. TBB listens +on port 9150. +The goal is to avoid conflicting with a "system" Tor install, so you can run a system Tor and TBB at the same time. We're <a href="https://trac.torproject.org/projects/tor/ticket/3948">working on a feature</a> where Tor will try the usual ports first and then back -off to a random choice if they're already in use. Until then, if you -want to configure some other application to use Tor as a Socks proxy, -here's a workaround: +off to a random choice if they're already in use. </p> -<p> -In Vidalia, go to Settings->Advanced and uncheck the box that says -'Configure ControlPort automatically'. Click OK and restart TBB. Your -Socks port will then be on 9050. -</p> - <hr> <a id="TBBPolipo"></a>