Conversation

twitter.com/DanielMicay/st This started happening again but github.com/GrapheneOS/inf has deterred it for the time being per 's suggestion. It's a stopgap for now and will need to be made stricter for IPv6 along with deploying a better solution to this new annoyance.
Quote Tweet
Our ns1.grapheneos.org DNS server was targeted by a DoS attack yesterday. They didn't target the DNS service but rather... SSH. That's a new one. Can see the traffic spike but it was hardly anything compared to the usual attacks. Still, SSH buckled. nodeping.com/reports/status
2
7
We've pretty much won that now. Unfortunately, many of the people involved with that moved on to a different community and have gotten even more aggressive bothering us in even more ways than before. It really never ends. They aren't very good at DoS / DDoS attacks at least.
1
1
They've been trying to do those attacks where you send a POST request and then trickle through the content body at super slow speed... to static web servers not accepting POST requests. Setting lower size limits, per-IP limits, etc. has dealt with most low-hanging fruit now.
1
1
They also let you set up to 20 manual IPv4 firewall rules for the DoS firewall which get enforced on the super high bandwidth DoS firewall system rather than on your dedicated server / VPS so it doesn't hurt your bandwidth. It also only slows down incoming bandwidth for that.
1
2
Show replies