[tor-relays] Relay is missing Running flag in the consensus

demfloro demfloro at demfloro.ru
Wed Dec 28 10:26:08 UTC 2016


Hello again,

Bwauths started voting again for my exit relay[1], looks like the problem disappeared. Though longclaw is still inaccessible from relay[1]:
10:16:14-root at bsd1 ~ # traceroute 199.254.238.53
traceroute to 199.254.238.53 (199.254.238.53), 64 hops max, 40 byte packets
 1  192.168.240.102 (192.168.240.102)  0.086 ms  0.075 ms  0.129 ms
 2  192.168.240.5 (192.168.240.5)  0.123 ms  0.136 ms  0.105 ms
 3  85.143.208.1 (85.143.208.1)  5.350 ms  7.816 ms  19.672 ms
 4  185-47-53-25.customer.comfortel.pro (185.47.53.25)  0.673 ms  1.111 ms  2.669 ms
 5  81-27-254-184.rascom.as20764.net (81.27.254.184)  1.638 ms  1.129 ms  1.484 ms
 6  80-64-96-225.rascom.as20764.net (80.64.96.225)  11.876 ms  12.420 ms  11.693 ms
 7  xe-9-2-0.bar1.Stockholm1.Level3.net (213.242.110.113)  11.507 ms  11.666 ms
    lag-127-401.ear1.Stockholm2.Level3.net (213.242.110.41)  12.122 ms
 8  * * *
 9  63-235-41-149.dia.static.qwest.net (63.235.41.149)  110.429 ms  109.880 ms  109.923 ms
10  * * *
11  65.116.154.6 (65.116.154.6)  183.700 ms  182.898 ms  185.499 ms
12  208.99.210.41 (208.99.210.41)  182.097 ms  182.302 ms  184.688 ms
13  208.99.192.65 (208.99.192.65)  182.331 ms  184.661 ms  184.562 ms
14  204.8.32.86 (204.8.32.86)  186.152 ms  190.550 ms  191.381 ms
15  wren.riseup.net (198.252.153.1)  182.196 ms  184.517 ms  184.863 ms
16  * * *
17  * * *
18  * * *

It is accessible from neighbour relay[2] in the same datacenter:
10:16:42-thirdexit ~ # traceroute 199.254.238.53
traceroute to 199.254.238.53 (199.254.238.53), 30 hops max, 60 byte packets
 1  192.168.240.138 (192.168.240.138)  3.014 ms  3.002 ms  3.001 ms
 2  192.168.240.5 (192.168.240.5)  3.012 ms  3.024 ms  3.034 ms
 3  85.143.208.1 (85.143.208.1)  3.089 ms  8.311 ms  12.929 ms
 4  185-47-53-25.customer.comfortel.pro (185.47.53.25)  3.024 ms  3.019 ms  3.019 ms
 5  81-27-254-184.rascom.as20764.net (81.27.254.184)  3.036 ms  3.047 ms  3.060 ms
 6  80-64-96-225.rascom.as20764.net (80.64.96.225)  12.107 ms  11.761 ms  11.879 ms
 7  lag-127-401.ear1.Stockholm2.Level3.net (213.242.110.41)  12.574 ms xe-9-2-0.bar1.Stockholm1.Level3.net (213.242.110.113)  49.256 ms  11.338 ms
 8  * * *
 9  63-235-41-149.dia.static.qwest.net (63.235.41.149)  109.894 ms  109.909 ms  110.102 ms
10  * * *
11  65.116.154.6 (65.116.154.6)  181.851 ms  181.868 ms  182.970 ms
12  208.99.210.41 (208.99.210.41)  182.146 ms  182.042 ms  182.625 ms
13  208.99.192.65 (208.99.192.65)  183.820 ms  183.781 ms  183.789 ms
14  204.8.32.86 (204.8.32.86)  186.095 ms  183.775 ms  183.773 ms
15  wren.riseup.net (198.252.153.1)  186.080 ms  186.032 ms  186.016 ms
16  longclaw.riseup.net (199.254.238.53)  183.757 ms  183.678 ms  185.967 ms

I'll try to contact riseup.net outside of the list about this issue.

[1] 1836695E7DFE2F80B13A9884431759B5DD19F1DA
[2] 2C2CD992B785F09752278260DCD8D6D6242BB87A



More information about the tor-relays mailing list