Date: Thu, 2 Oct 2008 11:09:32 +0700 From: "fire jotawski" <jotawski@gmail.com> To: "Kevin Kinsey" <kdk@daleco.biz> Cc: freebsd-questions@freebsd.org, fbsd1@a1poweruser.com Subject: Re: nat and firewall Message-ID: <c583719d0810012109i2b9f4a01u12b5bf26bbfd8508@mail.gmail.com> In-Reply-To: <48DA7491.8030002@daleco.biz> References: <NBECLJEKGLBKHHFFANMBOEBFCLAA.fbsd1@a1poweruser.com> <48DA7491.8030002@daleco.biz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 25, 2008 at 12:10 AM, Kevin Kinsey <kdk@daleco.biz> wrote: > FBSD1 wrote: > >> >> natd_enable="YES" This statement in rc.conf enables ipfw nated function. >> firewall_nat_enable="YES" This is an invalid statement. No such thing as >> you have here. >> > > This is no longer true; he did indeed find "firewall_nat_enable" > in /etc/defaults/rc.conf. The knob seems to have first appeared > in February in HEAD and I'm guessing it cues the system to use a > new kernel-based nat rather than natd(8), but I've not read anything > further about this, as my system isn't as up to date as the OP's. > I don't know when this change was MFC'ed, but apparently fairly > recently? > > I suppose we need someone a tad more "in the know" to straighten > that out for us. > up to this moment, i do not know if natd and firewall_nat function in the same or different. and is there firewall_nat_flags thing too ? thanks in advanced for any helps and hints. regards, psr > > Kevin Kinsey > -- > A wise man can see more from a mountain top > than a fool can from the bottom of a well. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c583719d0810012109i2b9f4a01u12b5bf26bbfd8508>