Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#13100 closed defect (fixed)

gabelmoo moves IP addresses

Reported by: Sebastian Owned by:
Priority: Medium Milestone: Tor: 0.2.3.x-final
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: karsten Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

We shouldn't forget to include it in 0.2.5.x-stable. Maybe backportable? Any other things to consider?

Child Tickets

Change History (6)

comment:1 Changed 5 years ago by Sebastian

I can forward traffic from the old address to the new until november.

comment:2 Changed 5 years ago by nickm

Here's how we should do this: As soon as the new address works, we should patch it in all supported versions. (Please let me know when that is.)

I'm told that the new address is 131.188.40.189.

As long as the old address works, we don't need to kludge it in at the directory authorities: we can just patch it in the source, and let the authorities upgrade before November.

comment:3 Changed 5 years ago by Sebastian

Cc: karsten added

The new address already has a relay running there and it works. I'm waiting on karsten to fetch the exported files via http rather than from the old gabelmoo host via ssh for the move.

comment:4 Changed 5 years ago by Sebastian

The move is completed.

Branch gabelmoo_move in my repository. I based it on 0.2.4 - are we still supporting 0.2.3? Happy to base the branch on that, or it should be easily cherry-pickable.

I have also updated the dirauth-conf repo for those dirauth ops that want to use it.

comment:5 Changed 5 years ago by arma

Resolution: fixed
Status: newclosed

I merged the commit into everything from maint-0.2.3 up. Closing as done -- please reopen if I screwed anything up. Thanks!

comment:6 Changed 5 years ago by arma

Milestone: Tor: 0.2.5.x-finalTor: 0.2.3.x-final
Note: See TracTickets for help on using tickets.