From owner-freebsd-security Fri Jan 26 1:55:46 2001 Delivered-To: freebsd-security@freebsd.org Received: from supermall.dk (mail.absolute-promotion.dk [195.41.95.9]) by hub.freebsd.org (Postfix) with SMTP id 211E937B404 for ; Fri, 26 Jan 2001 01:55:28 -0800 (PST) Received: (qmail 10942 invoked from network); 26 Jan 2001 09:46:42 -0000 Received: from unknown (HELO incorp.dk) (195.41.95.56) by mail.absolute-promotion.dk with SMTP; 26 Jan 2001 09:46:42 -0000 Message-ID: <3A715799.8EECF43@incorp.dk> Date: Fri, 26 Jan 2001 10:55:21 +0000 From: Dennis Rand X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-security@freebsd.org Subject: Re: ICMP attacks References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I also have this problem but that is when i portscan my computer from another host so is there a place or a log where i can check what IP has caused this Will Mitayai Keeso Rowe wrote: > > icmp-response bandwidth limit 205/200 pps > > icmp-response bandwidth limit 264/200 pps > > icmp-response bandwidth limit 269/200 pps > > icmp-response bandwidth limit 273/200 pps > > icmp-response bandwidth limit 273/200 pps > > icmp-response bandwidth limit 271/200 pps > > icmp-response bandwidth limit 261/200 pps > > icmp-response bandwidth limit 268/200 pps > > icmp-response bandwidth limit 205/200 pps > > icmp-response bandwidth limit 223/200 pps > > Is there any way to trace the people that are causing this? It's becoming a > daily occurance and it's beginning to irritate me. > > -Mit > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message -- Med Venlig Hilsen / Best regards __________________________ Dennis Rand inCorp A/S - Odense Middelfartvej 9-11 5000 Odense C Tlf.: 70 22 55 30 Fax.: 63 12 55 39 Email: dr@incorp.dk http://www.inCorp.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message