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
  • #30639

Closed (moved)
Open
Opened May 27, 2019 by Georg Koppen@gk

Tor tries to connect over IPv6 in IPv4 networks with ClientAutoIPv6ORPort set

In #29641 (moved) we set ClientAutoIPv6ORPort 1 to help users in IPv6-only networks. However, that leads to bootstrap errors, presumably because Tor is trying to use IPv6 in IPv4-only networks. See e.g.:

https://blog.torproject.org/comment/281976#comment-281976 https://blog.torproject.org/comment/282102#comment-282102

I've seen this myself as well when bootstrapping on a Windows machine at least. Just hitting the "Reconfigure" option and choosing "Connect" again "solved this issue.

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