From owner-freebsd-security Tue Jan 21 12:36: 5 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 3ECFA37B401 for ; Tue, 21 Jan 2003 12:36:04 -0800 (PST) Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.100.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id B26E043F18 for ; Tue, 21 Jan 2003 12:36:03 -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 h0LKZvvD077479 for ; Tue, 21 Jan 2003 14:35:58 -0600 (CST) (envelope-from martin@dc.cis.okstate.edu) Message-Id: <200301212035.h0LKZvvD077479@dc.cis.okstate.edu> To: freebsd-security@FreeBSD.ORG Subject: Re: Limiting icmp unreach response from 231 to 200 packets per second Date: Tue, 21 Jan 2003 14:35:57 -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 This is Martin McCormick again and it looks like those who said that bind first got sick and caused the situation that generated the ICMP slow-down are 100% right. I had been concentrating on the syslog file since the problem appeared to be network-related and there just wasn't much there to look at in the way of tracks, but I sure found tracks when I looked at the named.log file. Things had been going along quite busily with the usual transfers and dynamic updates and then: Jan 21 09:04:43.081 client 139.78.48.251#13631: no more TCP clients: quota reached That went on for a short time and then bind crashed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message