Character
Rules
Events
Map
RP Points
Proplimits
Statistics
Steam Group
Members
Hall of Fame
Team
Bans
Blacklists
Warnings
Changelog
Content
08-16-2014, 02:38 PM
(This post was last modified: 09-01-2022, 01:03 AM by Fearless Community.
Edit Reason: Checked Encoding
)
This type of this is right in my field, so i'll try and give some advice even though someone who thinks there a leet hacker will try and correct me.
Most people who attack game servers use either a hosted booter or a self coded one, i had an old friend who made a DOS(Not DDOS - Don't correct this) function that ran on an old laptop that he had plugged into his router. I can't remember what coding language it was but it was either Ruby or C#. But he made it in a way that it wold attack for around 10 minutes every 1 hour. But the severity of the attack was enough to shut the server down for the entire time till it rebooted.
People who have hosted Booters will have a similar function depending on how much they pay. Low budget ones will have limited boot times and cool downs to make sure their own shells dont crash.
So to put it simply, if who ever is attacking the server isn't a 12 year old who thinks he has power using LOIC on his pc the attacks can be scheduled, meaning they won't really get bored as they no longer have to do much in order to boot the servers.
Cloudflare will prevent the forums being taken down in effect, however, there is nothing of the sort available for game servers. Even if there was, constantly checking all ips and the data packets they are sending would probably cause just as much lag.
Long story short - no way to stop ddos attacks. Unless, you null route the IP of the attackers every time it happens. Not efficient as there is an almost infinite possiblilities of IPs that are available due to proxies, VPNS and hosts. But it would stop that attack in its track.
The other way to stop it is to "fight fire with fire.", I also have a friend that ran a Dark RP server. When ever some even said so much as "i will ddos this" i would notice that a guy that i now know as "System 32" Would join the game, followed by the threatening player timing out.
If anyone has even read down this far they are clearly very bored.
Most people who attack game servers use either a hosted booter or a self coded one, i had an old friend who made a DOS(Not DDOS - Don't correct this) function that ran on an old laptop that he had plugged into his router. I can't remember what coding language it was but it was either Ruby or C#. But he made it in a way that it wold attack for around 10 minutes every 1 hour. But the severity of the attack was enough to shut the server down for the entire time till it rebooted.
People who have hosted Booters will have a similar function depending on how much they pay. Low budget ones will have limited boot times and cool downs to make sure their own shells dont crash.
So to put it simply, if who ever is attacking the server isn't a 12 year old who thinks he has power using LOIC on his pc the attacks can be scheduled, meaning they won't really get bored as they no longer have to do much in order to boot the servers.
Cloudflare will prevent the forums being taken down in effect, however, there is nothing of the sort available for game servers. Even if there was, constantly checking all ips and the data packets they are sending would probably cause just as much lag.
Long story short - no way to stop ddos attacks. Unless, you null route the IP of the attackers every time it happens. Not efficient as there is an almost infinite possiblilities of IPs that are available due to proxies, VPNS and hosts. But it would stop that attack in its track.
The other way to stop it is to "fight fire with fire.", I also have a friend that ran a Dark RP server. When ever some even said so much as "i will ddos this" i would notice that a guy that i now know as "System 32" Would join the game, followed by the threatening player timing out.
If anyone has even read down this far they are clearly very bored.
wannabe skid
![[Image: J8Wdw2Z.gif]](https://i.imgur.com/J8Wdw2Z.gif)