From owner-freebsd-jail@FreeBSD.ORG Thu May 2 14:59:47 2013 Return-Path: Delivered-To: freebsd-jail@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AE0A5FCC for ; Thu, 2 May 2013 14:59:47 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 24E011186 for ; Thu, 2 May 2013 14:59:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id r42ExcaA078398; Fri, 3 May 2013 00:59:39 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 3 May 2013 00:59:38 +1000 (EST) From: Ian Smith To: Mark Felder Subject: Re: vnet jail with ipfw having logging problem In-Reply-To: Message-ID: <20130503004508.L30818@sola.nimnet.asn.au> References: <44AC45947DA14449AEDFB13B9F6C5F7DAF3E1FA5@ltcfiswmsgmb25> <517A7BCB.8060604@a1poweruser.com> <13CA24D6AB415D428143D44749F57D7201F22068@ltcfiswmsgmb21> <517D3426.1090703@a1poweruser.com> <51805EFB.6050806@a1poweruser.com> <20130502021830.O30818@sola.nimnet.asn.au> <51818C67.7070708@a1poweruser.com> <20130502142443.V30818@sola.nimnet.asn.au> <51826EF7.30302@a1poweruser.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-jail@freebsd.org X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 May 2013 14:59:47 -0000 On Thu, 2 May 2013 09:29:58 -0500, Mark Felder wrote: > On Thu, 02 May 2013 08:49:43 -0500, Joe wrote: > > > > I tested doing a kldload ipfw and fall into the default deny problem. > > Is there a sysctl to flip the default deny to default accept? > > > > options IPFIREWALL_DEFAULT_TO_ACCEPT when you build the kernel is the only > way AFAIK % man ipfw /FINE POINTS [..] o If you are logged in over a network, loading the kld(4) version of ipfw is probably not as straightforward as you would think. The fol- lowing command line is recommended: kldload ipfw && \ ipfw add 32000 allow ip from any to any Along the same lines, doing an ipfw flush in similar surroundings is also a bad idea. I expect running jexec(8) qualifies as 'logged in over a network' here? cheers, Ian