Opened 2 years ago

Closed 2 years ago

#23592 closed defect (implemented)

Update longclaw's IPv4 address (after it moves)

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: 0.3.2.x-final
Component: Core Tor/Tor Version: Tor: 0.2.6.2-alpha
Severity: Normal Keywords: tor-dir-auth, review-group-24
Cc: micah, dcf Actual Points:
Parent ID: Points: 0.5
Reviewer: Sponsor:

Description

Longclaw will soon move IPv4 addresses. Its current address was added in 0.2.6.2-alpha.

Will it have multiple IPv4 addresses?
(One for the hard-coded address, and one for the consensus?)

How does this impact 0.2.5 clients?

Child Tickets

Change History (15)

comment:1 Changed 2 years ago by nickm

Status: newneeds_information

Do we know when this will happen? Or when we will know the new IP?

comment:2 Changed 2 years ago by micah

Cc: hacim added

comment:3 Changed 2 years ago by micah

Cc: micah added; hacim removed

comment:4 Changed 2 years ago by dcf

Cc: dcf added

comment:5 Changed 2 years ago by micah

I am hoping that I can complete the hardware work that needs to be done next week. After that it is about another week and then I can move longclaw. So I think 2-3 weeks max. My goal is to have this done before the tor meeting in Montreal.

I will be able to forward IPs for a while afterwards without any trouble.

comment:6 in reply to:  5 Changed 2 years ago by teor

Replying to micah:

I am hoping that I can complete the hardware work that needs to be done next week. After that it is about another week and then I can move longclaw. So I think 2-3 weeks max. My goal is to have this done before the tor meeting in Montreal.

Excellent.
While longclaw is down, we will only have 3 bandwidth authorities.
How long will longclaw be down for?

I will be able to forward IPs for a while afterwards without any trouble.

This is great, especially for 0.2.5 client bootstrap.

(Longclaw was introduced in 0.2.4, we no longer support 0.2.4, 0.2.6 or 0.2.7, and 0.2.8 onwards have fallback directory mirrors for bootstrap.)

comment:7 Changed 2 years ago by micah

longclaw has moved, it is now available at 199.58.81.140

edit: fixed ip

Last edited 2 years ago by micah (previous) (diff)

comment:8 Changed 2 years ago by teor

Status: needs_informationnew

comment:9 Changed 2 years ago by atagar

Address updated in stem (and by extension the doctor checks): https://gitweb.torproject.org/stem.git/commit/?id=0d5d930

comment:10 in reply to:  7 Changed 2 years ago by nickm

Replying to micah:

longclaw has moved, it is now available at 199.58.81.140

edit: fixed ip

At your convenience, could you confirm that either by a PGP signature or by telling me in person? :)

comment:12 Changed 2 years ago by nickm

Status: newmerge_ready

bug23774_032 has this; Micah has confirmed in person. I will merge this after I'm back home and can check the pgp sig too.

comment:13 Changed 2 years ago by nickm

Err, that should be bug23592_025.

comment:14 Changed 2 years ago by nickm

Keywords: review-group-24 added

review-group-24 is now open.

comment:15 Changed 2 years ago by nickm

Resolution: implemented
Status: merge_readyclosed

Merged to 0.2.5 and forward.

Note: See TracTickets for help on using tickets.