Update longclaw's IPv4 address (after it moves)
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?
- Clients with a consensus will use whatever address longclaw signs in its relay descriptor
- Clients without a consensus:
- 0.2.8 and later try multiple authorities without waiting for failures, so they will be fine
- 0.2.4, 0.2.6, and 0.2.7 are no longer supported: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- teor changed milestone to %Tor: 0.3.2.x-final in legacy/trac
changed milestone to %Tor: 0.3.2.x-final in legacy/trac
- teor added component::core tor/tor in Legacy / Trac milestone::Tor: 0.3.2.x-final in Legacy / Trac points::0.5 in Legacy / Trac priority::medium in Legacy / Trac resolution::implemented in Legacy / Trac review-group-24 in Legacy / Trac severity::normal in Legacy / Trac status::closed in Legacy / Trac tor-dir-auth in Legacy / Trac type::defect in Legacy / Trac version::tor 0.2.6.2-alpha in Legacy / Trac labels
added component::core tor/tor in Legacy / Trac milestone::Tor: 0.3.2.x-final in Legacy / Trac points::0.5 in Legacy / Trac priority::medium in Legacy / Trac resolution::implemented in Legacy / Trac review-group-24 in Legacy / Trac severity::normal in Legacy / Trac status::closed in Legacy / Trac tor-dir-auth in Legacy / Trac type::defect in Legacy / Trac version::tor 0.2.6.2-alpha in Legacy / Trac labels
- Owner
Do we know when this will happen? Or when we will know the new IP?
Trac:
Status: new to needs_information Trac:
Cc: micah to micah, dcfI 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.
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.)
Address updated in stem (and by extension the doctor checks): https://gitweb.torproject.org/stem.git/commit/?id=0d5d930
- Owner
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? :)
Added to OONI scan lists. https://github.com/OpenObservatory/ooni-resources/pull/8
- Owner
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.
Trac:
Status: new to merge_ready - Owner
Err, that should be
bug23592_025
. - Owner
review-group-24 is now open.
Trac:
Keywords: N/A deleted, review-group-24 added - Owner
Merged to 0.2.5 and forward.
Trac:
Resolution: N/A to implemented
Status: merge_ready to closed - Trac closed
closed
- Trac changed time estimate to 4h
changed time estimate to 4h
- Trac moved from legacy/trac#23592 (moved)
moved from legacy/trac#23592 (moved)
- Trac removed 1 deleted label
removed 1 deleted label