Try to use mtr to that specific DirAuth, and see where you are being nullrouted.
Then contact that ASN (would be better if your provider did this in your name)
and ask why your origin is excluded / not routed-through.
They don't have to be "bad guys" or "Tor-unfriendly", it's most likely just a
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 differe
On Wednesday, 2 October 2024 21:24 Sebastian Hahn wrote:
> > On 2. Oct 2024, at 09:05, George Hartley via tor-relays
> > 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 n
Hi,
> On 2. Oct 2024, at 09:05, George Hartley via tor-relays
> 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 publ
> 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
On Tuesday, 1 October 2024 19:32 denny.obre...@a-n-o-n-y-m-e.net wrote:
>After my last restart I have:
>
>```
>
>Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
>
>Read configuration file "/etc/tor/torrc".
>
>Based on detected system memory, MaxMemInQue
Before my last restart 6 hours ago you get a series of messages like
these:
```
Since startup we initiated 0 and received 0 v1 connections; initiated 0
and received 0 v2 connections; initiated 0 and received 81 v3
connections; initiated 0 and received 341 v4 connections; initiat
My exit relay which has been running for months without a problem has
not been in the cached consensus for days now.
https://consensus-health.torproject.org/consensus-health.html?#7BDDE0E7
607A5F49578768F44CD721793FA2D7AE
After investigating, I thought the reason was that the IPv6 w
Hi, looks like the DirAuth's think that your relay is unreachable, and so your
descriptor isn't published, so your flags are not updated, this would explain
the lack of change in flags.
Port 443 on 156.67.111.146 is open for me, can't test IPv6 as I have disabled
it through my modem and kernel
