I can only speak with anonymity in mind, since this would mean you run a
"vpn" service (having a "quad-vpn", but actually one that makes sence in
that its not just 4 different servers of one company). Having an access
line would either mean you'd need to identify yourself (and of course it
Hello,
thanks for supporting the tor network! If I recall correctly, the lower
the better. E.g. if you start at 32768, which is the recommended port
range due to it not being used else where "officially", until 33018.
However, 6 - 60250 should also work well. You might also want to see
> 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
having it
> that low isn't an issue for the people handling that. Running means
> first time,
> little over a dozen relays have not been restarted in the last 6
> months. In
> general you should try to keep your relay be up to date, which
> necessarily
> imply a restart once in
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
Alright, good to know, thanks for your reply.
--
Best,
shruub
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hello,
so to also enable IPv6 on my relay I followed the post-install article
which said that one should ping all IPv6 authorities with the following
command: "ping6 -c2 2001:858:2:2:aabb:0:563b:1526 && ping6 -c2
2620:13:4000:6000::1000:118 && ping6 -c2 2001:67c:289c::9 && ping6 -c2
