| ▲ | Actor 2 hours ago | ||||||||||||||||||||||||||||
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. | |||||||||||||||||||||||||||||
| ▲ | Retr0id an hour ago | parent | next [-] | ||||||||||||||||||||||||||||
I'm not sure why this comment was flagged. Vouched. | |||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||
| ▲ | sitzkrieg an hour ago | parent | prev [-] | ||||||||||||||||||||||||||||
impressive you ran a guard on your isp service | |||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||