-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Currently I do have for an exit relay defined:
DirPort 80 DirPort [2a01:4f8:190:514a::2]:80 NoAdvertise
What would happen if I would NoAdvertise the ipv4 port instead of the ipv6 port ? - -- Toralf PGP: C4EACDDE 0076E94E, OTR: 420E74C8 30246EE7
See: https://lists.torproject.org/pipermail/tor-talk/2016-January/040074.html
My takeaway is that there's little point to setting an IPv6 DirPort at this point. Clients will rarely connect to it, and relays won't connect to it at all. Furthermore, "In 0.2.8, clients assume that the IPv6 DirPort is the same as the IPv4 DirPort" already. If that's still true, might as well leave the v4 port advertised, and if a v6 client comes along it will try the (non-advertised) v6 port anyway.
It seems like all of this is in flux though. Perhaps someone can provide an update on the current progress.
On 5 Jul 2016, at 07:30, Green Dream greendream848@gmail.com wrote:
See: https://lists.torproject.org/pipermail/tor-talk/2016-January/040074.html
My takeaway is that there's little point to setting an IPv6 DirPort at this point. Clients will rarely connect to it, and relays won't connect to it at all. Furthermore, "In 0.2.8, clients assume that the IPv6 DirPort is the same as the IPv4 DirPort" already. If that's still true, might as well leave the v4 port advertised, and if a v6 client comes along it will try the (non-advertised) v6 port anyway.
It seems like all of this is in flux though. Perhaps someone can provide an update on the current progress.
In 0.2.8.3-aplha, "clients, onion services, and bridge relays always use an encrypted begindir connection for directory requests". Encrypted beginner connections are made over the ORPort. This means that in 0.2.8 clients no longer use any DirPort, and relays only use the IPv4 DirPort. IPv6 clients and bridge clients use the IPv6 ORPort.
In 0.2.7 and before, clients and relays only use the IPv4 DirPort. IPv6 bridge clients use the IPv6 ORPort.
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP 968F094B ricochet:ekmygaiu4rzgsk6n
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 07/05/2016 04:01 AM, Tim Wilson-Brown - teor wrote:
In 0.2.8.3-aplha, "clients, onion services, and bridge relays always use an encrypted begindir connection for directory requests". Encrypted beginner connections are made over the ORPort. This means that in 0.2.8 clients no longer use any DirPort, and relays only use the IPv4 DirPort. IPv6 clients and bridge clients use the IPv6 ORPort.
In 0.2.7 and before, clients and relays only use the IPv4 DirPort. IPv6 bridge clients use the IPv6 ORPort.
Understood - so in the long run a DirPort is only used to serve the DirPortFrontPage
- -- Toralf PGP: C4EACDDE 0076E94E, OTR: 420E74C8 30246EE7
On 5 Jul 2016, at 19:23, Toralf Förster toralf.foerster@gmx.de wrote:
Signed PGP part On 07/05/2016 04:01 AM, Tim Wilson-Brown - teor wrote:
In 0.2.8.3-aplha, "clients, onion services, and bridge relays always use an encrypted begindir connection for directory requests". Encrypted beginner connections are made over the ORPort. This means that in 0.2.8 clients no longer use any DirPort, and relays only use the IPv4 DirPort. IPv6 clients and bridge clients use the IPv6 ORPort.
In 0.2.7 and before, clients and relays only use the IPv4 DirPort. IPv6 bridge clients use the IPv6 ORPort.
Understood - so in the long run a DirPort is only used to serve the DirPortFrontPage
The IPv4 DirPort is used by relays and authorities. This isn't going to change any time soon.
-- Toralf PGP: C4EACDDE 0076E94E, OTR: 420E74C8 30246EE7
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP 968F094B ricochet:ekmygaiu4rzgsk6n
tor-relays@lists.torproject.org