[tor-relays] Unexpected classification with my guard relay

Dear Mr./Mrs.,

As I really like the Deep Web field, and wanted to know about Tor, I decided to create a guard relay, which is this one:

https://metrics.torproject.org/rs.html#details/037F39EF786C0623A059553869C0D296A1C4CC9D

I did all the configurations required, but after a couple of weeks, this relay is not considered a guard relay (entry relay) yet.

I am contacting you because I don’t understand why my relay is not considered as a guard relay (entry relay), since I already have the following flags: Fast, HSDir, Running, Stable, V2Dir, Valid.

My configuration is:

Nickname securitses

ContactInfo securitses@gmail.com

ORPort 443

ExitRelay 0

ExitPolicy reject :

SocksPort 9050

AccountingStart day 0:00

AccountingMax 30 GBytes

BandwidthRate 301 KBytes

BandwidthBurst 350 KBytes

ControlPort 9051

HashedControlPassword <Hashed_password>

Thank you,

Yours sincerely,

Javier

I would assume it’s the bandwidth. Your bandwidth isn’t enough to operate as a guard. If you check other relays from the same Autonomous System as yours, there are machines with similar to your bandwidth but have been up for longer than 150+ days and they’re not guards.

···

Dear Mr./Mrs.,

As I really like the Deep Web field, and wanted to know about Tor, I decided to create a guard relay, which is this one:

https://metrics.torproject.org/rs.html#details/037F39EF786C0623A059553869C0D296A1C4CC9D

I did all the configurations required, but after a couple of weeks, this relay is not considered a guard relay (entry relay) yet.

I am contacting you because I don’t understand why my relay is not considered as a guard relay (entry relay), since I already have the following flags: Fast, HSDir, Running, Stable, V2Dir, Valid.

My configuration is:

Nickname securitses

ContactInfo securitses@gmail.com

ORPort 443

ExitRelay 0

ExitPolicy reject :

SocksPort 9050

AccountingStart day 0:00

AccountingMax 30 GBytes

BandwidthRate 301 KBytes

BandwidthBurst 350 KBytes

ControlPort 9051

HashedControlPassword <Hashed_password>

Thank you,

Yours sincerely,

Javier

I am contacting you because I don't understand why my relay is not considered as a guard relay (entry relay), since I already have the following flags: Fast, HSDir, Running, Stable, V2Dir, Valid.

The dir-spec.txt document (torspec/dir-spec.txt at main · torproject/torspec · GitHub) specifies what's needed for the different flags. For guard (line 2615) it says the following on bandwidth requirements:

- Its bandwidth is at least AuthDirGuardBWGuarantee (if set, 2 MB by
default), OR its bandwidth is among the 25% fastest relays

So looks you need to have at least 2MB/s. Your relay is at 290KB/s

···

_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

^^
Means: Relay hibernate every month.
These settings disqualify your relay as long time stable, fast & familiar.

https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2614

8<
"Guard" -- A router is a possible Guard if _all_ of the following apply:
- It is Fast, - It is Stable, - Its Weighted Fractional Uptime is at least the
median for "familiar" active routers, - It is "familiar", - Its bandwidth is
at least AuthDirGuardBWGuarantee (if set, 2 MB by default), OR its bandwidth
is among the 25% fastest relays,... >8

···

On Tuesday, February 22, 2022 3:45:14 PM CET Security GMVSES wrote:

AccountingStart day 0:00

AccountingMax 30 GBytes

BandwidthRate 301 KBytes

BandwidthBurst 350 KBytes

--
╰_╯ Ciao Marco!

Debian GNU/Linux

It's free software and it gives you freedom!