Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #3941

Closed
Open
Opened Sep 06, 2011 by Erinn Clark@erinn

Windows users + firewalls having trouble with automatic port selection

We've been seeing a lot of complaints from Windows users with firewalls who experience apparently random behavior in whether their tor in TBB connects successfully. It gets to Bootstrapped 100%: Done and then doesn't do anything else.

After some minor experimentation -- having them turn off (or uninstall) their firewall, and having one revert the TBB settings back to pre-auto days -- I think Windows and firewalls simply can't handle the automatic port selection very well. Tor will connect to an open port (I think) and then not actually be able to send traffic. Since it doesn't connect to the network, but doesn't obviously error, users just wait and get frustrated.

velope had an idea on IRC that there could be a client version of reachability testing for local ports.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#3941