[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-relays] Exit relay not in consensus



Hi,

> On 2. Oct 2024, at 09:05, George Hartley via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx> wrote:
> 
> 
> It could be that your provider has throttled you temporarily.
> 
> I don't think so, I get that message on a dedicated 10 GbE link with little to no use except for the exit relay on it.
> 
> Also, if his relay publishes it's descriptor, then why Metrics won't reflect that?
> 
> It should show it as online, as you don't need IPv6 to be reachable to get the online flag.


it looks like your upstream is maliciously messing with your traffic. I
am noticing a distinct difference between two traces, one directly from
my diraut's IPv4, another from a different host on the same network:

dirauth:
 1  informatik.gate.uni-erlangen.de (131.188.40.1)  0.522 ms  0.510 ms  0.506 ms
 2  constellation.gate.uni-erlangen.de (131.188.20.37)  0.485 ms  30.734 ms  30.714 ms
 3  yamato.gate.uni-erlangen.de (131.188.20.252)  0.530 ms  0.618 ms  0.740 ms
 4  cr-erl2-hundredgige0-7-0-5.x-win.dfn.de (188.1.234.229)  0.831 ms  0.881 ms  0.962 ms
 5  cr-fra2-be11.x-win.dfn.de (188.1.144.222)  4.694 ms  4.784 ms  4.814 ms
 6  ae56.edge9.Frankfurt1.Level3.net (62.67.67.153)  23.379 ms  14.507 ms  14.478 ms
 7  * * *
 8  if-ae-68.tcore2.fr0-frankfurt.as6453.net (80.231.65.22)  15.707 ms  15.677 ms  15.651 ms
 9  * * *
10  * * *
11  * * *
12  if-bundle-15-2.qcore1.emrs2-marseille.as6453.net (80.231.154.33)  25.474 ms *  25.201 ms
13  * * *
14  * * *
15  * * *

other host:
 1  informatik.gate.uni-erlangen.de (131.188.40.1)  0.705 ms  0.676 ms  0.626 ms
 2  constellation.gate.uni-erlangen.de (131.188.20.37)  0.571 ms  0.538 ms  0.508 ms
 3  yamato.gate.uni-erlangen.de (131.188.20.252)  1239.238 ms  1239.152 ms  1239.124 ms
 4  cr-erl2-hundredgige0-7-0-5.x-win.dfn.de (188.1.234.229)  1239.135 ms  1239.115 ms  1239.075 ms
 5  cr-fra2-be11.x-win.dfn.de (188.1.144.222)  4.337 ms  4.395 ms  4.497 ms
 6  ae56.edge9.Frankfurt1.Level3.net (62.67.67.153)  4.123 ms  8.507 ms  8.461 ms
 7  * * *
 8  * ix-bundle-68.qcore1.fr0-frankfurt.as6453.net (80.231.65.22)  14.755 ms *
 9  * * *
10  * * *
11  * * *
12  if-bundle-15-2.qcore1.emrs2-marseille.as6453.net (80.231.154.33)  25.063 ms  25.363 ms *
13  14.142.189.178.static-mumbai.vsnl.net.in (14.142.189.178)  141.605 ms  138.409 ms  138.429 ms
14  142.79.255.2 (142.79.255.2)  139.856 ms 142.79.255.0 (142.79.255.0)  138.112 ms 142.79.255.2 (142.79.255.2)  134.489 ms
15  142.79.252.34 (142.79.252.34)  240.947 ms  242.328 ms  245.329 ms
16  sortie-tor.a-n-o-n-y-m-e.net (156.67.111.146)  249.023 ms  243.328 ms  247.636 ms

While this traffic interference lasts, you will not be able to reliably
upload descriptors, get measured as reachable, etc. That might also
explain why your descriptors do not make it to metrics, as your upstream
is preventing you from ever getting them out there.

I hope you will be able to talk some sense into your upstream!

Cheers and thanks
Sebastian

Attachment: signature.asc
Description: Message signed with OpenPGP

_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays