I propose to reject these new DigitalOcean relays
(no contact/MyFamily)
+-+--+-+-+--+--+-+
| first_seen | fingerprint | tor_version
| or_port | dir_port
> Hello,
>
> Arthur and I have been emailing affected exit operators for a while
> now and many operators fixed their exits but some minor number or exits
> remain broken (even some that are running good tor versions).
>
> I believe it is reasonable to assign the BadExit flag to exits failing 100
Hi
AFter upgrade from 3.1.9 to 3.2.9, I've noticed that the cpu usage doubled
for same throughput / conditions. Is anyone else seeing that too?
Regards
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mail
Hello,
I upgraded 4 exits yesterday and apart from one of them suffering a
DDoS, I don't observe any large CPU increase.
Maybe your upgrade coincides with the recent overload of create cells?
https://trac.torproject.org/projects/tor/ticket/24716
Worth to keep an eye on it, anyway.
Best,
F
On Wed, January 17, 2018 7:16 am, nusenu wrote:
> I propose to reject these new DigitalOcean relays
> (no contact/MyFamily)
>
>
> +-+--+-+-+--+--+-+
> | first_seen | fingerprint
x9p:
> +1 blacklisted.
can you elaborate on what you mean with that?
thanks,
nusenu
--
https://mastodon.social/@nusenu
twitter: @nusenu_
signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject
Logged back in to check on it again this morning, and nyx is back to not
displaying any connections on the 2nd page.
--
John McDonnell
-Original Message-
From: John D. McDonnell
Sent: Tuesday, January 16, 2018 9:25 PM
To: 'tor-relays@lists.torproject.org'
Subject: RE: [tor-relays] nyx n
Hi John, I require the redacted logs to be able to help at all.
On Wed, Jan 17, 2018 at 6:32 AM, John D. McDonnell wrote:
> Logged back in to check on it again this morning, and nyx is back to not
> displaying any connections on the 2nd page.
>
> --
> John McDonnell
>
> -Original Message---
On Tue, 16 Jan 2018 20:18:00 +
nusenu allegedly wrote:
> Since this has been a common question in the last few days..
>
>
Excellent. Thanks. Installed and running. I still have problems, but I
have added some ratelimit rules to my firewall (a la teor
recommendations) and I'm getting fewer c
What logs do you need? I only logging at notice level in tor, so they're not
any help.
--
John McDonnell
-Original Message-
From: tor-relays [mailto:tor-relays-boun...@lists.torproject.org] On Behalf Of
Damian Johnson
Sent: Wednesday, January 17, 2018 10:58 AM
To: tor-relays@lists.torpr
Hi John, simply run 'nyx --debug' as discussed with Arisbe on this thread.
[1] https://lists.torproject.org/pipermail/tor-relays/2018-January/014173.html
On Wed, Jan 17, 2018 at 9:18 AM, John D. McDonnell wrote:
> What logs do you need? I only logging at notice level in tor, so they're not
> an
Sorry, I somehow missed that in the conversation. I'm sending you the logfile
off list as I'm sure I probably left stuff in there that should have been
redacted.
--
John McDonnell
Penn Cambria School District
-Original Message-
From: tor-relays [mailto:tor-relays-boun...@lists.torprojec
On 01/16/2018 11:15 PM, teor wrote:
> * it stops publishing an IPv6 ORPort or IPv4 DirPort,
> for one or more consensuses, even if it changes back.
Ick, that was it.
There was an attempt by me to close ports 80 and 443 of IPv6 for 1 minute to
let certbot try to renew the LetsEncrypt certificate ov
On Wed, January 17, 2018 10:04 am, nusenu wrote:
>
>
> x9p:
>> +1 blacklisted.
>
>
> can you elaborate on what you mean with that?
>
> thanks,
> nusenu
>
> --
> https://mastodon.social/@nusenu
> twitter: @nusenu_
>
> ___
> tor-relays mailing list
> tor-r
>> x9p:
>>> +1 blacklisted.
>>
>>
>> can you elaborate on what you mean with that?
>
>
> sorry. blocked on my relays.
If you mean "dropping all packets coming from and to these IP addresses
to your relays" by that, please don't do that. That breaks
functionality for tor clients, removal should h
> On 18 Jan 2018, at 05:18, Toralf Förster wrote:
>
>> On 01/16/2018 11:15 PM, teor wrote:
>> * it stops publishing an IPv6 ORPort or IPv4 DirPort,
>> for one or more consensuses, even if it changes back.
> Ick, that was it.
> There was an attempt by me to close ports 80 and 443 of IPv6 for 1 mi
I'm getting increased cpu usage also. On some VPSs I've had to
reduce bandwidth a little.
On 1/17/2018 2:50 AM, Florentin Rochet
wrote:
Hello,
I upgraded 4 exits yesterday and apart from one of them
suffering
On 01/17/2018 10:03 PM, teor wrote:
> If you need to do this in future, set PublishServerDescriptor 0.
Cool hint, thx.
--
Toralf
PGP C4EACDDE 0076E94E
signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.
Not any noticable difference in CPU usage for me:
https://kuehrmann.de/privateshare/20180117_tah6Eig8/cpu_usage.png
(upgraded Tor on January 15 at 9 AM, running a 300-400 Mbps Guard on FreeBSD,
Intel i7-6700, mysterious Tor clients (with lots connections) filtered by
firewall, DBE82FA23B9FE3CB2
19 matches
Mail list logo
