Date: Fri, 3 May 2013 00:59:38 +1000 (EST) From: Ian Smith <smithi@nimnet.asn.au> To: Mark Felder <feld@feld.me> Cc: freebsd-jail@freebsd.org Subject: Re: vnet jail with ipfw having logging problem Message-ID: <20130503004508.L30818@sola.nimnet.asn.au> In-Reply-To: <op.wwgnv8qy34t2sn@tech304.office.supranet.net> 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> <FC2D92AC-207F-4AC3-8B57-E837EF8DD779@netplex.se> <51826EF7.30302@a1poweruser.com> <op.wwgnv8qy34t2sn@tech304.office.supranet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2 May 2013 09:29:58 -0500, Mark Felder wrote:
> On Thu, 02 May 2013 08:49:43 -0500, Joe <fbsd8@a1poweruser.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130503004508.L30818>