Re: Ping Flood - whats is mean when ....
Marcin Bednarz <firstname.lastname@example.org> writes:
> I was recently receiving very many of Ping Flood.
> In my logs:
> ....... kernel: PING Flood IN=eth1 OUT= .......
It's most likely an attack.
It could be a single machine sending packets with random, forged
source IP addresses. Or, it could be several machines---cracked by
the attacker---that have *all* been directed to do this.
Alternatively, it may be a so-called "smurf" attack. This is where
someone sends ping requests to broadcast addresses forged as if they
came from your machine. The broadcast addresses are directed to
networks of machines that are misconfigured to respond to broadcast
pings. As a result, the attacker can send one ping request and
generate 50 or 60 packets of replies (which go to you because of the
forged source address of the request). By pinging several of these
misconfigured networks at a reasonable rate, the attacker hopes to
overwhelm your host without a traffic burden on his or her end.
Try to google for "smurf" or "smurf attack", or take a look at:
for more information. In particular, see the section titled
"Solutions for the Victim".
Note that the messages you are seeing are rate-limited---after the
first burst, they should appear at a maximum rate of once every 20
minutes or so. You'll need to run "tcpdump" or a similar packet
dumping utility to see them all. Then you'll be able to figure out
the rate they're coming in and whether the addresses look totally
random (in which case it's probably one of the first two kinds of
attack) or come from the same networks over and over (in which case
it's probably a smurf attack).
The bottom line is that you'll probably need to notify your upstream
provider (in this case, your university IT people) and have them
Kevin Buhr <email@example.com>
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com