Hi
> > I've noticed a new kind of possible attack on some of my relays, as
> > early as Dec.23 which causes huge spikes of outbound traffic that
> > eventually maxes out RAM and crashes Tor. The newest one today
> > lasted for 5 hours switching between two of the three relays on the
> > same IP.
>
On 1/13/24 18:29, George Hartley via tor-relays wrote:
Is anyone else experiencing this?
Yes,
https://gitlab.torproject.org/tpo/core/tor/-/issues/40749
--
Toralf
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.
Hi
>Sorry, but I'm going to vent a little bit. I'm not a network
>specialist, so 11 days ago I sent the following email to this
> mailing list asking for help because two of my Tor exit relays were
> completely frozen and I was unable to put them online again.
According to
https://metrics.
This happened to several oft my nodes. They even lost their guard flags, while
other nodes running on the same host are not affected.
On the 5 year graph I can see their stats going back years.
___
tor-relays mailing list
tor-relays@lists.torproject.org
On 1/15/24 3:19 PM, Chris Enkidu-6 wrote:
I've noticed a new kind of possible attack on some of my relays, as
early as Dec.23 which causes huge spikes of outbound traffic that
eventually maxes out RAM and crashes Tor. The newest one today lasted
for 5 hours switching between two of the three rela
Checking the available memory of my 2 GBytes server with Linux commend: free -m
the relay runs out of memory after rebooting within a few minutes while the
connections raise to the now usual 10600 connections. A few minutes the
available memory is about 90 MBytes and then the relay reboots.
It h
I've noticed a new kind of possible attack on some of my relays, as
early as Dec.23 which causes huge spikes of outbound traffic that
eventually maxes out RAM and crashes Tor. The newest one today lasted
for 5 hours switching between two of the three relays on the same IP.
During the attack, Tor b
It's not just you. 3 of my relays show as new for the past few days and
they still do. It doesn't seem to affect the traffic though so I'm
assuming it's just a reporting issue and Authorities don't see your
relay as new.
On 1/12/2024 1:00 PM, Keifer Bly wrote:
> Hi,
>
> So my relay
> at
> https:
I had this issue too. It resolved itself shortly within a few hours.
Original Message
On Jan 15, 2024, 05:23, Petrarca via tor-relays wrote:
> Just to confirm - the same happens to my relay, so this seems to be a general
> issue.
>
> Keifer Bly schrieb am Montag, 15. Januar 20
Just to confirm - the same happens to my relay, so this seems to be a general
issue.
Keifer Bly schrieb am Montag, 15. Januar 2024 um 09:29:
> Hi,
>
> So my relay at
> https://metrics.torproject.org/rs.html#details/79E3B585803DE805CCBC00C1EF36B1E74372861D
> is suddenly saying it's a new relay
There seems to be an issue with the metrics page,
mine(3A8D61AC59FD4F9AC7CC82B4B58FCC451578DC3B) has higher uptime than the first
seen which is very interesting 🤔
\ Original Message
On Jan 15, 2024, 1:33 PM, Keifer Bly < keifer@gmail.com> wrote:
>
>
>
> Hi,
>
>
>
>
> So m
Starting about a week or so the number of connections raised rapidly to 18000+
and since then my middle relay reboots every 15 minutes. Lowering the
relaybandwidth to a few MBytes partly solved these reboots. Before these
unplanned reboots the relay has run for months at 20 - 40 MBytes traffic
Keifer Bly:
Hi,
So my relay at
https://metrics.torproject.org/rs.html#details/79E3B585803DE805CCBC00C1EF36B1E74372861D
is suddenly saying it's a new relay. Don't know why this would happen as
it's been running for a few years, but suddenly saying it's new?
Should be fine again right now, no? W
Dear operators,
I'm conducting a study to understand relay operator motivations and needs,
funded by OTF.
If you had about 30-45 minutes to talk (completely anonymously if you wish)
about your experience as a relay operator, it will really help this research,
especially if you're running a rel
Hi,
I think this started with release 0.4.8.10, but both of my Tor relays no longer
reload their config when doing for example:
- systemctl reload tor@exit
Here is the relevant part of the unit file:
> [Unit]Description=Anonymizing overlay network for TCP
> After=syslog.target network.tar
I run the following relay:
https://metrics.torproject.org/rs.html#details/6C336E553CC7E0416EBC8577A7289349B757F6C3.
I just noticed that my relay’s ‘first seen’ date got reset. Tor now thinks
that my relay is less than 2 weeks old. But
Hi,
So my relay at
https://metrics.torproject.org/rs.html#details/79E3B585803DE805CCBC00C1EF36B1E74372861D
is suddenly saying it's a new relay. Don't know why this would happen as
it's been running for a few years, but suddenly saying it's new?
Thanks.
--Keifer
__
17 matches
Mail list logo
