V2 Directory Flag Requirements

TorSuperNodes · August 7, 2025, 2:21am

So, what is the ACTUAL code needed in the torrc file to enable this flag?

I read on the official Tor Relay setup that is was this:

DirPort 9030

Which I did, and made sure 9030 was open on the firewall, and that does NOT seem to work. What else is needed? I also read somewhere that v2 Directory was no longer relevant in the newest version.

What version is correct?

My Current torrc:

ORPort 443
ORPort [*******************]:9050 ## IPv6
Address **********
ExitRelay 0
ExitPolicy reject “:”
Nickname TorSuperNodes
ContactInfo *****************
SocksPort 0
SocksPolicy reject *
DirPort 9030
AccountingStart month 1 00:00
AccountingMax 2000 GBytes

TorSuperNodes · August 7, 2025, 3:26am

I may suspect that if there are any Accounting or other bandwidth restrictions, the flag will be revoked. Is this correct?

atari · August 7, 2025, 3:43am

github.com/torproject/torspec

dir-spec.txt

main


      
          "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,
              - It qualifies for the V2Dir flag as described below (this
                constraint was added in 0.3.3.x, because in 0.3.0.x clients
                started avoiding guards that didn't also have the V2Dir flag).
          
               To calculate weighted fractional uptime, compute the fraction
               of time that the router is up in any given day, weighting so that
               downtime and uptime in the past counts less.
          
               A node is 'familiar' if 1/8 of all active nodes have appeared more
               recently than it, OR it has been around for a few weeks.

Guess you need a guard flag first. DirPort is not needed anymore.

TorSuperNodes · August 7, 2025, 6:52am

I can understand that. Interesting reading. All of my nodes DID have the v2 flag when they started a few days ago, and they are all on more than fast VMs in Akamai data centers.

Not that I really care anyway. I put them up, donate the time and donate the 37TB of monthly bandwidth, and however the network decides to use or allocate is up to them I guess. I just want to make sure that I am doing all I can for my part (I’m not ready to enable them as exit nodes right now though).

GeKo · August 19, 2025, 8:17am

TorSuperNodes via Tor Project Forum:

I can understand that. Interesting reading. All of my nodes DID have the v2 flag when they started a few days ago, and they are all on more than fast VMs in Akamai data centers.

Not that I really care anyway. I put them up, donate the time and donate the 37TB of monthly bandwidth, and however the network decides to use or allocate is up to them I guess. I just want to make sure that I am doing all I can for my part (I’m not ready to enable them as exit nodes right now though).

It looks good now, doesn’t it? Unless you disable the DirCache you
should get the V2Dir flag. There is no DirPort statement needed in your
torrc file anymore. Current Tor versions don’t use it anymore in a relay
context.

TorSuperNodes · August 19, 2025, 10:22am

Yeah, they all look good now: