Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #17850

Closed (moved)
(moved)
Open
Created Dec 14, 2015 by Trac@tracbot

other relays can confuse NATed relays

This is from /var/log/tor/log:

Dec 13 02:21:00.000 [notice] Our IP Address has changed from 91.45.222.226 to 104.233.75.228; rebuilding descriptor (source: 104.233.75.165).
Dec 13 02:21:12.000 [notice] We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish. [701 similar message(s) suppressed in last 600 seconds]
Dec 13 02:21:35.000 [notice] Our IP Address has changed from 104.233.75.228 to 91.45.222.226; rebuilding descriptor (source: 217.79.179.177).

It looks like .228 is confused causes my relay to advertise the wrong IP address for several seconds.

Maybe a NATed OR should self-test its reachability before advertising the new IP address.

Trac:
Username: herzi

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