From owner-freebsd-security Wed Aug 11 20: 4:55 1999 Delivered-To: freebsd-security@freebsd.org Received: from tasam.com (tasam.com [206.161.83.22]) by hub.freebsd.org (Postfix) with ESMTP id 4E025156BC for ; Wed, 11 Aug 1999 20:04:49 -0700 (PDT) (envelope-from freebsd.list@bug.tasam.com) Received: from bug (216-164-241-26.s26.tnt10.lnh.md.dialup.rcn.com [216.164.241.26]) by tasam.com (8.9.3/8.9.1) with SMTP id XAA26983; Wed, 11 Aug 1999 23:04:32 -0400 (EDT) Message-ID: <003901bee46f$5b90ed80$0286860a@tasam.com> From: "Joe Gleason" To: , References: <37b234fe.c8.0@telebot.com> Subject: Re: ipfw Date: Wed, 11 Aug 1999 23:02:03 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Probably the best way to block floods of that sort of dummynet and put some rate limiting there. ----- Original Message ----- From: Jason Schwab To: Sent: Wednesday, August 11, 1999 23:44 Subject: ipfw > what rules should I add to my ipfw ruleset to block out icmp > floods and smurf attacts, etc thanks. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message