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
  • #25295
Closed
Open
Created Feb 18, 2018 by Trac@tracbot

Torsocks only accepts IPv4 replies but Tor prefers IPv6Automap by default

At the moment, MapAddress .exit entries won't resolve through torsocks for me, because tor gives an IPv6 reply, and torsocks is only designed for IPv4 replies.

Torsocks gives the characteristic error [socks5] Resolve destination buffer too small (in socks5_recv_resolve_reply() at socks5.c:681) when tor replies with an IPv6 address, which it does every single time for mapaddress .exit entries for me.

Trac:
Username: fuzzyTew

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