Date: Mon, 8 Feb 2010 10:24:18 -0600 From: John <john@starfire.mn.org> To: Warren Block <wblock@wonkity.com> Cc: freebsd-questions@freebsd.org Subject: Re: Can loader.conf give you NATD support? Message-ID: <20100208102418.A24197@starfire.mn.org> In-Reply-To: <alpine.BSF.2.00.1002080827190.77390@wonkity.com>; from wblock@wonkity.com on Mon, Feb 08, 2010 at 08:39:14AM -0700 References: <20100208075855.A20993@starfire.mn.org> <alpine.BSF.2.00.1002080827190.77390@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 08, 2010 at 08:39:14AM -0700, Warren Block wrote: > On Mon, 8 Feb 2010, John wrote: > > > The natd man page says it is still necessary to create a customer > > kernl with > > > > options IPFIREWALL > > options IPDIVERT > > > > Is that still true, or can it be accomplished vi a loader.conf? > > It's a kernel option, so you probably can't do it at runtime. > > Consider using pf instead of ipfw. pf does NAT without needing natd or > those kernel options. Oh. OK! That must be new since the last time I did this. Will it be difficult to port my ipfw and natd rules to pf? > -Warren Block * Rapid City, South Dakota USA > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" -- John Lind john@starfire.MN.ORG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100208102418.A24197>