Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #4904

Closed (moved)
(moved)
Open
Created Jan 14, 2012 by Roger Dingledine@arma

tor-resolve falsely says can't resolve if answer is 127.0.0.1

$ tor-resolve localhost.seul.org
Jan 14 18:52:47.884 [warn] Got SOCKS5 status response '4': host is unreachable

In my logs I have

Jan 14 18:52:47.884 [info] connection_edge_process_relay_cell_not_open(): Got a resolve with answer 127.0.0.1.  Rejecting.

Trying to connect to 127.0.0.1 over Tor is a poor move. But knowing that a given address resolves to it? I can imagine situations where you'd want that info, rather than being told that the address doesn't resolve.

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