[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #26783 [Obfuscation/Snowflake]: Snowflake statistics appear to be broken from something plus mid-June

#26783: Snowflake statistics appear to be broken from something plus mid-June
-----------------------------------------+------------------------
 Reporter:  TracTorProjectSucksRightNow  |          Owner:  (none)
     Type:  defect                       |         Status:  new
 Priority:  Medium                       |      Milestone:
Component:  Obfuscation/Snowflake        |        Version:
 Severity:  Normal                       |     Resolution:
 Keywords:                               |  Actual Points:
Parent ID:                               |         Points:
 Reviewer:                               |        Sponsor:
-----------------------------------------+------------------------

Comment (by dcf):

 I'm not sure what's wrong. I checked and there were not any configuration
 changes on the bridge in June. It's missing from Onionoo too:
 https://metrics.torproject.org/rs.html#details/5481936581E23D2D178105D44DB6915AB06BFB7F

 The bridge is still producing stats locally:
 {{{
 # cat /var/lib/tor/stats/bridge-stats
 bridge-stats-end 2018-07-14 05:36:29 (86400 s)
 bridge-ips cn=8,in=8,ma=8
 bridge-ip-versions v4=8,v6=0
 bridge-ip-transports snowflake=8
 }}}

 It may have something to do with #26771, which is a change of bridge
 authority. Apparently there was something wrong with the previous bridge
 authority, Bifroest. But I don't know if it could have caused this
 problem.
 https://lists.torproject.org/pipermail/tor-announce/2018-July/000162.html

 I've added this line to the torrc, but I don't think it will help. I
 believe the bridge authority is only for BridgeDB purposes, not for
 metrics collecting.
 {{{
 AlternateBridgeAuthority Serge orport=9001 bridge 66.111.2.131:9030 BA44
 A889 E64B 93FA A2B1 14E0 2C2A 279A 8555 C533
 }}}

 In May 2017, we had the same problem of the Snowflake bridge not
 publishing statistics. Then, we worked around it by setting
 `AssumeReachable 1`. Two other default bridges, cymrubridge31 and
 cymrubridge33, were not—and still are not :(—publishing statistics, and no
 one was ever able to determine the cause. Maybe we are being affected by
 the same thing again.
 https://lists.torproject.org/pipermail/tor-dev/2017-May/012241.html
 https://lists.torproject.org/pipermail/tor-dev/2017-June/012291.html
 (thread continues)

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

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