[QUOTE=DrogenViech;43356281]I'm just going to leave this here:
[IMG]http://s29.postimg.org/7gv21vwaf/wtfisddos.jpg[/IMG][/QUOTE]
Also note that it doesn't have to be an infected computer of any sort. Example: Anonymous and LOIC.
[QUOTE=Ananda;43356326]Also note that it doesn't have to be an infected computer of any sort. Example: Anonymous and LOIC.[/QUOTE]
+10 Faith in Humanity
Thanks for your input and knowledge. Huggies.
But, I am curious, and it may seem like a stupid question, but is it possible for "Zombies" to be our computers? Or would you know if your computer is a Zombie? :V
... Oh my god. The Zombie apocalypse is going to also be a robot apocalypse when Zombie Computers come to life.
I just figured out the end of the world.
[QUOTE=DrogenViech;43356281]I'm just going to leave this here:
-complete and utter nonsense-[/QUOTE]
Obliviously some people don't excel in much in life and so being able to "sound technical" on a subject that is very easy to comprehend gives a sense of importance.
Your problem is that you're talking nonsense and your illustration is false. You can set up multiple virtual networks and have them run through a DSN, or you could likewise have a set of servers you use for your attacks. A botnet is completely irrelevant. You don't need multiple computers to do a DDoS attack, nor do you need to have "slaves" (as in a botnet).
Any child can run a simple script and do it - it's simple. The harder part is writing your own encrypted client that can use other remote networks to do the task, without there being a connection from your own network to the crime-committing networks.
And as far as I've heard it's some young French guys who did it. I wouldn't be surprised if these.. people.. feel a sense of intelligence when they are proclaimed "hackers" and when little kids threaten them. But obviously it's an immature, underdeveloped, child-like bunch that are doing this. There is no - or doesn't seem to be any - self-interest in doing this. The only "positive" outcome is a psychological feeling of superiority or wellbeing, but such can be induced merely by repeating a slogan.
[QUOTE=BlackScienceM;43356351]-Clippity-[/QUOTE]
He's just trying to help. Since you're "smarter", why are you reading this? And if you're reading it, why not provide positive input that helps people (which was the point of this in the first place.)
I also feel "hacker" is an easy term to throw around, because it's pretty broad except for perfectionists who can't handle a generalized term for lifeless folk who try to ruin gaming for everyone else.
Oh. And if you've got a better illustration, please feel free to post it! Otherwise..
Please, just leave now. You're making me frown. ;D
[QUOTE=Reichvier;43353177] ...[/QUOTE]
you not wrong, but you are kind of an asshole, the OP is giving his/her best explanation to people who have no idea what is going on, the ones who actually care about the details/difference already know what is going on and this isnt intended for them
[editline]30th December 2013[/editline]
[QUOTE=DrogenViech;43356281]...[/QUOTE]
just change "infected computer" to a "slave PC", this covers botnets that are viral and those that are intentional
[QUOTE=Ananda;43356326]Also note that it doesn't have to be an infected computer of any sort. Example: Anonymous and LOIC.[/QUOTE]
There is also the reflection attack using improperly configured DNS servers, but i didn't want to go into full detail - i don't want to confuse the not-so tech savvy users in here (It's so hard to make this not sound offensive, lol)
[B]Edited:[/B]
[QUOTE=BlackScienceM;43356351]long text[/QUOTE]
Again, i'm well aware of the other methods to execute a DDoS and i am just trying to keep it simple so everyone understands it, no need to get that worked up about it. The machines that say 'infected' can be indeed even servers that have been willingly bought and set up to execute the DDoS attack.
[B]Edited:
[/B]I expanded the chart a bit and edited my old post.
[QUOTE=BlackScienceM;43356351]You don't need multiple computers to do a DDoS attack, nor do you need to have "slaves" (as in a botnet).
[/QUOTE]
You're talking about a DoS, not a DDoS. DDoS needs several machines/mirrors/slaves/whatevers (there's many ways), it is in the name. That's why its a [I]distributed[/I] DoS.
[QUOTE=DrogenViech;43356535]-Clippity-[/QUOTE]
Be offensive. We like offensive. It helps us see who has a sense of humor and who does not. I still appreciate the charts and hope people look this far into the comments to see them. If I may, at some point when I'm not drunk tired, I'd like to add them to the post itself.
[QUOTE=MorbidWolfess;43356820]Be offensive. We like offensive. It helps us see who has a sense of humor and who does not. I still appreciate the charts and hope people look this far into the comments to see them. If I may, at some point when I'm not drunk tired, I'd like to add them to the post itself.[/QUOTE]
I don't know who you are. I don't know what you want, but call me maybe and i luv ya
lol... badgers!
[video=youtube;EIyixC9NsLI]http://www.youtube.com/watch?v=EIyixC9NsLI[/video]
[highlight](User was banned for this post ("Off-topic" - MaxOfS2D))[/highlight]
Meanwhile on "Garry" Springer...
[highlight](User was banned for this post ("Why reply?" - MaxOfS2D))[/highlight]
[QUOTE=B!N4RY;43353890]Your DDOS analogy is honestly the worst and the most irrelevant analogy I've ever heard.[/QUOTE]
Then perhaps SUGGEST something instead of being a moronic ass who isn't contributing anything to the conversation.
[QUOTE=ping ling;43356849]I don't know who you are. I don't know what you want, but call me maybe and i luv ya[/QUOTE]
Give me your steam and I'll stalk you.
[QUOTE=LuaChobo;43356900]Fun fact, people can still say an alpha is bad as long as they recognize its an alpha.
If its up for public consumption it's up for criticism.[/QUOTE]
I can also offer my humble opinion on people who say an alpha is bad, and my opinion on the alpha itself, while also providing as much insight as possible to those who have no idea what they've gotten into.
I mean. I get it now that people will complain about what they want, and people don't actually care if it's an alpha, to them it's a game that they spent money on. And yeah. People can criticize all they want, but I can criticize the critics for their idiotic criticisms when they obviously knew what they were getting themselves into. <3
[QUOTE=LuaChobo;43357268]I'm more or less talking about people that say its bad/good with what it currently has, then people get all mad with "its alpha" and "muh money well spent"
people that bitch about features will generally always be ignored by devs, because its a "what you need" not "what you want" scenario when it comes to development[/QUOTE]
Yes. People seem to have the mindset of "It's what I want, not what anyone else wants." Like, some people love the game but would like to see more features for PvE too. Not saying they drop the entire PvP thing, because y'know. It's better for revenue and money making to appeal to only one color of the rainbow. I think they're doing fine as of right now, and probably doing what they can.
That... and... nobody tends to provide feedback, instead they complain about it. I made a few humble suggestions, but they were nothing extremely major in my opinion. And y'know. Suggestions are cool and nice, some Dev's are like "Oh hey that's an awesome idea", others are "Maaaan I know what I'm doooinnn get your noobcake ass outta here."
What I can't stand is people who are intolerant to things that the devs can't really actively control.
I mean. French guys crossing baguettes and trying to ruin the party seems pretty uncontrollable to me. Maybe it's the size of the baguettes, or their nasal laughter.
[QUOTE=MorbidWolfess;43357232]Give me your steam and I'll stalk you.
[/QUOTE]
Ask and you shall receive, sent to your inbox
While your original post was somewhat misleading, it was for the most part correct. There's a few things you forgot to mention about DDoS but as it stands you covered the basics for the people who aren't exactly the brightest when it comes to understanding these issues.
From a technical perspective: You've said a lot wrong and pissed quite a few of the technical community off.
@BlackScienceM:
DDoS was originated from infected computers using master servers to botnet accounts. Please shut the fuck up and stop attacking her like she's the most ignorant person on the planet. She isn't Al Sharpton or Obama ffs.
Secondly: The picture left above explains perfectly how DDoS works. You have the attacker(s) and then you have a series of master servers who query the slave servers. The slave servers can be botnet accounts, infected computers, or slave machines running the software needed to send information to servers to be filtered out. When there's too many packets incoming, the server is rendered unresponsive because it's attempting to filter so many negligible packets containing no data that it sets the server on overload.
In this case we are aware it's a uLink problem, and therefore they're rendering it through different means. Case in point is that you made your statement, it was good for the most part, and you were correct in many ways.
It's funny how so many people are technical networking engineers all of a sudden when someone comes out and posts something for the general population of a forum and the amount of butthurt in them comes out.
Unless there's screenshots of your guys' degrees... you've got no proof to say your post is more valid than hers because of your googling for the limited amount of knowledge behind networking you do have.
That's all.
OP,
Well done. Whether or not your explanation and analogies of a DDoS were correct or not, you've managed to divert the previously unmitigated torrents of extreme nerd rage flowing from the folks who think that Alpha means "finished game" from Garry to you, thus acting as a lightning rod.
However, I think what you really need to provide is a succinct example of what the word "empathy" means. After all, that is what you're asking everyone to have for the developers, right? Could you explain that to everyone so they understand what the real point of your post was?
Oh, wait...feelings...the internet...tech-nerds whose emotional intelligence has been sterilized due to years of burying their heads in hyper logic and impersonal machinery...
On second thought, keep being a lightning rod. +1!
[QUOTE=Ehngage;43357212]Then perhaps SUGGEST something instead of being a moronic ass who isn't contributing anything to the conversation.[/QUOTE]
This thread is quite useless other then 2 post....it should just get deleted as it is more confusing then anything.
-Dan
[QUOTE=ochie;43362289]This thread is quite useless other then 2 post....it should just get deleted as it is more confusing then anything.
-Dan[/QUOTE]
And yet you felt that your addition to this post was anything but useless? Please. Go back to hiding under your rock.
The best way to explain a DDoS attack is by explaining it with real world examples.
Imagine its Black Friday at Walmart!
Everyone is going to go buy some snackfoods, and at first everything is flying smoothly and well. Occasionally we get some issues with people getting stuck in between other people. This is what we will call "latency". Even with this "latency" people still manage to get by with a little bit of time.
Now, over the intercom the manager of the store announces, "Discount on Twinkees in the snack aile :D" everyone is ecstatic, but before anyone can get there a bunch of fat people smash into one side of the aile, and get stuck. This is a DoS attack. One end is blocked, and stops all traffic from going through that way. Traffic can be routed to the other way around, but it still hinders oncoming traffic without the usage of something we call "routing the clients"
Now, everything is going smoothly with Walmart's employees trying to ease the fatasses out of the other side, but then another problem occurs. They never monitored the traffic to the other side, and we now have all the fat people's children rushing to the other side in the 100's, and they all get stuck... This is a DDoS attack. Now you can't get in no matter which way you take, and theirs not exception to routing anything.
Ultimately, the fat people are stuck until they lose weight, and therefore that snackfood aile can never be reached again. Unless they start pulling out, and stop being fatasses, no one can access the delicious snackfoods of that aile.
A few weeks later, the fatasses have lost weight, and are now no-longer a problem. The encompass of this issue has forced Walmart to rethink their strategy of item placement, and they now have two back up ailes(backup servers), which they can route traffic too during fatass loads sticking up the original aile.
Another method is the Hostess company releasing the recipe as open source freeware. All though fatasses will still get stuck sometimes in the main retailer aile, people now can make them at home because they are "open source" for anyone to make and host their own bakery stalls.
The OP's post is the technical explanation of how DDoS's work. This is just simplifying it too real life situations.
[QUOTE=JoeSkylynx;43362702]The best way to explain a DDoS attack is by explaining it with real world examples.
Imagine its Black Friday at Walmart!
Everyone is going to go buy some snackfoods, and at first everything is flying smoothly and well. Occasionally we get some issues with people getting stuck in between other people. This is what we will call "latency". Even with this "latency" people still manage to get by with a little bit of time.
Now, over the intercom the manager of the store announces, "Discount on Twinkees in the snack aile :D" everyone is ecstatic, but before anyone can get there a bunch of fat people smash into one side of the aile, and get stuck. This is a DoS attack. One end is blocked, and stops all traffic from going through that way. Traffic can be routed to the other way around, but it still hinders oncoming traffic without the usage of something we call "routing the clients"
Now, everything is going smoothly with Walmart's employees trying to ease the fatasses out of the other side, but then another problem occurs. They never monitored the traffic to the other side, and we now have all the fat people's children rushing to the other side in the 100's, and they all get stuck... This is a DDoS attack. Now you can't get in no matter which way you take, and theirs not exception to routing anything.
Ultimately, the fat people are stuck until they lose weight, and therefore that snackfood aile can never be reached again. Unless they start pulling out, and stop being fatasses, no one can access the delicious snackfoods of that aile.
A few weeks later, the fatasses have lost weight, and are now no-longer a problem. The encompass of this issue has forced Walmart to rethink their strategy of item placement, and they now have two back up ailes(backup servers), which they can route traffic too during fatass loads sticking up the original aile.
Another method is the Hostess company releasing the recipe as open source freeware. All though fatasses will still get stuck sometimes in the main retailer aile, people now can make them at home because they are "open source" for anyone to make and host their own bakery stalls.
The OP's post is the technical explanation of how DDoS's work. This is just simplifying it too real life situations.[/QUOTE]
Fatasses and twinkies anology = fucking win. GG sir. You have my Winner award.
LMAOing pretty hard over here.
A DOS is a "Denial-Of-Service" attack. That is, an attack which [I]denies[/I] someone else a [I]service[/I]. By taking the servers down, it is a DOS attack, by definition.
the fact that they dont care about hackers atm says alot
[QUOTE=zeroxzzz;43363076]the fact that they dont care about hackers atm says alot[/QUOTE]
you really think we don't care about hackers? we've had our programmers stay up working 18-hour days so they can fix the exploits in the networking library, for god's sake!
[QUOTE=JoeSkylynx;43362702]The best way to explain a DDoS attack is by explaining it with real world examples.
Imagine its Black Friday at Walmart!
Everyone is going to go buy some snackfoods, and at first everything is flying smoothly and well. Occasionally we get some issues with people getting stuck in between other people. This is what we will call "latency". Even with this "latency" people still manage to get by with a little bit of time.
Now, over the intercom the manager of the store announces, "Discount on Twinkees in the snack aile :D" everyone is ecstatic, but before anyone can get there a bunch of fat people smash into one side of the aile, and get stuck. This is a DoS attack. One end is blocked, and stops all traffic from going through that way. Traffic can be routed to the other way around, but it still hinders oncoming traffic without the usage of something we call "routing the clients"
Now, everything is going smoothly with Walmart's employees trying to ease the fatasses out of the other side, but then another problem occurs. They never monitored the traffic to the other side, and we now have all the fat people's children rushing to the other side in the 100's, and they all get stuck... This is a DDoS attack. Now you can't get in no matter which way you take, and theirs not exception to routing anything.
Ultimately, the fat people are stuck until they lose weight, and therefore that snackfood aile can never be reached again. Unless they start pulling out, and stop being fatasses, no one can access the delicious snackfoods of that aile.
A few weeks later, the fatasses have lost weight, and are now no-longer a problem. The encompass of this issue has forced Walmart to rethink their strategy of item placement, and they now have two back up ailes(backup servers), which they can route traffic too during fatass loads sticking up the original aile.
Another method is the Hostess company releasing the recipe as open source freeware. All though fatasses will still get stuck sometimes in the main retailer aile, people now can make them at home because they are "open source" for anyone to make and host their own bakery stalls.
The OP's post is the technical explanation of how DDoS's work. This is just simplifying it too real life situations.[/QUOTE]
Thanks for providing another metaphor. Loved this one. In particular, mostly I was writing about what I had researched, paraphrasing, and the like. I'm grateful for people who actually stepped in to help, such as yourself. So, thanks!
I'm hoping that it fixes itself. I've also heard (word of mouth, I have no idea) League of Legends and Dota 2 apparently had a mini.. hacking... fiasco.. thing.
Maybe everyone wants to get their trouble making done before new-years, then their new-years revolution might just be "get a life" or "eat less twinkies" :)
[editline]30th December 2013[/editline]
[QUOTE=MaxOfS2D;43363100]you really think we don't care about hackers? we've had our programmers stay up working 18-hour days so they can fix the exploits in the networking library, for god's sake![/QUOTE]
Again, I think you guys are doing the best you can with what you've got. Any form of interruption in moderating and/or server reliability is kind of hard to deal with. But these things tend to get fixed, it takes a while, but they'll be fixed.
And it doesn't help everyone complains about it like they paid 200$ instead of 20$.
Here's another explanation of the ULink exploit:
There's a sale at walmart, which is irrelevant since fatasses spend too much time in their basements trying to halt the development of a game by finding exploits instead of actually doing something useful such as getting a job.
Best way to explain DDoS is to start by explaining what a DoS is - and you don't need an analogy; in real terms somebody parking their car in front of your garage to stop you using it [B][I]is[/I][/B] a DoS attack. A DDoS is when that attack comes from multiple sources (never believe it when you hear the attack is coming from China or France or something: with UDP-based attacks it is trivial to spoof the source IP from any network that doesn't implement [URL="http://www.bcp38.info/index.php/Main_Page"]BCP38[/URL]). In the car in front of your garage example it would be a bunch of people turning the entrance to your garage into a car park.
Sorry, you need to Log In to post a reply to this thread.
