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 313
    • Issues 313
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • 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
  • #40283
Closed
Open
Created Feb 09, 2021 by David Goulet@dgoulet🔆Owner

relay: Don't fail if AF_INET6 family is not supported

Someone on tor-relays@ reported that when going from 044 to 045, their config failed to work:

ORPort 587
DIRPORT 995

with :

[notice] Opening OR listener on 0.0.0.0:587
[notice] Opened OR listener connection (ready) on 0.0.0.0:587
[notice] Opening OR listener on [::]:587
[warn] Socket creation failed: Address family not supported by protocol
[notice] Opening Directory listener on 0.0.0.0:995
[notice] Closing partially-constructed OR listener connection (ready) on 
0.0.0.0:587
[notice] Closing partially-constructed Directory listener connection 
(ready) on 0.0.0.0:995

We should probably not fail this in that implicit case for IPv6 if the address is not supported.

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