Re: [tor-relays] DoS statistics from EA4366BCDCA6167B8CFF70E41D8CD1EE9968E445

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

Re: [tor-relays] DoS statistics from EA4366BCDCA6167B8CFF70E41D8CD1EE9968E445

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

Re: [tor-relays] DoS statistics from EA4366BCDCA6167B8CFF70E41D8CD1EE9968E445

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

Re: [tor-relays] DoS statistics from EA4366BCDCA6167B8CFF70E41D8CD1EE9968E445

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

[tor-relays] DoS statistics from EA4366BCDCA6167B8CFF70E41D8CD1EE9968E445

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

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

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

Re: [tor-relays] Tor program

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

Re: [tor-relays] new Tor exit

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

Re: [tor-relays] new Tor exit

Holy Cow!  The new Toe exit I just crabbed about just took off. My apologies everyone! (23:39 PDT) Arisbe On 3/14/2018 11:03 PM, Arisbe wrote: Hello all, I rolled out a new Tor exit [0] this morning West Coast U.S. time.  It's special to me because I've negotiated the trust of a host

Re: [tor-relays] new Tor exit

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#MultipleRelays. In regards to new relay usage, see https://blog.torproject.org/lifecycle-new-relay

Re: [tor-relays] new Tor exit

2018-03-15 7:03 GMT+01:00 Arisbe : > > Here is my problem: The aforementioned relay has been on for nearly > 24-hours and not a single user has frequented my doorsteps. https://blog.torproject.org/lifecycle-new-relay ___ tor-relays

[tor-relays] new Tor exit

Hello all, I rolled out a new Tor exit [0] this morning West Coast U.S. time.  It's special to me because I've negotiated the trust of a host company in Albania.  I was the first Tor relay in that country and now I'm the first exit relay there.  This trust took me a year to establish.  I run