Re: [tor-relays] Flags gone after restart
andrew reid wrote: > Hey there, I am running a tor relay off an old samsung phone. When I first > started the relay, my observed bandwidth was around 4.5MB/s. It was running > for around 7 days and had the stable and HSdir flag. After a few problems > with IP6 and being overloaded (thought this was a problem on my end, not a > DDoS attack) I restarted the phone and edited the config file to take away > IPv6. It has now been running for 7 days again but my observed bandwidth is > only 1.6MB/s now and I still haven't gotten the stable and HSdir flag back. > How long would this take or is it just a problem on my end ? and for the > bandwidth, my connection is still the same and hasn't changed. Is this just > something that takes time to come back like the flags. This is my first > relay so I would like to understand a bit more. Thank you Stable, AFAIK, still depends upon something like the average uptime of the current instance and the previous instance relative to the corresponding averages among all other relays. Assignment of the Stable flag is made to relays above a certain percentile rank of those averages. Fast used to depend upon the maximum throughput speed allowed by the Bandwidth* and RelayBandwith* entries in the torrc file. More than some minimum bandwidth was required for assignment of the flag to a relay. HSDir used to depend upon its torrc option not being set to 0. That option was removed some time ago and is now apparently solely under the control of the Authority relays. *HOWEVER*, both a randomization factor appears to have been added three or four years ago to the Authority relays' algorithm used to decide whether to award Fast and to award HSDir. Now either flag comes and goes like birds landing on tree limbs and later departing, often for no reason obvious to humans. My relay has many times been up for one or more months. During those times Fast and HSDir have been repeatedly assigned to it and lifted from it and perhaps reassigned to it, often only a few hours apart. The only consistencies I have seen are that 1) the first time a tor relay is assigned the HSDir flag is after at least 96 hours of uptime in the current instance, though it may not happen until much later than 96 hours and 2) HSDir does not appear ever to be assigned unless Fast is also assigned. AFAIK, the tor project has never offered an explanation for the addition/intrusion of this randomization factor. Frankly, I think it is a destabilizing factor to the tor relay network and doubly so for hidden services activities, and it must add to overall tor traffic to have to restock the hidden service directory servers so often. Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * ** * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * *-- Gov. John Hancock, New York Journal, 28 January 1790 * ** ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Refuse Guard flag
On 8/2/22 20:58, Eldalië via tor-relays wrote: Recently I noticed that my ISP started to reset my IP a few hours after the node gets the Guard flag, The Guard flag is given after a more or less constant time (or?) - so I'd not see a conincidence here. -- Toralf ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] recommended way to run 0.4.7 on armhf?
ilf: Thanks. I thought about doing that, but I would rather not like to mix Raspian bullseye and Debian bullseye-backports. Is there a good reason against building armhf on deb.torproject.org? Just resource constraints. We have a ticket for that work[1] but de-prioritized it even further given that we have a good workaround and a lot of affected users are happy with it. Patches (still) welcome! :) Georg [1] https://gitlab.torproject.org/tpo/core/tor/-/issues/40347 Georg Koppen: Right. One thing we recommended when talking to relay operators during earlier EOL upgrade periods is adding the debian -backports repository to the Raspberry Pi. It worked well according to the feedback we got. We linked to https://marksrpicluster.blogspot.com/2019/12/add-buster-backports-to-raspberry-pi.html for general steps (you need to adapt them for bullseye, though). OpenPGP_signature Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Flags gone after restart
Hey there, I am running a tor relay off an old samsung phone. When I first started the relay, my observed bandwidth was around 4.5MB/s. It was running for around 7 days and had the stable and HSdir flag. After a few problems with IP6 and being overloaded (thought this was a problem on my end, not a DDoS attack) I restarted the phone and edited the config file to take away IPv6. It has now been running for 7 days again but my observed bandwidth is only 1.6MB/s now and I still haven't gotten the stable and HSdir flag back. How long would this take or is it just a problem on my end ? and for the bandwidth, my connection is still the same and hasn't changed. Is this just something that takes time to come back like the flags. This is my first relay so I would like to understand a bit more. Thank you ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] How useful are bridges on ports other than 80 and 443
Unfortunately I've had to shut down my home based tor relay because my wife's employer is mis-categorising it as an exit node, instead of the middle/guard that it really is. So, until she retires, in a few months, that relay will now be silent after about 5-years running (all of which her having the same employer. Go figure). So, I thought in the meantime I'd run a couple of tor bridges, as my IP should now be clear of any published tor node lists. But I do need to leave ports 80 and 443 open for "normal" HTTP(S) traffic, which I know are the recommended bridge ports as they raise the least suspicion. Are there any other ports that folks might suggest I use that would get enough traffic and not be blocked by a simple firewall. I also run an internal mail server, so all those ports are off limits as well. Cheers. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] recommended way to run 0.4.7 on armhf?
Thanks. I thought about doing that, but I would rather not like to mix Raspian bullseye and Debian bullseye-backports. Is there a good reason against building armhf on deb.torproject.org? Georg Koppen: Right. One thing we recommended when talking to relay operators during earlier EOL upgrade periods is adding the debian -backports repository to the Raspberry Pi. It worked well according to the feedback we got. We linked to https://marksrpicluster.blogspot.com/2019/12/add-buster-backports-to-raspberry-pi.html for general steps (you need to adapt them for bullseye, though). -- ilf If you upload your address book to "the cloud", I don't want to be in it. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Refuse Guard flag
Eldalië via tor-relays: Hello there. I have been running my (non-exit) relay without issues for some months. Recently I noticed that my ISP started to reset my IP a few hours after the node gets the Guard flag, thus making it lose such a flag (as well as Stable and HSDir). I am not sure if the Guard flag is the real cause, but it is the only condition that is verified always and only right before I get a new IP. Is there a way I can keep my node running with the same settings but preventing it from becoming a guard, to investigate if the flag is the real cause? Hrm, what about just asking the ISP why they are doing the reset instead (I don't think what you want is easily possible) Georg Thanks, Eldalië ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays OpenPGP_signature Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
