From owner-freebsd-security Fri Jun 29 14:49:42 2001 Delivered-To: freebsd-security@freebsd.org Received: from ringworld.nanolink.com (diskworld.nanolink.com [195.24.48.189]) by hub.freebsd.org (Postfix) with SMTP id BBD4837B40C for ; Fri, 29 Jun 2001 14:49:22 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 1888 invoked by uid 1000); 29 Jun 2001 21:53:46 -0000 Date: Sat, 30 Jun 2001 00:53:46 +0300 From: Peter Pentchev To: appleseed@hushmail.com Cc: freebsd-security@FreeBSD.ORG Subject: Re: What is ipfw telling me ? Message-ID: <20010630005346.A887@ringworld.oblivion.bg> Mail-Followup-To: appleseed@hushmail.com, freebsd-security@FreeBSD.ORG References: <200106292115.OAA06336@user7.hushmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106292115.OAA06336@user7.hushmail.com>; from appleseed@hushmail.com on Fri, Jun 29, 2001 at 02:05:12PM -0500 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 Fri, Jun 29, 2001 at 02:05:12PM -0500, appleseed@hushmail.com wrote: [snip] > If you want to > close off access to that subnet creating incoming tcp/udp sessions I suggest > u > upgrade to ipf (;-)) and define keep state rules as well as deny incoming > session > initialization attempts. This way u can still access google's nifty database > but they > cant access u =) Uhm. ipfw(4) is stateful, too. I suggest you take a look at ipfw(4) and ipfw(8) :) G'luck, Peter -- This sentence every third, but it still comprehensible. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message