Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • 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
  • #6939
Closed (moved) (moved)
Open
Created Sep 22, 2012 by shamrock@shamrock

Missing IPv6 ORPort reachability check

Issue: Tor does not log (or does not perform) a test to determine if an IPv6 ORPort is reachable.

Tor does log a corresponding test for an IPv4 ORPort.

Environment: Debian squeeze amd64, latest patches Tor version 0.2.4.2-alpha (git-0537dc6364594474)

How to reproduce:

  • configure Tor with both IPv4 and IPv6 IP addresses and OrPorts.
  • start Tor
  • the Tor log file will show a test to determine if the IPv4 OrPort is reachable, but not if the IPv6 ORPort is reachable.
  • (this particular system was configured as a bridge)

Expected Behavior: The user might expect to see a log entry for IPv6 that corresponds to the following log entry for IPv4:

"Sep 22 11:09:21.000 [notice] Now checking whether ORPort [host's IPv4 address]:443 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)"

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