[metrics-bugs] #24160 [Metrics/Atlas]: Wrong info about bridges?

[Tor Bug Tracker & Wiki]

#24160: Wrong info about bridges?
---------------------------+------------------------------
 Reporter:  eduperez       |          Owner:  metrics-team
     Type:  defect         |         Status:  new
 Priority:  Medium         |      Milestone:
Component:  Metrics/Atlas  |        Version:
 Severity:  Normal         |     Resolution:
 Keywords:                 |  Actual Points:
Parent ID:                 |         Points:
 Reviewer:                 |        Sponsor:
---------------------------+------------------------------

Comment (by karsten):

 Replying to [ticket:24160 eduperez]:
 > I am currently running a bridge, and have tried to check it at
 atlas.torproject.org, but the info there seems to be wrong.
 >
 > I have copied the contents of the "hashed-fingerprint" file into the
 search box at ATLAS, and the info shown there seems to belong to my node:
 "nickname", "first seen", "last restarted", and "platform" all match my
 node. However, "OR address", and "advertised bandwidth" are off:
 >
 > * I have configured my node as "ORPort 9001", and effectively port 9001
 is open and listening; but ATLAS shows "IPv4:52563" at "OR address".

 The reason is that we're sanitizing TCP ports in order to make it harder
 to discover bridges with unusual ports. See https://metrics.torproject.org
 /bridge-descriptors.html#tcp-port

 I wonder if we should take out bridge OR address and ports from Atlas
 entirely. They were added before we started sanitizing TCP ports, and then
 they made some sense. But that may not be the case anymore.

 > * I have also configured "RelayBandwidthRate 512 KBytes" and
 "RelayBandwidthBurst 1024 KBytes", but ATLAS shows "55.09 KiB/s" at
 "advertised bandwith".

 The advertised bandwidth does not only depend on your configuration but
 also on what your relays reports. See
 https://metrics.torproject.org/glossary.html#advertised-bandwidth

 > Is this a known issue with ATLAS? Or perhaps I am misinterpreting the
 page? Many thanks!

 Not a code issue, but possibly a documentation issue. I'll leave it up to
 irl, the Atlas maintainer, to say whether there's something to fix in the
 documentation or presentation. Thanks for the report!

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24160#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online