[tor-relays] Exit relay not in consensus

[denny.obreham at a-n-o-n-y-m-e.net]

   I tried changing the exit and OR ports, I tried setting
   CircuitBuildTimeout to 300, and my ISP keep assuring me they don't
   block any port, ever. Some DirAuth still cannot connect with me.

   I have about 20 exit relays spread across 11 ISPs, including 4 with
   this ISP (each in a different country). They are all built with the
   same setup. This particular Tor instance has been working fine for
   months now.

   I don't understand what more I can do. Everything is OK on my side,
   except for an "It seems like we are not in the cached consensus." line
   appearing in the log once in a while. It's the DirAuth that somehow
   cannot reach me, apparently blocked by some proxy server in the middle.

   What more can I do? Do I just abandon this server and IP address
   because it is somehow blacklisted by I don't know who?

   Denny

   On 2024-10-03 13:06, boldsuck via tor-relays wrote:

   On Wednesday, 2 October 2024 21:24 Sebastian Hahn wrote: On 2. Oct
   2024, at 09:05, George Hartley via tor-relays
   <tor-relays at lists.torproject.org> 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: A few years ago,
   Roger emailed me that he could not reach a service @ mit.edu (ASN3) via
   my exit. I had 2 exits at the same provider with same torrc, network
   config, IPtables, etc. One had "mystery null routes between Tor
   relays." https://gitlab.torproject.org/tpo/core/tor/-/issues/40357 I
   then switched to a different exit port and the problem was solved. --
   â°_⯠Ciao Marco! Debian GNU/Linux It's free software and it gives you
   freedom!

   _______________________________________________ tor-relays mailing list
   tor-relays at lists.torproject.org
   https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20241005/b6e93949/attachment.htm>