07-02-2014
It's hard to use iptables effectively to mitigate an DDOS attack with changing IP addresses.
Most attackers easily change IP addresses; but they forget to change the User Agent string, so it's often easier to block the hackers User Agent string. Did you do any analysis on the UA strings?
Also, if you are using Apache2, there may be an anti-DDOS module, as I recall.
This User Gave Thanks to Neo For This Post:
5 More Discussions You Might Find Interesting
1. Cybersecurity
heloo
today i have DDos Attack in my server
what is the better way to secure my server from DDos Attack
i use CentOS 4&5
i try every firewall and talk to softlayer - iweb i've Tried every possible solutions but I can not find a solution to the problems
Give Me The best way plzz (4 Replies)
Discussion started by: a7medo
4 Replies
2. Cybersecurity
In my logs I find entries about attacks on my system. I know IP addresses, I know date and time and I know what they tried to do. So what's the best I can do now? Tell everybody that there are cybercriminals on that network? Write an email to their admin? Anything else? (10 Replies)
Discussion started by: Action
10 Replies
3. Cybersecurity
are there any popular DDoS simulation tools to test my own infrastructure? Anyone tried to setup all these in AWS EC2? (1 Reply)
Discussion started by: boriskong
1 Replies
4. Cybersecurity
How to protect DDoS and brute force attack.
I want to secure my server and block attacker. (1 Reply)
Discussion started by: romanepo
1 Replies
5. UNIX for Advanced & Expert Users
Hi guys, just need a opinion from you.
I found anti ddos script from github
Script
What is your opinion about it? Is it usefull? Do you have some similar? I want to protect my servers on all levels, why not in the servers via script.
I assume I must fix this script to be useful for me, but... (1 Reply)
Discussion started by: tomislav91
1 Replies
LEARN ABOUT DEBIAN
log::agent::tag::priority
Agent::Tag::Priority(3pm) User Contributed Perl Documentation Agent::Tag::Priority(3pm)
NAME
Log::Agent::Tag::Priority - a log priority tag string
SYNOPSIS
Not intended to be used directly
Inherits from Log::Agent::Tag.
DESCRIPTION
This class represents a log priority tag string.
CREATION ROUTINE PARAMETERS
The following parameters are defined, in alphabetical order:
"-display" => string
Specifies the priority/level string to display, with minimal variable substitution. For instance:
-display => '[$priority/$level]'
The defined variables are documented in the DISPLAY VARIABLES section underneath.
"-level" => level
This parameter is internally added by "Log::Agent" when computing the priority tag, since only it knows the level of the current
messsage.
"-postfix" => flag
Whether tag should be placed after or before the log message. By default, it is prepended to the log message, i.e. this parameter is
false.
"-priority" => prio
This parameter is internally added by "Log::Agent" when computing the priority tag, since only it knows the priority of the current
messsage.
"-separator" => string
The separation string between the tag and the log message. A single space by default.
DISPLAY VARIABLES
The "-display" switch understands a few variables that can be substituted in the supplied string. Both $var and "${var}" forms are
supported. Unknown variables are left untouched.
$priority
The full priority name of the logged message, e.g. "warning" or "error".
$level
The associated priority level of the logged message, a number. For instance, the level associated to "warning" is 4. See
Log::Agent::Priorities for the default name -> level mapping.
AUTHOR
Raphael Manfredi <Raphael_Manfredi@pobox.com>
SEE ALSO
Log::Agent::Tag(3), Log::Agent::Message(3), Log::Agent::Priorities(3).
perl v5.10.0 2002-03-09 Agent::Tag::Priority(3pm)