Early on April 11th, one of my middle relays was hit with a large DDoS,
my provider was able to divert the attack but has not been able to
produce any other information.
//Brian
Green Dream:
> One of my non-exit relays was knocked offline by a DDoS on April 10th. It's
> happened before to another
Hey everybody,
I'd like to invite you to the first Dutch Tor relay operator meetup
organized by Bits of Freedom and stichting
HVIV(https://hartvoorinternetvrijheid.nl/)
The first meeting[1] will take place on the 11th of May in Utrecht, in
the center of the Netherlands. The cafe where we'll meet
One of my non-exit relays was knocked offline by a DDoS on April 10th. It's
happened before to another relay as well.
My provider isn't especially helpful when it happens. They basically just
disable traffic to the node for 3 hours.
___
tor-relays mailin
Hi,
my hoster notified me about nullrouting due to packet floods (?) against
two diffferent relays on April 12 and April 17.
Has this been happening to other people in the same time frame?
Best,
Luke
___
tor-relays mailing list
tor-relays@lists.torp
> On 18 Apr 2016, at 20:18, George Kadianakis wrote:
>
> PS: We could also in theory imagine writing those descriptors on disk, and
> only
> caching the ones that we have received requests for lately. This way we
> would not utilize our RAM that much…
Hmm, there is a disk DoS risk here, pa
Tim Wilson-Brown - teor:
>
>> On 18 Apr 2016, at 14:14, eliaz wrote:
>>
>> In looking at the check.torproject.org page on the browser/machine that
>> runs my bridge, I'm used to seeing the same IP address a.b.c.d on the
>> check page ("Your IP address appears to be: a.b.c.d") as in the exit on
>>
