[tor-relays] IPv6 auto-discovery vs. privacy extensions

[Casper]

Onion Operator a écrit :
>    Saluton,
>    My relay started to log this message since 0.4.5.5:
>    Auto-discovered IPv6 address [...]:443 has not been found reachable.
>    However, IPv4 address is reachable. Publishing server descriptor without
>    IPv6 address. [2 similar message(s) suppressed in last 2400 seconds]
>    I think it started with the introduction of IPv6 auto-discovery.
>    The problem, as I understand it, is that my relay has IPv6 privacy
>    extensions enabled and therefore the IPv6 detection logic gets
>    fooled. Indeed the IPv6 I see in the logs is one of the temporary
>    addresses used as client towards other relays.
>    Relevant config is:
>    ORPort 443 IPv4Only
>    ORPort [...]:443 IPv6Only
>    I added the IPv{4,6}Only options only in searching a solution to this
>    problem, before 0.4.5.5 the IPv6 relay worked perfectly without.
>    In reading the documentation of AddressDisableIPv6 I got the
>    impression that if (any?) ORPort is configured with IPv4Only the
>    IPv6 auto-discovery gets disabled but evidence does not support my
>    understanding. Is it a bug?
>    Any other way to disable IPv6 auto-discovery?
Hi,

in my config:

ORPort 26709
ORPort [<ipv6_address_here>]:26709
DirPort 26710

No IPv6 auto-discovery in my logs, and ipv6 flag putted on my relays

I got this config from the torproject documentation.

hope this help :)
-- 
GnuPG: AE157E0B29F0BEF2 at keys.openpgp.org
CA Cert: https://dl.casperlefantom.net/pub/ssl/root.der
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20210224/deb2f3e3/attachment.sig>