remember people, ther is no one right way to do things with computers, only “a way to do it” and “a better way to do it” (and there is always a better way) - no-one aspires to do it “a worse way”, unless maybe you are a government employee with “highly knowledgable superiors”.
(guess thats sorted then - and the initial responder was a mod too - shame on you - ziiiiiiiip)
using other ports does not really work, I’ve checked the various (common) scriptable “probe” options, and they can spam ports for known protocols, not just spam known protocols on known ports. some dont even wait for a response (yay lets ping 10 million different IP adresses per second)
not automatically. Linode has controls in place to catch and disconnect “compromised” servers. What constitutes a compromised server is up for debate, but it includes, and is not limited to:
- “super” high volume outgoings (external, vertical - same IP, different ports)
- “super” high volume outgoings (internal - DMZ, inside hosting zone)
- spam volume outgoings (internal - DMZ, inside hosting zone)
- spam volume outgoings (external, horizontal - same ports, different IP)
I dont know it that makes any sense to anyone (without getting into elaborate details), but thats (part of) the gist of it.
They dont shut down the server, they lock it off (iscolate it internally), send a warning saying “if this continues we are going to shut it down”. They are pretty quick about it too.
On the SS:FragWhare proto server (on Linode Texas) I do get hit from inside the DMZ for that zone from time to time, and I could have manually blocked a few more, but when I checked their source they were gone already. Last month I undid a couple of blocked IPv4 from a few other zones they have. Yes its on the rise, but all-in-all, Linode have a good handle on things (not so much anyone else)
For anyone interested Automated Threat Response was how SS:FragWhare came about, and there is at least 2 posts specifically about this question, one being why it was not implimented.
EDIT: tried to clarify those network details above, and made IP/sec accurate (10 not 14)