From owner-freebsd-security Tue Jan 21 8: 0:16 2003 Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0B9837B401 for ; Tue, 21 Jan 2003 08:00:14 -0800 (PST) Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.100.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DF7143E4A for ; Tue, 21 Jan 2003 08:00:14 -0800 (PST) (envelope-from martin@dc.cis.okstate.edu) Received: from dc.cis.okstate.edu (localhost.cis.okstate.edu [127.0.0.1]) by dc.cis.okstate.edu (8.12.6/8.12.6) with ESMTP id h0LG08vD022507 for ; Tue, 21 Jan 2003 10:00:08 -0600 (CST) (envelope-from martin@dc.cis.okstate.edu) Message-Id: <200301211600.h0LG08vD022507@dc.cis.okstate.edu> To: freebsd-security@FreeBSD.ORG Subject: Limiting icmp unreach response from 231 to 200 packets per second Date: Tue, 21 Jan 2003 10:00:08 -0600 From: Martin McCormick Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On rare occasions, a FreeBSD system in our network has been known to print the example shown in the subject at a furious rate for a short time and then things get back to normal. Is that what the effects of a ping flood look like? On one system running bind9, the named process died after the syslog message said that packets had reached 243 per second, but I was able to restart it within seconds of its crash. Only the named process crashed, not the system. Any ideas as to what this is? Martin McCormick WB5AGZ Stillwater, OK OSU Center for Computing and Information Services Network Operations Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message