[tor-dev] path selection constraints: /16 subnet rule when using bridges

teor teor2345 at gmail.com
Wed Dec 20 01:45:50 UTC 2017

> On 20 Dec 2017, at 10:00, nusenu <nusenu-lists at riseup.net> wrote:
>>> does the following also apply if a Tor users chooses to use a bridge?
>>>>    - We do not choose more than one router in a given /16 subnet
>>> [1]
>>> Will tor ensure that the relays are not in the same /16 netblock with the bridge?
>> Yes, as each node is added to the path, its IPv4 address is checked
>> against the IPv4 /16 netblocks of the existing nodes in the path.
>> This includes relays and bridges.
>> There is no support for checking IPv6 addresses yet:
>> https://trac.torproject.org/projects/tor/ticket/24393
>> But when there is, we will check IPv6 /32s, for those nodes that have IPv6
>> addresses.
> Does it check only against actively used ORPort IPv4 address or all ORPort IPs
> in the bridge descriptor when connecting to the bridge via IPv6?
> example:
> - bridge has an IPv6 and IPv4
> - exit has
> - tor client connects to the bridge using IPv6
> Will the client use that exit if it connects to the bridge via IPv6?

It only checks IPv4 addresses for the moment, regardless of how it


Tim / teor

PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20171220/aff4407a/attachment.sig>

More information about the tor-dev mailing list