Hi,
After a power cut a couple of weeks ago, my tor relay is not longer part of the consensus: B33BFA9AA0005730C1C0E8F7E6F53CF3C5716BD6
Current tor process has been running since 2018-03-14. How much time is it needed to come back?
Cheers,
S
On 3/23/18 12:31, victoring@riseup.net wrote:
Hi,
After a power cut a couple of weeks ago, my tor relay is not longer part of the consensus: B33BFA9AA0005730C1C0E8F7E6F53CF3C5716BD6
Current tor process has been running since 2018-03-14. How much time is it needed to come back?
Cheers,
S
Does your relay do both IPv4 and IPv6? Did your IPv4/6 address change?
Some of the authorities think you're running, but not enough. It could be because something changed about your address(es).
See here. Very large webpage. https://consensus-health.torproject.org/consensus-health-2018-03-23-15-00.ht...
Matt
El 23/03/18 a las 12:34, Matt Traudt escribió:
On 3/23/18 12:31, victoring@riseup.net wrote:
Hi,
After a power cut a couple of weeks ago, my tor relay is not longer part of the consensus: B33BFA9AA0005730C1C0E8F7E6F53CF3C5716BD6
Current tor process has been running since 2018-03-14. How much time is it needed to come back?
Cheers,
S
Does your relay do both IPv4 and IPv6? Did your IPv4/6 address change?
Thanks. I haven't realised there is a problem with its IPv6 address, even if it the prefix hasn't changed. I am disabling for the moment.
Some of the authorities think you're running, but not enough. It could be because something changed about your address(es).
See here. Very large webpage. https://consensus-health.torproject.org/consensus-health-2018-03-23-15-00.ht...
Where the differences come from? Why there are authorities that think it's running while others not?
On 3/23/18 12:55, victoring@riseup.net wrote:
El 23/03/18 a las 12:34, Matt Traudt escribió:
Does your relay do both IPv4 and IPv6? Did your IPv4/6 address change?
Thanks. I haven't realised there is a problem with its IPv6 address, even if it the prefix hasn't changed. I am disabling for the moment.
Some of the authorities think you're running, but not enough. It could be because something changed about your address(es).
See here. Very large webpage. https://consensus-health.torproject.org/consensus-health-2018-03-23-15-00.ht...
Where the differences come from? Why there are authorities that think it's running while others not?
Some (not all) of the authorities are capable of IPv6. The ones that are capable of IPv6 require that relays with both IPv4 and IPv6 ORPorts be reachable on both. If you have both and aren't reachable on both, you'll end up being marked as not running.
Hope that helps.
Matt
El 23/03/18 a las 13:06, Matt Traudt escribió:
On 3/23/18 12:55, victoring@riseup.net wrote:
El 23/03/18 a las 12:34, Matt Traudt escribió:
Does your relay do both IPv4 and IPv6? Did your IPv4/6 address change?
Thanks. I haven't realised there is a problem with its IPv6 address, even if it the prefix hasn't changed. I am disabling for the moment.
Some of the authorities think you're running, but not enough. It could be because something changed about your address(es).
See here. Very large webpage. https://consensus-health.torproject.org/consensus-health-2018-03-23-15-00.ht...
Where the differences come from? Why there are authorities that think it's running while others not?
Some (not all) of the authorities are capable of IPv6. The ones that are capable of IPv6 require that relays with both IPv4 and IPv6 ORPorts be reachable on both. If you have both and aren't reachable on both, you'll end up being marked as not running.
Hope that helps.
Yes, thanks.
JFTR, it seems that AS3215 (Orange, FR) support IPv6 only in some of its networks. I had to reconnect more than once until I got a routing IPv6 network.
Cheers,
S
tor-relays@lists.torproject.org
-
Matt Traudt -
victoring＠riseup.net