my friend got dos'ed because he uses irc during bh and he lost 2m of stuff . not much but this just shows that dos'ing is still happening.

It's DOS'ing, not DDOS'ing. I highly doubt a script kiddie will have a botnet under his command to pull a distributed denial of service attack.

 

But we know this is happening, and there's an easy fix: Don't go on IRC. If you get electrocuted every time you stick a fork in the socket, your best bet would probably be to stop sticking the fork in the socket, rather than complain to the fork manufacturers or your electric company.

http://www.itsyourip.com/networking/disable-icmp-redirects-in-windows2000xp2003/

 

If you don't feel like visiting the article here is how you disable icmp ping echo requests, this is what most DOS and DDOS attacks use(the simple ones at least, which is what these RS attacks are).

 

(This will only apply in windows and other operating systems it may be in an entirely different place or disabled manually by the command line.)

Start > run > regedit > HKey_Local_Machine > System > CurrentControlSet > Services > TCP/IP > Parameters

 

A long list of names has now appeared in the main registry menu of regedit. Look for "EnableICMPRedirect", double-click, and then set it to 0. Congratulations you are now immune to these [developmentally delayed]ed script kiddies.

 

Now, what did this do? It rejects all incoming ping requests in ICMP(http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol).

Sorry Stragomagnus, but disabling ICMP isn't going to stop a potential DOS. If any script kiddie has a grip on the situation, they'll try the "legal" traffic ports that the person has - probably the same TCP/UDP ports that you use to connect to IRC anyway (6667, 6668). To block these would be to restrict him from using IRC, and since he's obviously not blocking those, they are a much better target than any other arbitrary port.

 

A thirty-second brief on DOS attacks: Imagine a kindergarten teacher getting flooded with questions from all thirty-five of her students, or imagine Mod MMG's chatroom when he shows up, and the room is full. Both are examples of perfectly legal communication (traffic), but the sheer amount of it in such a small time basically doesn't allow for the handler (teacher, MMG, or MMG's ranks) to communicate with them effectively, slowing, stalling, or stopping communication altogether.

 

Anyway, the only way to fix this is as follows:

 

But we know this is happening, and there's an easy fix: Don't go on IRC. If you get electrocuted every time you stick a fork in the socket, your best bet would probably be to stop sticking the fork in the socket, rather than complain to the fork manufacturers or your electric company.

 

Prevention is the best cure. If you can't avoid going to IRC, though, then only go to networks that you can trust, and only go to channels with reputable Ops. Or be clever enough to not play RS while on IRC if you can't trust the Ops.

That is where firewall blocking comes in Makoto, if they have a handle on that. For that level, a firewall can be set to reject incoming packets of this nature by deliberately setting the rejection of packets to a very low level...Of course it still won't stop the clogging of the line itself.

 

 

The ICMP part was mainly for the old style of DOS.

Please use the following topic; http://forum.tip.it/topic/188841-what-i-hate-about-getting-pked-other-than-dying/ :)