From owner-freebsd-stable Thu Feb 11 07:23:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01079 for freebsd-stable-outgoing; Thu, 11 Feb 1999 07:23:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.mtlusa.com (dc-35-252.ici.net [207.180.35.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01071 for ; Thu, 11 Feb 1999 07:23:29 -0800 (PST) (envelope-from madlove@cs.umb.edu) Received: by mail.mtlusa.com from localhost (router,QMProSrv V2.6); Thu, 11 Feb 1999 10:23:25 -0500 Received: by mail.mtlusa.com from www.noel.nu (207.180.35.234::mail daemon,QMProSrv V2.6); Thu, 11 Feb 1999 10:23:25 -0500 Message-ID: <36C2AFC4.CE6B7055@cs.umb.edu> Date: Thu, 11 Feb 1999 05:24:05 -0500 From: "Luke H." Reply-To: madlove@cs.umb.edu Organization: MTL X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.8-STABLE i386) MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: 3.0-stable supports bandwidth limitation in the kernel? Content-Type: multipart/alternative; boundary="------------27B01BE890CC22F9CB170AA7" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------27B01BE890CC22F9CB170AA7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi all, I heard that 3.0-current has the option in the kernel where you can enable the bandwidth limitation to prevent ping flood attack. Does 3.0-stable have that function, too? I ask coz I'm still in 2.2.8-stable (waiting for 3.1-stable coming out) Thanx, Luke --------------27B01BE890CC22F9CB170AA7 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit 
Hi all,
I heard that 3.0-current has the option in the kernel where you can enable the bandwidth limitation to prevent ping flood attack.  Does 3.0-stable have that function, too?   I ask coz I'm still in 2.2.8-stable (waiting for  3.1-stable coming out)
Thanx,
Luke
  --------------27B01BE890CC22F9CB170AA7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message