Skip to content
GitLab
Projects Groups Topics 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
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #30084
Closed (moved) (moved)
Open
Issue created Apr 08, 2019 by cypherpunks@cypherpunks

Relay: channel_tls_process_netinfo_cell private IP as public wrongly reported

Log output: Nov 06 17:11:10.000 [info] {OR} channel_tls_process_netinfo_cell(): We made a connection to a relay at 92.167.89.160:9001 (fp=427E5C8ADC43B09582DDDA80EA8EDFBD05DF5003) but we think they will not consider this connection canonical. They think we are at 10.42.194.61, but we think its 92.222.41.125.

Nov 06 17:30:35.000 [info] {OR} channel_tls_process_netinfo_cell(): Got good NETINFO cell from 92.167.89.160:9001; OR connection is now open, using protocol version 5. Its ID digest is 033DC13D5639A530C098388D8F53A693D76AD59B. Our address is apparently 10.42.194.61.

10.42.194.61 does not exist in Intranet. It's reported wrongly by remote relay.

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