Changes between Version 196 and Version 197 of doc/FAQUnanswered


Ignore:
Timestamp:
Apr 23, 2010, 10:49:25 AM (9 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/FAQUnanswered

    v196 v197  
    352352'''What to do (troubleshooting) if browsing slows to a crawl with Tor and Privoxy running in OS X?'''
    353353
    354 My best solution so far is to put these lines in the tor torrc file:
     354Somebody proposed the following solution, which ''should not be used'' as it will break Tor for everyone else.
     355
    355356{{{CircuitBuildTimeout 6
    356357NewCircuitPeriod 3
     
    358359LongLivedPorts 80,23,21,22,706,1863,5050,5190,5222,5223,6667,8300,8888}}}
    359360
    360 I'm sure some people will cringe at "6" for the build timeout. It normally is 60 -- which means that a circuit that is slow enough to need a full minute for creation will be considered fast enough for use. Sadly, a timeout of 5 causes far too many failures -- with a timeout of 6, browsing is "mostly fast". This ensures that the entry and middle nodes will be fast -- it does NOT protect against bad exit nodes. The four nodes that seem to consistently give me trouble are listed as "do not use".
    361 
    362 Finally, port 80 is added to the "long lived ports" list. The idea here is that if a site isn't reliable, web browsing will be likely to have interruptions.
     361CircuitBuildTimeout causes the client to drop an uncompleted circuit after 6 seconds; it will cause your tor to build circuits more aggressively than other nodes.  The default value is 60.
     362
     363Finally, port 80 is added to the "long lived ports" list. This will overload long lived ports, making tor unusable for people who need to use ssh over tor.
    363364
    364365