The guard flag gets automatically assigned to you if you have enough bandwidth and uptime. You usually don't get to choose. You can still influence it by inducing downtime or limiting bandwidth (but both will be counterproductive). There are no risks in being a guard node, unlike being an exit. That's why web hosts are okay with guard nodes but not exits, and also why you can be a guard node on a broadband connection without getting complaints from your ISP. Abuse complaints don't go to a guard node, it goes to exits as exits connect directly to requested non-onion websites and guards don't.
-Neel Chauhan
===
On 2018-06-06 14:42, Keifer Bly wrote:
Hello, I have one question.
I have been running my relay “torland” at
http://torstatus.blutmagie.de/router_detail.php?FP=db1af6477bb276b6ea5e72132...
For roughly 3 months now (I am unsure exactly how many days). While my relay is marked “fast” and “stable” currently, it has never been marked as a “guard” relay. I believe being a “guard” relay requires at least 10mb/s for relay speed, but am wondering, do I need to configure my torrc file to allow it to be used as a guard relay and are there any risks for doing this (like there are in running in exit relay)? Thank you. _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays