[tor-bugs] #13658 [Onionoo]: discrepancy in Onionoo and bridge DB

[Tor Bug Tracker & Wiki]

#13658: discrepancy in Onionoo and bridge DB
-------------------------+----------------------
     Reporter:  eli      |      Owner:  karsten
         Type:  defect   |     Status:  assigned
     Priority:  normal   |  Milestone:
    Component:  Onionoo  |    Version:
   Resolution:           |   Keywords:
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+----------------------

Comment (by eli):

 > Can you explain why you think this number should be zero for a bridge in
 an email pool?

 Previous implementations of the bridge (last September or so, ~55 days
 uptime, under the name maushaus, running as a vanilla bridge in a https
 pool, had a nonzero advertized bandwidth which increased (though very
 slowly) with time. When looking at onionoo & the DB for this current
 implementation (assigned to the email pool) I just assumedthat the 0 BW
 would change in time. So far (after 16 or so days uptime) it hasn't.

 > Regarding obfs3, it seems the bridge doesn't include that transport in
 its
 > routerdescriptor. There would be a line "transport obfs3". Can you check
 the logs for
 > anything unusual?

  The only Warning I get in the log ia "Rejecting SOCKS request for
 anonymous connection to private address [scrubbed]. [3 similar message(s)
 suppressed in last 300 seconds" which from a old discussion in  tor-talk
 is unimportant.  The only line in the bridge torrc relating to transports
 is

 ClientTransportPlugin obfs3 exec Tor\PluggableTransports\obfsproxy managed

 I have no line "transport obfs3" - I didn't find anything relating to this
 (at least for bridges running on windows - in tor-manual.html.en or
 anywhere else. I'll try adding it and see what happens.

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