<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span></span></div><div><span></span><span>Hi,</span><br><span></span><br><blockquote type="cite"><span>On 12 Dec 2017, at 06:38, Andreas Piesk <<a href="mailto:a.piesk@mailbox.org">a.piesk@mailbox.org</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Hello list,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Relay Search shows wrong data of one of my relays. I'm not sure if the data is wrong or if relay search does the wrong thing or the directory server doesn't like te relay.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>The relay's fingerprint is 43AD3376735B4A227920AD06D2D9B6970B3C75DF and it is running 3.1.9 on Linux.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Relay Search reports:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Downtime</span><br></blockquote><blockquote type="cite"><span> 2 days 23 hours 20 minutes and 15 seconds</span><br></blockquote><blockquote type="cite"><span>Last Seen</span><br></blockquote><blockquote type="cite"><span> 2017-12-08 20:00:00Tor 0.3.1.9 on Linux</span><br></blockquote><blockquote type="cite"><span>Additional Flags</span><br></blockquote><blockquote type="cite"><span> Not Recommended IPv6 ORPort</span><br></blockquote><blockquote type="cite"><span>Last Restarted</span><br></blockquote><blockquote type="cite"><span> 2017-12-10 23:12:29</span><br></blockquote><blockquote type="cite"><span>Platform</span><br></blockquote><blockquote type="cite"><span> Tor 0.3.1.9 on Linux</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>It got the "Not Recommended" flag because of "This relay is running an outdated Tor version and should be updated to a recent release of Tor that may contain important fixes.".</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Something is not right:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>1. the relay IS running and i see V2, V3 and V4 connections.</span><br></blockquote><span></span><br><span>The relay is reachable over IPv4, but not IPv6.</span><br><span></span><br><span>The 5 directory authorities that check ReachableIPv6 have marked your relay</span><br><span>as not Running. That means the IPv6 address is wrong or unreachable.</span></div><div>(The 3 that only check IPv4 marked it as Running, but they're not a majority.</div><div>And 1 authority did not vote.)</div><div><br></div><div>Also, the bandwidth authorities are still voting for your relay.</div><div><br></div><div>This page lists all the votes for your relay:</div><div><a href="https://consensus-health.torproject.org/consensus-health-2017-12-11-17-00.html#43AD3376735B4A227920AD06D2D9B6970B3C75DF">https://consensus-health.torproject.org/consensus-health-2017-12-11-17-00.html#43AD3376735B4A227920AD06D2D9B6970B3C75DF</a><br><span></span><br><span>We're working on having better support for IPv6 across Relay Search and</span><br><span>consensus health.</span><br><span></span><br><blockquote type="cite"><span>2. if it was last seen 2017-12-08 20:00:00,</span><br></blockquote><span></span><br><span>It was last seen in the consensus.</span><br><span></span><br><blockquote type="cite"><span>where does the restart date 2017-12-10 23:12:29 come from?</span><br></blockquote><span></span><br><span>The restart date comes from the descriptor.</span><br><span></span><br><blockquote type="cite"><span>3. 3.1.9 is not outdated as Relay Search reports</span><br></blockquote><span></span><br><span></span>I'm not sure if you received nusenu's email:</div><div><br></div><div><span style="background-color: rgba(255, 255, 255, 0);"><blockquote type="cite">this has likely todo with this bug:<br><a href="https://trac.torproject.org/projects/tor/ticket/22488" dir="ltr" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="1">https://trac.torproject.org/projects/tor/ticket/22488</a></blockquote></span><br><blockquote type="cite"><span>How to fix it? Unfortunately there is no way to delete the relay and start from scratch,is it?</span></blockquote><blockquote type="cite"><span>I don't want generate a new key and leave this relay as a zombie in the database, i would like to keep thois relay.</span><br></blockquote><div><br></div><span style="background-color: rgba(255, 255, 255, 0);">Please check your relay's IPv6 address!</span><br><blockquote type="cite"><span></span></blockquote></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Here's what I do:</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">From the relay:</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">ping6 <a href="http://ipv6.google.com">ipv6.google.com</a></span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">From another IPv6 machine:</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">ping6 (the relay's IPv6 address)</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Or you can try using telnet to the ORPort.</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">T</span></div></body></html>