From owner-freebsd-security Sat Apr 21 8:55:51 2001 Delivered-To: freebsd-security@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 0EAB237B422 for ; Sat, 21 Apr 2001 08:55:48 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 17570 invoked by uid 1000); 21 Apr 2001 15:54:10 -0000 Date: Sat, 21 Apr 2001 18:54:10 +0300 From: Peter Pentchev To: Lee Smallbone Cc: freebsd-security@freebsd.org Subject: Re: ipfw problem Message-ID: <20010421185410.C458@ringworld.oblivion.bg> Mail-Followup-To: Lee Smallbone , freebsd-security@freebsd.org References: <200104211706.SAA31941@mailgate.kechara.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104211706.SAA31941@mailgate.kechara.net>; from lee@kechara.net on Sat, Apr 21, 2001 at 04:54:35PM +0100 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Apr 21, 2001 at 04:54:35PM +0100, Lee Smallbone wrote: > Hi there, > > The machine stops booting on either of these two rules, and I have to boot into > single user, remove the rules and reboot. What's wrong with them? > > ${fwcmd} add 300 unreach 9 all from 213.46.1.1-213.46.123.254 to ${ip} > > I also get the same problem on this rule (in place of the one above): > > ${fwcmd} add 300 deny all from 213.46.1.1-213.46.123.254 to ${ip} Where exactly in the boot process does it 'stop'? What application/program is it trying to execute? Or does ipfw itself hang when adding those rules? G'luck, Peter -- If this sentence were in Chinese, it would say something else. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message