<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Hi,<br><div><br>On 17 Jan 2018, at 08:31, Toralf Förster <<a href="mailto:toralf.foerster@gmx.de">toralf.foerster@gmx.de</a>> wrote:<br><br></div><blockquote type="cite"><div><span>I do wonder why</span><br><span> $> scripts/maint/updateFallbackDirs.py check_existing</span><br><span>tells</span><br><span> $> WARNING::1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA not a candidate: changed address/port recently (2017-10-22 07:00:00)</span><br><span></span><br><span>But 1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA didn't changed it address/port since end of 2016.</span><br></div></blockquote><div><br></div><div>We use Onionoo data this check, and it gives that date for last_changed_address_or_port:</div><div><br></div><div><a href="https://onionoo.torproject.org/details?limit=1&search=1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA">https://onionoo.torproject.org/details?limit=1&search=1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA</a></div><div><br></div><div>Onionoo says a relays has changed its address or port if:</div><div>* it changes the published <span style="background-color: rgba(255, 255, 255, 0);">address or port of an </span>IPv4 or IPv6 ORPort, or IPv4 DirPort, or</div><div>* it stops publishing an IPv6 ORPort or IPv4 DirPort,</div><div>for one or more consensuses, even if it changes back.</div><div><br></div><div>Onionoo does not say that an address has changed if you add an IPv6 ORPort</div><div>to a relay that doesn't have an IPv6 ORPort.</div><br><blockquote type="cite"><div><span>What I did is to establish a 2nd Tor relay at the same hardware at 2 different ports in automn last year: D11D11877769B9E617537B4B46BFB92B443DE33D (to verify if the combined bandwidth/weight of both would be equal to the one of the former single relay at the same IP). And I played a little bit with its configuration values.</span><br></div></blockquote><div><br></div><div>You probably changed a port value on your existing relay while doing this.</div><div>If you keep the addresses and ports the same until we next rebuild the list,</div><div>your relay should be a candidate.</div><div><br></div><div>(We require at least 90 days on the same address, because we lose most</div><div>fallbacks that way.)</div><br><blockquote type="cite"><div><span>What comes in addition into my mind is that at every reboot I do run first "certbot" to check for a renewed LetsEncrypt certificate. And shortly (1 or 2 minutes) after it finished both Tor instances are started.</span><br></div></blockquote><br><div>Startup delays in Tor do not change the address in Onionoo.</div><div><br></div><div>T</div></body></html>