Re: [tor-relays] arm crashes

2018-03-23 Thread Gary
Hello. On 23 March 2018 at 21:13, Roger Dingledine wrote: > On Fri, Mar 23, 2018 at 11:53:08AM -0400, smichel0 wrote: > > Yes, thank you. Nyx is running, but the relay is down again. It was down > in the morning. I restartet it and now it's obvisely down again since noon. > But nyx is still OK.

Re: [tor-relays] arm crashes

2018-03-23 Thread Roger Dingledine
On Fri, Mar 23, 2018 at 11:53:08AM -0400, smichel0 wrote: > Yes, thank you. Nyx is running, but the relay is down again. It was down in > the morning. I restartet it and now it's obvisely down again since noon. But > nyx is still OK. > > Now I restartet it and enclosed the log because the log ma

Re: [tor-relays] My relay lost concensus

2018-03-23 Thread Matt Traudt
On 3/23/18 12:55, victor...@riseup.net wrote: > El 23/03/18 a las 12:34, Matt Traudt escribió: >> >> Does your relay do both IPv4 and IPv6? Did your IPv4/6 address change? >> > > Thanks. I haven't realised there is a problem with its IPv6 address, > even if it the prefix hasn't changed. I am disab

Re: [tor-relays] My relay lost concensus

2018-03-23 Thread victoring
El 23/03/18 a las 12:34, Matt Traudt escribió: > On 3/23/18 12:31, victor...@riseup.net wrote: > > Hi, > > > > After a power cut a couple of weeks ago, my tor relay is not longer part > > of the consensus: > > B33BFA9AA0005730C1C0E8F7E6F53CF3C5716BD6 > > > > Current tor process has been running s

Re: [tor-relays] My relay lost concensus

2018-03-23 Thread Matt Traudt
On 3/23/18 12:31, victor...@riseup.net wrote: > Hi, > > After a power cut a couple of weeks ago, my tor relay is not longer part > of the consensus: > B33BFA9AA0005730C1C0E8F7E6F53CF3C5716BD6 > > Current tor process has been running since 2018-03-14. How much time is > it needed to come back? >

[tor-relays] My relay lost concensus

2018-03-23 Thread victoring
Hi, After a power cut a couple of weeks ago, my tor relay is not longer part of the consensus: B33BFA9AA0005730C1C0E8F7E6F53CF3C5716BD6 Current tor process has been running since 2018-03-14. How much time is it needed to come back? Cheers, S ___ tor-r

Re: [tor-relays] Publishing bridge contact information

2018-03-23 Thread Karsten Loesing
On 2018-03-04 23:26, Roger Dingledine wrote: > On Tue, Feb 20, 2018 at 05:51:44PM +0100, Karsten Loesing wrote: >> FWIW, we collected all feedback from this thread, discussed this change >> in the metrics team, and forwarded our planned change to the Tor >> Research Safety Board. I don't know how f

Re: [tor-relays] DoSer is back, Tor dev's please consider

2018-03-23 Thread David Goulet
On 22 Mar (23:20:54), tor wrote: > > Suggestion: DoSCircuitCreationMinConnections=1 be established in consensus > > > The man page for the above option says: > > "Minimum threshold of concurrent connections before a client address can be > flagged as executing a circuit creation DoS. In other wo

Re: [tor-relays] arm crashes

2018-03-23 Thread Gary
Hello. It is good you got it working, On 23 March 2018 at 05:04, smichel0 wrote: > > Tor has now a uptime of about 22 hrs, it ran with an up-/download-average > of about 47 KB/sec which is really low. > Now there is no up- or download at all. If it is a new relay it takes at least a week for fo

Re: [tor-relays] DoSer is back, Tor dev's please consider

2018-03-23 Thread starlight . 2017q4
At 03:20 3/23/2018 +, tor wrote: >> Suggestion: DoSCircuitCreationMinConnections=1 be established in consensus > >The man page for the above option says: > >"Minimum threshold of concurrent connections before a client address can be >flagged as executing a circuit creation DoS. In other words