<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><div>On 21 Dec 2017, at 16:33, Conrad Rockenhaus <<a href="mailto:conrad@rockenhaus.com">conrad@rockenhaus.com</a>> wrote:<br><br></div><blockquote type="cite"><div><span>Hello,</span><br><span></span><br><span>One of the relays that I brought online yesterday, ConradsAWSExit (Hash 1B47E33F9D422CC97BD2DDA1F082BFF2FC58E79A) is showing up on Atlas that the IPv6 OR is unreachable.</span><br><span></span><br><span>The other relay is working just fine with IPv6.</span><br><span></span><br><span>I’ve confirmed that the following entries are in torrc:</span><br><span></span><br><span>ORPort 9001</span><br><span>ORPort [2600:1f14:ede:d601:e107:1a4b:ba3:803]:9001</span><br><span>IPv6Exit 1</span><br></div></blockquote><div><br></div><div>Are these the only ORPort entries in your torrc?</div><div>Have you restarted or HUP'd the relay since you last edited the torrc?</div><br><blockquote type="cite"><div><span>Just to confirm, here’s the output from ifconfig, that is the IP:</span><br><span></span><br><span>inet6 2600:1f14:ede:d601:e107:1a4b:ba3:803 prefixlen 64 scopeid 0x0<global></span><br></div></blockquote><div><br></div><div>This is what Relay Search (Atlas) says:</div><div><br></div><div><dt style="box-sizing: border-box; line-height: 1.42857143; font-weight: 700;"><span class="tip" title="" data-original-title="Addresses and ports where the relay claims to listen for incoming connections from clients and other relays but that the directory authorities failed to confirm as reachable." style="box-sizing: border-box; background-color: rgba(255, 255, 255, 0);">Unreachable OR Addresses</span></dt><dd style="box-sizing: border-box; line-height: 1.42857143; margin-left: 0px; word-break: break-word; -webkit-hyphens: auto;"><pre class="pre-scrollable" style="box-sizing: border-box; overflow-x: auto; overflow-y: scroll; padding: 9.5px; margin-top: 0px; margin-bottom: 10px; line-height: 1.42857143; word-break: break-all; word-wrap: break-word; border: 1px solid rgb(204, 204, 204); border-top-left-radius: 4px; border-top-right-radius: 4px; border-bottom-right-radius: 4px; border-bottom-left-radius: 4px; max-height: 340px;"><font face="UICTFontTextStyleTallBody"><span style="white-space: normal; background-color: rgba(255, 255, 255, 0);">[2600:1f14:ede:d601:72c2:a87d:960d:c334]:9001</span></font></pre></dd></div><div><br></div><div>The last 8 bytes of the address your relay is advertising,</div><div>are not the same as the address on your machine.</div><div><br></div><div>Also, you have set IPv6Exit, but Relay Search says:</div><div><br></div><div><dt style="box-sizing: border-box; line-height: 1.42857143; font-weight: 700;"><span class="tip" title="" data-original-title="Port summary of IPv6 exit connections that the relay is going to accept or reject." style="box-sizing: border-box; background-color: rgba(255, 255, 255, 0);">IPv6 Exit Policy Summary</span></dt><dd style="box-sizing: border-box; line-height: 1.42857143; margin-left: 0px; word-break: break-word; -webkit-hyphens: auto;"><pre class="pre-scrollable" style="box-sizing: border-box; overflow-x: auto; overflow-y: scroll; padding: 9.5px; margin-top: 0px; margin-bottom: 10px; line-height: 1.42857143; word-break: break-all; word-wrap: break-word; border: 1px solid rgb(204, 204, 204); border-top-left-radius: 4px; border-top-right-radius: 4px; border-bottom-right-radius: 4px; border-bottom-left-radius: 4px; max-height: 340px;"><font face="UICTFontTextStyleTallBody"><span style="white-space: normal; background-color: rgba(255, 255, 255, 0);">reject<br style="box-sizing: border-box;"> 1-65535</span></font></pre><div><br></div><div>Relay Search data is usually up to 2.5 hours behind, but it can lag more.</div><div><br></div><div>Please copy and paste the notice-level Tor logs that mention your ORPort,</div><div>DirPort, and Exit settings, so we can see what Tor is actually doing.</div></dd></div><br><blockquote type="cite"><div><span>I have confirmed that all of the applicable Security Group rules are configured correctly:</span><br><span></span><br><span>Custom TCP Rule</span><br><span>TCP</span><br><span>9001</span><br><span>0.0.0.0/0</span><br><span>ORPort</span><br><span>Custom TCP Rule</span><br><span>TCP</span><br><span>9001</span><br><span>::/0</span><br><span>ORPort</span><br><span>Custom TCP Rule</span><br><span>TCP</span><br><span>9030</span><br><span>0.0.0.0/0</span><br><span>DIRPort</span><br><span>Custom TCP Rule</span><br><span>TCP</span><br><span>9030</span><br><span>::/0</span><br><span>DIRPort</span></div></blockquote><div><br></div><div>By the way, there are no IPv6 DirPorts :-)</div><br><blockquote type="cite"><div><span>Plus, I have confirmed with a telnet -6 to port 9001 from both my house and my servers at OVH in Canada that I’m able to connect to port 9001 via the IPv6 address on this node.</span><br></div></blockquote><div><br></div>What are the exact commands you used?<br><div><br></div><div>This shows that the relay is listening on whatever IPv6 address and port</div><div>you checked, but it doesn't show which IPv6 address the relay is</div><div>advertising.</div><br><blockquote type="cite"><div><span>So, my question is…what could I be missing here that is causing atlas to say that IPv6 is unreachable? I’ve been looking into this through the day and would like to kind of close it out, got a bunch of emails to catch up on hehe :D, so any input would be appreciated.</span><br></div></blockquote><div><br></div><div>There are a few more detailed troubleshooting things we can try,</div><div>like checking consensus health and the exact content of your</div><div>relay's descriptor and the authorities' votes.</div><div><br></div><div>If the above steps don't help, I'm happy to go through them later,</div><div>when I'm using a more capable device.</div><br><div>T</div></body></html>