Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 823
    • Issues 823
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 30
    • Merge requests 30
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #4617
Closed
Open
Created Nov 30, 2011 by Linus Nordberg@linus

IPv6 bridge address might go unused

Configure a client with the IPv4 and the IPv6 address of a bridge. One of them are going to be "preferred", as pointed out in logs (notice level). It happens to be the first Bridge line that becomes preferred. Regardless of which is preferred, two connections will be established with the bridge, one over IPv4 and one over IP6. When the IPv6 address of a bridge is reported to be preferred, the IPv4 address will still be used, it seems.

This is because we already have a connection, the IPv4 one, so there's no attempt of setting up a second to the same bridge.

This bug should be fixed as part of the work with making the connection code aware of the multitude of addresses, probably by replacing the node->is_running flag with a flag per node address.

The workaround for clients that don't want to use the IPv4 address of a given bridge is to remove it from the configuration.

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