Re: [tor-relays] "Received http status code 404 ("Consensus is too old")" keeps popping up in my logs

2018-03-15 Thread teor
> On 13 Mar 2018, at 22:20, nottryingtobel...@protonmail.com wrote: > > I'm just wondering if there is anything I can do to resolve this. The relay > is running ntpd and consistently keeps the right time, and I'm not getting > this from any other server (it's the same IP address every time). Is

Re: [tor-relays] DoS statistics from EA4366BCDCA6167B8CFF70E41D8CD1EE9968E445

2018-03-15 Thread robink
I have changed to a non-google DNS. I will look into running a local resolver/unbound. BTW, the "eventdns: All nameservers have failed.." and then quickly "...is back up" error has been with around for a long time, also when I was running tor stable. kind regards, Robin - Original messag

Re: [tor-relays] DoS statistics from EA4366BCDCA6167B8CFF70E41D8CD1EE9968E445

2018-03-15 Thread Matt Traudt
On 3/15/18 23:38, Toralf Förster wrote: > On 03/15/2018 10:02 PM, robink wrote: >> Mar 15 19:03:52.000 [warn] eventdns: All nameservers have failed >> Mar 15 19:03:52.000 [notice] eventdns: Nameserver 8.8.4.4:53 is back up >> Mar 15 19:04:01.000 [warn] eventdns: All nameservers have failed >> Mar 1

Re: [tor-relays] DoS statistics from EA4366BCDCA6167B8CFF70E41D8CD1EE9968E445

2018-03-15 Thread Toralf Förster
On 03/15/2018 10:02 PM, robink wrote: > Mar 15 19:03:52.000 [warn] eventdns: All nameservers have failed > Mar 15 19:03:52.000 [notice] eventdns: Nameserver 8.8.4.4:53 is back up > Mar 15 19:04:01.000 [warn] eventdns: All nameservers have failed > Mar 15 19:04:01.000 [notice] eventdns: Nameserver 8

Re: [tor-relays] DoS statistics from EA4366BCDCA6167B8CFF70E41D8CD1EE9968E445

2018-03-15 Thread nusenu
robink: > Mar 15 19:15:30.000 [notice] eventdns: Nameserver 8.8.8.8:53 is back upMar 15 > 19:15:37.000 [warn] eventdns: All nameservers have failed > Mar 15 19:15:37.000 [notice] eventdns: Nameserver 8.8.4.4:53 is back up thanks for running an exit relay, please use a non-google DNS resolver if

[tor-relays] DoS statistics from EA4366BCDCA6167B8CFF70E41D8CD1EE9968E445

2018-03-15 Thread robink
Running tor 0.3.3.3 Mar 15 19:00:44.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:00:48.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:01:17.000 [warn] Tried to est

Re: [tor-relays] middle relay connexions dropped in half

2018-03-15 Thread torix
Thanks; this was a really helpful reply; when the electricity goes off, one tends to check one's own plug rather than think the main transformer just died. Especially the capacity/latency part; I would never have gotten that by myself. ​Sent with ProtonMail Secure Email.​ ‐‐‐ Original Me

Re: [tor-relays] Tor program

2018-03-15 Thread Colin Childs
Hi Arisbe, Here are some resources that may come in helpful, please feel free to reach out directly if you need any clarification or additional resources. 1. https://www.eff.org/pages/tor-and-https this interactive graphic helps illustrate what Tor and

Re: [tor-relays] new Tor exit

2018-03-15 Thread Arisbe
I appreciate the reminder.  I think we are okay. Arisbe On 3/14/2018 11:23 PM, Jordan wrote: Hi Arisbe, Thanks for running relays! If you're running multiple relays (as you've suggested) it's important to run then under the same family, see https://www.torproject.org/docs/faq.html.en#Multip