Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #5610

Closed (moved)
(moved)
Open
Created Apr 12, 2012 by Trac@tracbot

Tor 0.2.2.35 ignores ExcludeExitNodes list, also cannot connect when ExitNodes specified

Installed Vidalia Tor bundle for Win (not the Tor browser bundle), Vidalia 0.2.17 Tor 0.2.2.35. In an effort to ensure the exit node used is in the USA, Added to torrc :

StrictNodes 1 ExcludeExitNodes {AD},{AE},{AF},{AG},{AI},{AL} ( + many other country codes not including US))

However, Tor seems to ignore the list of country codes and will still exit through arbitrary countries in the list. Problem persists though restarts of Tor and the Win7 computer.

Also tried ExitNodes, both with {} , node name, and node signature. ( for example, ExitNodes {us} )

When trying to specify just US exit nodes, the result was Tor not connecting, log displays: Apr 12 16:48:53.777 [Warning] failed to choose an exit server Apr 12 16:48:54.759 [Notice] All routers are down or won't exit or are Excluded -- choosing a doomed exit at random. Apr 12 16:48:54.759 [Warning] No specified non-excluded exit routers seem to be running: can't choose an exit. Apr 12 16:48:54.759 [Warning] failed to choose an exit server

Trac:
Username: stevecrye

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking