Skip to content
GitLab
Projects Groups Topics 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
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 344
    • Issues 344
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • 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
  • #19945

tor 0.2.8.5-rc connecting/binding to 18.0.0.1 (regression)

tor-win32-0.2.8.5-rc.zip and torbrowser-install-6.5a2_en-US.exe

connecting/binding to 18.0.0.1

this was a bug 4 or 5 years ago for mac users, had a ticket and its been solved.

https://trac.torproject.org/projects/tor/ticket/1827

seems tor again is binding to 18.0.0.1

from Roger Dingledine @tor-talk-Aug2016:

Sounds like a regression. A search in the code for "18.0.0.1" led me to get_interface_address6_via_udp_socket_hack(). Looking at the recent commits that mention that function we have: https://trac.torproject.org/projects/tor/ticket/17950 and https://trac.torproject.org/projects/tor/ticket/17951

The ChangeLog entries are:

o Minor features (relay, address discovery): - Add a family argument to get_interface_addresses_raw() and subfunctions to make network interface address interogation more efficient. Now Tor can specifically ask for IPv4, IPv6 or both types of interfaces from the operating system. Resolves ticket 17950.

- When get_interface_address6_list(.,AF_UNSPEC,.) is called and
  fails to enumerate interface addresses using the platform-specific API, have it rely on the UDP socket fallback technique to try and find out what IP addresses (both IPv4 and IPv6) our machine has. Resolves ticket 17951.

That second one looks very related. Hopefully teor and rl1987 will notice and work on a fix. --Roger

in summary tickets are:

https://trac.torproject.org/projects/tor/ticket/1827 https://trac.torproject.org/projects/tor/ticket/17950 https://trac.torproject.org/projects/tor/ticket/17951

thank you

Trac:
Username: landers

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