Feb 18, 2023 12:31:31 trinity pointard 'trinity.pointard at gmail.com'
:
> Hi,
>
> You shouldn't worry too much about your relay sometime appearing as
> overloaded. Sadly due to the ongoing network ddos, many relays show up
> that way. You shouldn't restart your relay daily, that would make
>
shruub via tor-relays wrote:
I also (stupidly) tried to have a cron restarting
my tor daemon daily which also resulted in the latter. So I wonder, if
there is any way to have a relay run more stable and I suppose with a
somewhat higher consensus weight (I can only asssume making some further
Hi,
You shouldn't worry too much about your relay sometime appearing as
overloaded. Sadly due to the ongoing network ddos, many relays show up
that way. You shouldn't restart your relay daily, that would make everybody
think it's not very stable, so you won't be able to get flags such as Stable,
On Donnerstag, 16. Februar 2023 06:15:02 CET Keifer Bly wrote:
> So my bridge at
> https://metrics.torproject.org/rs.html#details/4D6E3CA2110FC36D3106C86940A1D
> 4C8C91923AB says it has “none “,
Well, then you have configured BridgeDistribution (Default: any) to none.
> though the torrc file has
Hello,
so my relay regulary gets overloaded, for what I can only assume is an
hardware issue, (which I can't upgrade rn) since I already applied the
tor anti ddos scripts. It seems to be able to recover, however with a
lower Consensus Weight. I also (stupidly) tried to have a cron restarting
my
Hi,
the tor 0.4.5.x end of live versions are still on the recommended versions list:
https://consensus-health.torproject.org/#recommendedversions
consensus client-versions 0.4.5.6, 0.4.5.7, 0.4.5.8, 0.4.5.9, 0.4.5.10,
0.4.5.11, 0.4.5.12, 0.4.5.14, 0.4.5.15, 0.4.5.16, 0.4.7.7, 0.4.7.8,
> makes you lose
flags, and it also might be the reason your consensus weight was lowered.
I'm not sure if I actually lost flags, but yes, that is probably the main
reason.
> RelayBandwidthBurst
One question, what actually is the burst? Haven't found anything online
nor in man.
> There's not
Ok. Here is the torrc file:
GNU nano 3.2 /etc/tor/torrc
Nickname gbridge
ORPort 443
SocksPort 0
BridgeRelay 1
PublishServerDescriptor bridge
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ServerTransportListenAddr obfs4 0.0.0.0:8080
ExtOrPort auto
Log
