On Wed, Nov 05, 2014 at 12:17:50PM +0100, Karsten Loesing wrote:
On 01/11/14 01:44, David Fifield wrote:
This might be the key to the mystery. It must be that PacificSunset, despite being an obfs3 bridge, doesn't have ExtORPort enabled, so all its obfs3 connections are being counted as <OR> connections.
Hi David,
sorry for not replying earlier and for not replying in more detail.
I just wanted to say that your analysis looks plausible to me. Fixing PacificSunset's ExtORPort might indeed fix the metrics graphs.
Here's one more graph on the subject. The shading in the background indicates when PacificSunset was running (blue) and not running (white). It looks like the periods of highest correlation come while it is running.
I got the uptime information from https://onionoo.torproject.org/uptime?search=pacificsunset.
David Fifield
