netdev - ping DOS avoidance?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <d9dc600703141859x3eeddd4cs51b3aea89d4dc32a@mail.gmail.com>
Date:	Wed, 14 Mar 2007 18:59:56 -0700
From:	"Luis Carlos Cobo Rus" <luiscarlos@...il.com>
To:	"Netdev List" <netdev@...r.kernel.org>
Subject: ping DOS avoidance?

Hi,

I'm stress testing some network devices by doing some cross flood
pings among them. It occurs  sometimes that one of the hosts (host
foo) will stop answering to pings from other hosts. foo can ping all
the other hosts, and I can use ssh back and forth, but it doesn't
answer ping requests.

More info:
- tcpdump at foo actually shows the ping requests (but no replies)
- other network interfaces connected at foo also stop answering pings
- icmp_echo_ignore_all is 0
- foo cannot even ping itself. I would swear it was able to ping
itself, but just went to confirm it for this mail and found out it
isn't.

I took a look at icmp.c to see where the packet could get dropped but
found nothing. I assume it's some kind of DOS prevention, but I don't
know where it is taking place nor how to revert it. Any hint would be
appreciated.

Thanks in advance!

--
Luis Carlos Cobo Rus       GnuPG ID: 44019B60
cozybit Inc.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html