Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-18 Thread Tim Wilson-Brown - teor
> On 13 Jan 2016, at 11:21, Tim Wilson-Brown - teor wrote: >> On 13 Jan 2016, at 10:33, Tim Wilson-Brown - teor > > wrote: >>> At 19:20 1/12/2016 +0100, Aeris wrote: ... After grepping some logs, seems 13/12 was the

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-17 Thread Tim Wilson-Brown - teor
> On 13 Jan 2016, at 02:56, Aeris wrote: > >> Here's the latest list of fallback directory candidates: >> https://trac.torproject.org/projects/tor/attachment/ticket/15775/fallback_di >> rs.inc.20160112 > > ... > (I already opt-in for it inclusion on december, with my

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-17 Thread Aeris
> kitten3 doesn't have a DirPort configured. Relays need a DirPort to be a > fallback directory mirror. Let me know if you are able to configure a > DirPort for it. > > Also let me know if you want to opt-in or opt-out other relays in that > family. Thanks for the report, corrected ! For others

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-14 Thread Paul Staroch
Hi, Am 2016-01-12 um 05:35 schrieb Tim Wilson-Brown - teor: Here's the latest list of fallback directory candidates: https://trac.torproject.org/projects/tor/attachment/ticket/15775/fallback_dirs.inc.20160112 Since my relay "rueckgrat" (0756B7CD4DFC8182BE23143FAC0642F515182CEB) is on the

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-12 Thread starlight . 2016q1
I'd guess a bug in the version update script. At 19:20 1/12/2016 +0100, Aeris wrote: >> Are you *absoultely* certain that the config >> was not fiddled with at the time of this event? > >After grepping some logs, seems 13/12 was the day of a Tor >upgrade : > >2015-12-13 10:47:31 upgrade

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-12 Thread Aeris
> Are you *absoultely* certain that the config > was not fiddled with at the time of this event? After grepping some logs, seems 13/12 was the day of a Tor upgrade : 2015-12-13 10:47:31 upgrade tor:amd64 0.2.7.5-1~d80.jessie+1 0.2.7.6-1~d80.jessie+1 2015-12-13 10:48:39 configure tor:amd64

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-12 Thread Tim Wilson-Brown - teor
> On 12 Jan 2016, at 16:09, starlight.201...@binnacle.cx wrote: > > Hmm, don't see the script in this Git repository, > most recently updated files are from a month ago. Yes, my branch has some bug fixes that are awaiting review before they get merged into tor master. > > > At 15:35

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-12 Thread Toralf Förster
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/12/2016 05:35 AM, Tim Wilson-Brown - teor wrote: > If you run an under-utilised exit, we encourage you to opt-in as a > fallback directory. > We've also fixed a major bug that excluded some relays from the list. Well, I to amintain an exit

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-12 Thread 12xBTM
On 12.1.16 9:47, Toralf Förster wrote: > On 01/12/2016 05:35 AM, Tim Wilson-Brown - teor wrote: >> If you run an under-utilised exit, we encourage you to opt-in as a >> fallback directory. >> We've also fixed a major bug that excluded some relays from the list. > > Well, I to amintain an exit

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-12 Thread Aeris
> Here's the latest list of fallback directory candidates: > https://trac.torproject.org/projects/tor/attachment/ticket/15775/fallback_di > rs.inc.20160112 Is this list removes already included fallback nodes ? Previously, my node kitten1 was on the list, but not on this one. (I already opt-in

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-12 Thread starlight . 2016q1
Just sent a request to the contact of three affected relays asking they post daemon log entries if they have them. Hopefully someone can retrieve the information and it will shed some light on what's happening. At 10:33 1/13/2016 +1100, Tim Wilson-Brown - teor wrote: >>At 19:20 1/12/2016 +0100,

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-12 Thread Tim Wilson-Brown - teor
> At 19:20 1/12/2016 +0100, Aeris wrote: >>> Are you *absoultely* certain that the config >>> was not fiddled with at the time of this event? >> >> After grepping some logs, seems 13/12 was the day of a Tor >> upgrade : >> >> 2015-12-13 10:47:31 upgrade tor:amd64 0.2.7.5-1~d80.jessie+1 >>

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-12 Thread Tim Wilson-Brown - teor
> On 13 Jan 2016, at 10:33, Tim Wilson-Brown - teor wrote: > > >> At 19:20 1/12/2016 +0100, Aeris wrote: Are you *absoultely* certain that the config was not fiddled with at the time of this event? >>> >>> After grepping some logs, seems 13/12 was the day of a

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-12 Thread Aeris
> DEBUG:root:86E78DD3720C78DA8673182EF96C54B162CD660C not a candidate: changed > address/port recently (2015-12-13 11:00:00) Hum… Don’t know how is it possible, this relay has the same IP/port since it creation 1 year ago. From CollecTor, seems there is only a single network glitch, and only on

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-12 Thread starlight . 2016q1
At 16:56 1/12/2016 +0100, you wrote: >Is this list removes already included fallback nodes ? >Previously, my node kitten1 was on the list, but >not on this one. >(I already opt-in for it inclusion on december, >with my others nodes (kitten[1-4])). Reason is listed in the the attachment to the

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-12 Thread starlight . 2016q1
Perhaps this is a bug in the consensus system. Pulling the consensus archive and grepping, exactly the one single consensus is showing DirPort as zero: 12-13-09-cons:r kitten1 vG0ZWLi31UXoqz4H2H/hweSvxqo 04:44:19 62.210.124.124 9001 9030 12-13-10-cons:r kitten1 vG0ZWLi31UXoqz4H2H/hweSvxqo

[tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-11 Thread Tim Wilson-Brown - teor
Hi all, Nick sent an email in December[0] asking relay operators to opt-in as a fallback directory mirror. This will help tor clients reach the tor network, and reduce the load on directory authorities.[1] We will keep the opt-ins and opt-outs submitted so far - no need to opt-in or opt-out

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

2016-01-11 Thread starlight . 2016q1
Hmm, don't see the script in this Git repository, most recently updated files are from a month ago. At 15:35 1/12/2016 +1100, you wrote: >This list was generated a few minutes ago from >scripts/maint/updateFallbackDirs.py in my branch fallback-17887-17888-18035 on >[2]. (This branch has some