Date: Fri, 09 Jun 2006 15:35:52 +0700 From: Roger Merritt <mcrogerm@stjohn.ac.th> To: freebsd-questions@FreeBSD.ORG Cc: Nick Withers <nick@nickwithers.com> Subject: Re: natd not starting on boot-up Message-ID: <5.2.0.9.0.20060609152309.00b105a8@127.0.0.1> In-Reply-To: <20060609141313.cf5129b6.nick@nickwithers.com> References: <5.2.0.9.0.20060607172108.032e7db8@127.0.0.1> <20060607183003.23ae3f8c.nick@nickwithers.com> <5.2.0.9.0.20060607120734.00a80700@127.0.0.1> <5.2.0.9.0.20060607151302.00b25118@127.0.0.1> <20060607183003.23ae3f8c.nick@nickwithers.com> <5.2.0.9.0.20060607172108.032e7db8@127.0.0.1>
next in thread | previous in thread | raw e-mail | index | archive | help
At 02:13 PM 6/9/2006 +1000, you wrote: >I've been doing a little hunting around to figure out >how /etc/rc.d/natd's called in the first place and it seems >this is done by the /etc/rc.d/ipfw script, which in turn is run >when "firewall_enable" is set >in /etc/rc.conf. /etc/rc.d/natd's not run directly >by /etc/rc due to its having the "nostart" KEYWORD. > >Is IPFW definitely launched correctly on the system? Definitely. After I reboot I entered 'ipfw show' and it displayed the ruleset it's using. The first rule (actually number 0050) is 'divert 8668 ip4 from any to any via ed1'. Hmmm. Only 'ip4'? I have ip6 enabled, too, although as far as I know I only deal with ip4. Something new to research. >Otherwise, perhaps it's worthwhile chucking a debug echo or two >about the place (for instance, in /etc/rc.d/natd and / >or /etc/rc.d/ipfw) and rebooting. Something like this should do >the trick, I believe: "echo && echo && echo && echo >'/etc/rc.d/natd' && echo && echo && echo" (without the outer >quotes). > >-- >Nick Withers >email: nick@nickwithers.com >Web: http://www.nickwithers.com >Mobile: +61 414 397 446 Well, I'll give it a try. Thanks for the suggestion. -- Roger
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.2.0.9.0.20060609152309.00b105a8>