#23592: Update longclaw's IPv4 address (after it moves) --------------------------+------------------------------------ Reporter: teor | Owner: (none) Type: defect | Status: needs_information Priority: Medium | Milestone: Tor: 0.3.2.x-final Component: Core Tor/Tor | Version: Tor: 0.2.6.2-alpha Severity: Normal | Resolution: Keywords: tor-dir-auth | Actual Points: Parent ID: | Points: 0.5 Reviewer: | Sponsor: --------------------------+------------------------------------
Comment (by teor): Replying to [comment:5 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.) -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23592#comment:6> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs