I installed a non-exit relay 5 days ago.
Works actually quit nicely.
I was awarded the stable flag.
(Also had briefly the HSDir flag, but lost it after a restart. Too early for the Guard flag.)
So I think everything looks good.
I have DirPort 9030 in my config.
It is shown in nyx and the tor process listens there.
But the relay search page says:
Dir Address none
It looks like this on my server:
tcp 0 0 0.0.0.0:9030 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN
tcp6 0 0 :::9001 :::* LISTEN
Why is it not shown and used by TOR?
And what is directory for anyways?
Why is it not listening und using IPv6 additionally to IPv4?
Did I need to configure something additionally to get it running?
Some TOR nodes show a port there.
Anything to consider for new relay operators?
I have limited the network traffic to 15 MB/s, so 240 MBit/s (bidirectional) so I should be well below my allowance.
Yep! This is fine and normal, but I agree it is a surprise.
I just opened a ticket in the relay-search component to help future
relay operators understand why it ends up as a 0:
Thanks for running a relay!
--Roger
···
On Sat, Jan 15, 2022 at 01:40:27PM +0100, Richard Menedetter wrote:
I installed a non-exit relay 5 days ago.
Works actually quit nicely.
I was awarded the stable flag.
(Also had briefly the HSDir flag, but lost it after a restart. Too early for the Guard flag.)
So I think everything looks good.
I have DirPort 9030 in my config.
It is shown in nyx and the tor process listens there.
But the relay search page says:
Dir Address none
> I have DirPort 9030 in my config.
> It is shown in nyx and the tor process listens there.
> But the relay search page says:
> Dir Address none
Yep! This is fine and normal, but I agree it is a surprise.
Thanx fot the quick explanation!
I have set it back to DirPort 0.
One comment, would it not make more sense to give an error when trying to set DirPort != 0?
When configured the tor process will open that (now useless??) port and allow connections to it.
If it is unused why not simply give an error telling that DirPort is depracted and the config directive was ignored?
> > I have DirPort 9030 in my config.
> > It is shown in nyx and the tor process listens there.
> > But the relay search page says:
> > Dir Address none
> > Why is it not shown and used by TOR?
Yes, this is new see release notes:
Removed features (relay):
Because DirPorts are only used on authorities, relays no longer advertise
them. Similarly, self-testing for DirPorts has been disabled, since an
unreachable DirPort is no reason for a relay not to advertise itself.
(Configuring a DirPort will still work, for now.) Closes ticket 40282.
One comment, would it not make more sense to give an error when trying to
set DirPort != 0? When configured the tor process will open that (now
useless??) port and allow connections to it. If it is unused why not simply
give an error telling that DirPort is depracted and the config directive
was ignored?
No, DirPort can still be used to publish an HTML file.
i.e.: DirPortFrontPage /etc/tor/tor-exit-notice.html
···
On Sunday, January 16, 2022 9:34:24 AM CET Richard Menedetter wrote: