Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Arti Arti
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 138
    • Issues 138
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • ArtiArti
  • Issues
  • #92
Closed
Open
Created Mar 15, 2021 by Nick Mathewson@nickm⛰Owner

Automatically detect and tolerate IPv6-only environments

Arti should be able to detect when it's running without the ability to connect to an IPv4 address, and behave reasonably in those cases.

This ticket relates to #329 (closed) and #93 (closed); although "IPv6-only" is one common kind of address restriction that a client might have, it's not the only such restriction.

Also, detection can be tricky: a lack of IPv6 interface means that we can't connect to IPv6, but the presence of an IPv6 interface doesn't mean that it's usable.

Edited Mar 02, 2022 by Nick Mathewson
Assignee
Assign to
Time tracking