<div dir="ltr"><div>hi Gerard,</div><div><br></div><div>you can find the instructions via the link provided in the original email: <br></div><div><div><br>
[2] <a href="https://2019.www.torproject.org/docs/debian.html.en" rel="noreferrer" target="_blank">https://2019.www.torproject.org/docs/debian.html.en</a><font color="#888888"><br></font>
</div></div><div><br></div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">gr. Paul<br></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jul 23, 2020 at 11:48 PM Dr Gerard Bulger <<a href="mailto:gerard@bulger.co.uk">gerard@bulger.co.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Where do we get daily builds?<br>
<br>
-----Original Message-----<br>
From: tor-relays <<a href="mailto:tor-relays-bounces@lists.torproject.org" target="_blank">tor-relays-bounces@lists.torproject.org</a>> On Behalf Of<br>
David Goulet<br>
Sent: 22 July 2020 20:55<br>
To: <a href="mailto:tor-relays@lists.torproject.org" target="_blank">tor-relays@lists.torproject.org</a><br>
Subject: [tor-relays] Call for Testing - New Feature: Relay IPv6 Address<br>
Discovery<br>
<br>
Greetings everyone!<br>
<br>
We've very recently merged upstream (tor.git) full IPv6 supports which<br>
implies many many things. We are still finalizing the work but most of it is<br>
in at the moment.<br>
<br>
This is a call for help if anyone would like to test either git master[1] or<br>
nightly builds[2] (only Debian) to test for us a specific feature.<br>
<br>
The feature we would love for some of you to test is the IPv6 address<br>
discovery. In short, with this new feature, specifying an ORPort without an<br>
address will automatically bind tor to [::]:<port> and attempt to find the<br>
IPv6 address by looking at (in this order):<br>
<br>
1. "Address" from torrc<br>
2. "ORPort address:port" from torrc<br>
3. Interface address. First public IPv6 is used.<br>
4. Local hostname, DNS AAAA query.<br>
<br>
If all fails, the relay will simply never publish an IPv6 in the descriptor<br>
but it will work properly with the IPv4 (still mandatory).<br>
<br>
The other new thing is that now tor supports *two* "Address" statement which<br>
can be a hostname or IPv4 or IPv6 now.<br>
<br>
Thus this is now valid:<br>
<br>
Address 1.2.3.4<br>
Address [4242::4242]<br>
ORPort 9001<br>
<br>
Your Tor will bind to <a href="http://0.0.0.0:9001" rel="noreferrer" target="_blank">0.0.0.0:9001</a> and [::]:9001 but will publish the<br>
1.2.3.4 for the IPv4 address and [4242::4242] for IPv6 in the descriptor<br>
that is the address to use to reach your relay's ORPort.<br>
<br>
Now, if you happen to have this configuration which I believe might be<br>
common at the moment:<br>
<br>
ORPort 9001<br>
ORPort [4242::4242]:9001<br>
<br>
The second ORPort which specifies an IPv6 address will supersede the "ORPort<br>
9001" which uses [::] and thus you will bind on <a href="http://0.0.0.0:9001" rel="noreferrer" target="_blank">0.0.0.0:9001</a> and<br>
[4242::4242]:9001. You should get a notice log about this.<br>
<br>
Thus the recommended configuration to avoid that log notice would be to bind<br>
to specific addresses per family:<br>
<br>
ORPort <IPv4>:9001<br>
ORPort <IPv6>:9001<br>
<br>
And of course, if you want your relay to _not_ listen on IPv6:<br>
<br>
ORPort 9001 IPv4Only<br>
<br>
In your notice log, you will see which address is used to bind on the ORPort<br>
and then you will see the reachability test succeed or not on the address<br>
that tor either used from the configuration or auto discovered that is the<br>
address you are supposedly reachable from.<br>
<br>
Man page has NOT been updated yet, it will arrive once we stabilize the IPv6<br>
feature and everything around it.<br>
<br>
Please, do report (on this thread) _anything_ even slightly annoying about<br>
this like logging or lack of logging and so on. This is a complex feature<br>
and errors can be made thus any testing you can offer is extremely<br>
appreciated.<br>
<br>
Thanks!!<br>
David<br>
<br>
[1] <a href="https://gitweb.torproject.org/tor.git/" rel="noreferrer" target="_blank">https://gitweb.torproject.org/tor.git/</a><br>
[2] <a href="https://2019.www.torproject.org/docs/debian.html.en" rel="noreferrer" target="_blank">https://2019.www.torproject.org/docs/debian.html.en</a><br>
<br>
--<br>
EeJVrrC/dHQXEXYB1ShOOZ4QuQ8PMnRY2XGq4BYsFq4=<br>
<br>
_______________________________________________<br>
tor-relays mailing list<br>
<a href="mailto:tor-relays@lists.torproject.org" target="_blank">tor-relays@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
</blockquote></div>