I started running a non-exit node a few months ago and after a little while it became trusted and became a guard node. Guard nodes seems more important than amiddle node so I was happy to run one I know is legitimate. That makes at least one legitimate guard node for the network.
I noticed the attack when my mom said the wi-fi wasn't working well and I checked it out and the download speed was down 99% from normal. And eventually after various other troubleshooting attempts I turned off my mini pc where the relay and other self-hosted services run and the internet speed returned to normal. Yeah I'm not a very adept sys-admin, AI set up all the docker compose stacks for me.
I then looked at my relay on the relay search and it said overloaded. So I checked the Tor forum and sure enough others were reporting the same thing.
So at first I tried just lowering the bandwidth let through, although I'd thought it should already not be letting that much through. That did not work.
So I made it not become a guard node and now it works fine. But I also read something about malicious guards and exits being how Tor users have been compromised before. So it seems important guards are trustworthy.
I'm not gonna risk running a guard again (letting my node become a guard) at least for a while until this attack stabilizes.
I tried Tor briefly maybe about 10 years ago, only to have a little look around as I was curious, and to be honest I remember the experience was pretty disappointing, websites were slow and lots of resources seemed to be unavailable.
Has it changed much at all? I don't really know what most people get up to on Tor admittedly.
it's gotten much better - but yes the internet is inherently slower in it. some places build intentionally for it so can be fast (duckduckgo in particular)
DOS are always going to be a cat and mouse game on Tor. Who has an interest in shutting it down?
Usually they are directed at specific sites (competitors, etc), but this seems system-wide. Perhaps these are relays caught in the middle of a specific DOS?
Tor has made advances in POW challenges and things like that, but this may be even before that is triggered.
I noticed the attack when my mom said the wi-fi wasn't working well and I checked it out and the download speed was down 99% from normal. And eventually after various other troubleshooting attempts I turned off my mini pc where the relay and other self-hosted services run and the internet speed returned to normal. Yeah I'm not a very adept sys-admin, AI set up all the docker compose stacks for me.
I then looked at my relay on the relay search and it said overloaded. So I checked the Tor forum and sure enough others were reporting the same thing.
So at first I tried just lowering the bandwidth let through, although I'd thought it should already not be letting that much through. That did not work.
So I made it not become a guard node and now it works fine. But I also read something about malicious guards and exits being how Tor users have been compromised before. So it seems important guards are trustworthy.
I'm not gonna risk running a guard again (letting my node become a guard) at least for a while until this attack stabilizes.
Has it changed much at all? I don't really know what most people get up to on Tor admittedly.
Usually they are directed at specific sites (competitors, etc), but this seems system-wide. Perhaps these are relays caught in the middle of a specific DOS?
Tor has made advances in POW challenges and things like that, but this may be even before that is triggered.